[EHotwagner]

Refs #5097, Refs #4730. Route rebind for coherent 0.114.1, authorized by programme decision 6 (#4730) and admitted by Root. Pattern: #5034 (0.114.0) and #4833 (0.113.0). Reversible source composition only: no candidate, preflight, publication, main hold or installation is selected.

Why. Directory.Build.props already says 0.114.1 (#5110), but release-successor-candidate.yml still has test "$version" = 0.114.0, predecessor 0.113.0 and absence checks for the published v0.114.0, and CURRENT_RELEASE is the consumed 0.114.0 journal. A candidate on main would refuse. The follow-up that removes this per-release step is #5156 (derive the route from the version bump).

Change.

• Candidate workflow: version 0.114.1, predecessor 0.114.0 (coherent-set/v0.114.0, source 3c13e67f56de25041c6a5f9de85c54d178134956), absence of coherent-set|kit|drivers|coord-engine/v0.114.1, both uniqueness checks.
• CURRENT_RELEASE: 0.114.1 over 0.114.0, predecessor content sha256:250a010e27ebcc43007ea72bbdf01fddbabc45c2a85feabde3268d095d91d01c (read from the promoted release's stable-channel.json), fresh journal coord1141-board-reader-20261101-01 (ref and directory).
• Feed-readiness default/choice coherent-01141-absence; Host observer CHOICES; the three tests that pin them; the 0.114.0 fixture receipt (promotedAt 2026-10-31T15:54:06.802607Z from the same channel file).
• Consumed 0.114.0 journal coord114-enrollment-context-20261031-01 added to the prior-journal refusal list, with test_current1141_cannot_initialize_consumed114_journal (recovery suite 207 tests).
• PackageReleaseNotes: one added line for plan-only board-v2 tend (coord: board-v2 tend plan-only with batched read-only reads, rule C1 and a measured live run (Refs #5136) #5155), which merged after the notes were finalized. Nothing else in the notes changed (5,350 of 35,000 characters; first token still the version).
• Roadmap: coherent1141 window section.
• Fixture rule (skills: fixtures and release controls derive dates and versions from observed state (Refs #5109) #5110): these are the controls' declared subjects, a pin checked against its authoritative source (the promoted channel file), not ambient hard-codes.

Checks run (clean tree, exact head). tests/release-successor-candidate, release-successor-recovery (207, 2 skipped, OK), release-successor-journal, telemetry-host-published-org-read, release-effect-sealing, release-source-closure, telemetry-host-successor, engine-release-notes 32/0, coherent-set-version 13/0, check-engine-release-notes, check-publication-writer-coverage --local 0 unmet, check-paths-coherence: all OK. Not run: the candidate, the live-feed uniqueness check, the hosted engine job.

Still owed. Candidate, publish=false preflight, publish=true, readback and fdev install each need their admission; this release is the first real exercise of #5107 and #5108.

🤖 Generated with Claude Code

[EHotwagner]

Root/fdev, a proportionate review. This is the same mechanical rebind as #5034. It sets the version to 0.114.1 over the promoted 0.114.0, gives the journal and feed-readiness choice new names, pins the consumed 0.114.0 journal as refused, and updates the tests and the release-notes line for #5155. The route logic is unchanged. Approved. #5156 removes the need for this PR in future. Refs #4730