Release CodeStory 0.17.4 from dev/codestory-next

[TheGreenCedar]

Outcome

Publish CodeStory 0.17.4 as a native release from the current dev/codestory-next integration line, with every release surface synchronized to 0.17.4.

Scope

• bump every codestory-* workspace crate and Cargo.lock entry to 0.17.4
• bump the model producer version and all host plugin manifests to 0.17.4
• pin the managed CLI to v0.17.4 and leave the native source pin archive-less
• promote the existing Unreleased Cursor fixes as the 0.17.4 release notes
• run the canonical source stabilization, bump-then-calibrate freeze, qualification, dev-to-main promotion, publication, marketplace delivery, installed-runtime, and live project-scoped proof lanes

Acceptance

• canonical release validator and workflow policy pass on the bumped source head
• exact-head source stabilization succeeds and is reusable
• calibration runs on the bumped tree and the sole constant-set freeze commit is accepted
• frozen-candidate qualification succeeds for the selected native claim
• dev/codestory-next is promoted to main through the required same-repository PR
• GitHub release v0.17.4 and native assets exist
• marketplace delivery state is verified
• normally installed CodeStory reports the intended plugin and CLI versions and project-scoped MCP reaches ready/full retrieval

Boundaries

This release does not close or claim completion of the unfinished v3 epic or its remaining child issues. Their current dark source remains governed by their own acceptance criteria.

Refs #1973.
Refs #1974.
Refs #1977.
Refs #1978.

[TheGreenCedar]

Source candidate frozen

• version: 0.17.4
• dev head: 09f3d0d
• tree: ea7e0754308170534a6ed0e9ace906882024fcdb
• current main: 7d496b7
• promotion PR: Release CodeStory 0.17.4 #1986, draft
• source PRs in this wave: [codex] run Cursor marketplace MCP as the Node main module #1970, [codex] align MCP output schemas with Cursor-validated payloads #1972, [codex] build the v3 compatibility harness #1979, [codex] add the dark call path proof kernel #1980, [codex] prepare CodeStory 0.17.4 #1981
• next proof target: exact-head source stabilization

The selected release excludes future source from #1974, #1977, and #1978. Any source or workflow commit added to dev after this point invalidates the candidate and every queued or running proof for it. The unrelated dirty primary checkout and active #1974 worktree remain untouched.

[TheGreenCedar]

0.17.4 source candidate replacement

The first source-stabilization run (32486607908) passed hostile mutations, retrieval generalization, Windows native contracts, and the protected Windows native probe, then failed the full source gate on Rust 1.98 clippy. That candidate is invalidated.

The complete mechanical compatibility fix is now pushed through PR #1988:

• head: 82d4128cef685ddf4e5d325de199bffeadd369df
• tree: 2edd19b297bd5ce52e4aea2ea935f55821de056e
• local Rust 1.98 workspace all-target/all-feature clippy: passed
• focused decoding, vector validation, clause-guard, and citation-capping tests: passed

No version or generated calibration constant changed. The next permitted mutation is the exact-head source-stabilization dispatch for PR #1988. Future work in #1974, #1977, and #1978 remains outside this release candidate.

[TheGreenCedar]

0.17.4 calibration-source correction

Source proof run 32488871024 fully accepted parent head 82d4128cef685ddf4e5d325de199bffeadd369df. Calibration run 32490274023 then stopped at preflight because the source still carried the previous release's frozen calibration record. No protected calibration measurement ran.

The required one-file unfreeze is now pushed through PR #1988:

• head: 30eafeb4dacaf57a350def2a3512f3dc56f747dd
• tree: cd992e4cd6040e1d042473aee7b07fc08a4dfbc0
• changed file: crates/codestory-llama-sys/per-user-embedding-server-constant-set.json
• state: unfrozen, freeze_record: null
• all runtime constants and thresholds: unchanged
• release version validator and workflow policy: passed

The parent acceptance and calibration receipt are invalidated. The next permitted action is source stabilization on this exact head, followed by calibration. After calibration, the only permitted file mutation is the generated constant-set freeze.

[TheGreenCedar]

0.17.4 candidate updated to current dev

PR #1989 merged into dev/codestory-next at 6f6e6b2a1c8aceb5a3e585ab40b6f8df20bf3e30 while source proof 32490514283 was running. The release-freeze invalidation workflow correctly canceled that obsolete proof; the apparent Windows cancellation was caused by this dev movement, not a source-contract failure.

PR #1988 now contains current dev and the release work:

• head: be68b7e8f8ca32d2a7d6a7190c7b5c47429afc00
• tree: 685b39cc4e0112fcf220b622bbba16ad69911328
• current dev is an ancestor
• all release surfaces remain 0.17.4
• constant set remains correctly unfrozen for calibration
• integrated Rust 1.98 workspace all-target/all-feature clippy: passed
• release-freeze invalidation for this PR update: completed

There are no other open PRs targeting dev. The next permitted action is source stabilization on this exact head.

[TheGreenCedar]

0.17.4 source stabilization restarted on the final integrated source head.

• Release PR: [codex] make CodeStory 0.17.4 Rust 1.98-clean and freeze it #1988
• Candidate commit: 53e14010cef259caecec15b1403cfac59498a588
• Candidate tree: eed7cc771453a850fba4273a59fe15285048f6b2
• Current dev: d7a1da54042c368f3f11b61571326be4c2a43ec2
• Included support PRs: [codex] run Cursor marketplace MCP as the Node main module #1970, [codex] align MCP output schemas with Cursor-validated payloads #1972, [codex] build the v3 compatibility harness #1979, [codex] add the dark call path proof kernel #1980, [codex] prepare CodeStory 0.17.4 #1981, [codex] add dark v3 packet projections #1989, [codex] remove repository-shaped packet rank bias #1990
• Automatic invalidation completed: run 32495046444
• Source stabilization: run 32495096018

All release surfaces validate as 0.17.4. The constant set remains unfrozen with no freeze record until protected calibration succeeds on this exact source head. Earlier source and calibration receipts are invalidated.

[TheGreenCedar]

0.17.4 source stabilization restarted on corrected exact head 1ef4447a4900c925592b93a90e4417e951a1d9d9 (tree cb8c82acf9e8ac2d9427ae4486891c9fc2353e51).

Run 32495096018 passed compilation, all-target/all-feature lint, hostile mutations, retrieval generalization, Windows source contracts, and 3,592 of 3,593 workspace tests. Its sole failure was an older runtime test asserting that collections/ paths must outrank neutral paths—the exact repository-shaped authority removed by merged PR #1990.

The correction deletes only that stale opposite-contract test. Production neutrality integration tests pass 2/2, both runtime replacement guards pass, full Rust 1.98 clippy passes, and every release surface remains 0.17.4.

• Automatic invalidation: run 32497350439, passed
• Corrected source stabilization: run 32497379642, running

All earlier source and calibration receipts remain invalidated. The constant set remains unfrozen until protected calibration succeeds on this exact head.

[TheGreenCedar]

0.17.4 qualification exposed a macOS proof-harness defect after authenticated Metal execution had succeeded: an exited-but-unreaped process remained present as a zombie, proc_pidinfo stopped returning its exact start identity, and the waiter correctly refused to infer exit from unreadability alone.

The corrected source head is 9f982d76cb47b45805a29982cdeae670684ca72a (tree 442e70b55c83c709b14a322515e54a33ddac04be). It adds an explicit, fail-closed macOS Z-state observation before start-identity inspection and preserves unknown/unreadable states as failures.

• Native macOS reproduction before: ps_state=Z, waiter rejected the still-present PID as unreadable.
• Native macOS reproduction after: ps_state=Z, exited=true.
• Packaged-proof self-test: passed.
• Adversarial process-identity review: no deterministic counterexample; parser, liveness, compile, and fail-closed probes passed.
• Release surfaces: still synchronized at 0.17.4.
• Invalidated: source run 32497379642, calibration run 32498872287, frozen acceptance 32499273186, qualification 32499705940.
• Superseded qualification: force-cancelled after its protected Windows step did not acknowledge ordinary cancellation promptly.
• Automatic freeze invalidation: run 32503480638, passed on rerun.

The constant set is restored exactly to the pre-calibration source state (unfrozen, no freeze record). The next proof target is source stabilization on this exact head, followed by three fresh protected Metal calibration runs.