chore(release): correct v0.1.5 date

[thequantumfalcon]

What this changes

This is an intentional release-metadata correction, not a bug repair. The
0.1.5 release date recorded on main was 2026-09-09. The owner has directly
selected 2026-09-10 as the real ISO release date, and no release occurred
under the previous value.

• CHANGELOG.md changes its 0.1.5 heading date to 2026-09-10.
• CITATION.cff changes date-released to 2026-09-10.
• tests/test_release_controls.py changes the current-metadata expected tuple
  to 2026-09-10.

No runtime, scanner, hook, workflow, dependency, or protected-control code
changes.

path	mode	added	deleted
CHANGELOG.md	100644	1	1
CITATION.cff	100644	1	1
tests/test_release_controls.py	100644	1	1

Linked issue

No issue is linked. The direct owner selection of the real release date
prompted this change.

Checklist

• The PR title is a Conventional Commit — feat, fix, docs, test, refactor, or chore. Given the trust core's change bar, feat usually needs an accepted proposal issue first. Everything is merged by squash, so this title becomes the permanent commit subject on main. See CONTRIBUTING.md.
• just test passes.
• just lint passes.
• just deps passes — causal_continuity_engine/ still imports nothing outside the standard library.
• just bench passes — all eleven ContinuityBench scenarios, every metric at target.
• just corpus passes — the reference still agrees with the committed vectors in vectors/.
• just caps passes — every capability claim still resolves to real symbols, files, and tests. If the claims changed, docs/CAPABILITIES.md was regenerated with python -m causal_continuity_engine.capabilities --write rather than hand-edited.
• just build passes if packaging, generated assets, or release machinery changed — both builds match and the clean-installed wheel audits successfully.
• Every commit carries a Signed-off-by trailer (git commit -s). Enforced: the DCO check is a required status on main, so a pull request with any commit missing the trailer cannot merge.
• No gate was weakened, skipped, or made conditional in order to get a test to pass. If a gate had to change, that change is the subject of this PR and is argued for above.
• No AI attribution anywhere in the diff, commit messages, or PR title or body.

Every box is checked against the gates run from this exact commit, listed
below.

If this is a bug fix

Not applicable — this is an intentional release-metadata correction, not a
defect repair.

Candidate identity

• candidate b58e206b1212f41f008b6893d08d2149d5f926bb
• parent 4eda663317bea5bca9c92909f88e82fbe24a2b38
• tree 804307d946f76998917315acdeaf37b74d2d29de
• incremental patch 1,602 bytes, SHA-256
  8ca953a7269ecfaa6d44876467cf38dfd7cd135d8b5a6e3f645e697066dd6ba6
• stable patch ID 387f1d307904e8dbc340789b8c3828a2fd54be33
• three paths, all mode 100644, +3/-3
• new blobs 9b0f3e1bf43860be0d72b6c639a80939b600b460,
  ea104f2e3c35814368edfe0d236f58dff14a188f, and
  3d0facdcfdcea9648f0115ccadc35f291d3a6612
• owner author and committer, exactly one DCO trailer, exactly one SSH
  signature, local verification status 0
• exactly three 2026-09-10 occurrences and zero remaining 2026-09-09
  occurrences in the three changed files

Gate evidence from this commit

• Release metadata checker: release metadata is internally consistent for 0.1.5 (released 2026-09-10) and release metadata is tag-ready for v0.1.5 on 2026-09-10.
• Focused release-control selectors: seven of seven passed, zero failures,
  errors or skips.
• Ruff on tests/test_release_controls.py: clean.
• git diff --check: clean. Pinned content and attribution scanners: clean
  over 200 blobs, over the tree, the commit, and the base-to-head range.
• just setup: succeeded.
• just release: status 0 with all fifteen stages in order, 44 conformance
  vectors, 23 capability claims at 18 implemented, 2 out-of-scope and 3
  partial, stdlib-only runtime, reproducible distributions, exact-byte
  distribution structure, and installed-wheel behavior verification.
• Built-wheel real-client MCP exercise from this build: the wheel was installed
  alone into an empty environment, a project was initialized, and the reference
  MCP SDK connected over stdio. The negotiated protocol revision was
  2025-11-25, tools/list returned all four tools, and one continuity_check
  call returned real content with isError: false.

The MCP application result was conclusion: "failure" with the sole verifier
gap policy:proof-required-without-required-verifiers. That is the expected
policy state of a fresh empty project. The exercise proves a successful
protocol and tool-call round trip, not a successful continuity verdict. The
project's canonical SQLite iterdump digest was identical before and after the
session; that is equality of a logical serialization, not byte identity of the
database file.

Scope and protected paths

Protected-path intersection: empty. None of CHANGELOG.md, CITATION.cff, or
tests/test_release_controls.py matches any of the advisory's twelve protected
pathspecs. No content-integrity-policy-change label is requested or required.

Release boundary

• 2026-09-10 is the owner's directly selected real release date, recorded
  with trusted_time:false.
• No release has occurred yet: there is no v0.1.5 tag, GitHub Release, or
  published package at the time this body was frozen.
• The clean-main release gate and the real-client MCP exercise will be
  repeated from a dedicated checkout at the merged commit before any tag is
  created.
• Local distribution hashes from this branch are rehearsal artifacts. The
  squash commit will have a different identity, so the built bytes can differ,
  and they are not release assets.