Regenerate the final-stack manifest after #1018 changed one of its sources

[seathatflowsinourveins]

Scope

• What this PR changes, in one or two sentences: main is red because Move the claude-native-practice skill row to the commit that holds #1001, #1005 and #986 #1018 (791eab0) changed catalogs/landscape/skills-lifecycle.json after Generate the canonical final-stack manifest (W4 PR 2) #1007 (c2dee17) bound its sha256 in catalogs/landscape/final-stack.json. This commit is the generator's own --write output on main: one source hash and the manifest's evidence registration.
• Base commit: 791eab026438656ece68579bfbe4b04f0451c319
• Lane: lane:foundation
• Owned paths touched: catalogs/landscape/final-stack.json, manifests/evidence.json

SOTA sources

• The repository's own generator and check, introduced by Generate the canonical final-stack manifest (W4 PR 2) #1007: scripts/final_stack.py --write and --check at main 791eab0, run by .github/workflows/validate.yml:152-154 ("Check the final-stack manifest is current", shard 0). No new mechanism; the PR is generated output only.
• Merge skew between two individually green PRs is the failure class GitHub's merge queue exists to prevent (GitHub Docs, "Managing a merge queue"); the repository's interim control is the landing script's merge validation, which this incident shows must also run final_stack.py --check (CC follow-up below).

Evidence-class table

Claim	Evidence class	Command / receipt
Main fails the currency check	local_integration	python3 scripts/final_stack.py --check at 791eab0: "sources: catalogs/landscape/skills-lifecycle.json sha256 changed (7293ca6d2a0a -> b7bf21a3720c)"; hosted run 38184919849 (validate-shard-0 job 114605078077; shard 4 job 114605078040)
The fix is the generator's output only	local_integration	python3 scripts/final_stack.py --write rc 0 at 791eab0; diff = the skills-lifecycle.json source hash in final-stack.json and its registration in evidence.json (2 lines)
The check passes after it	local_integration	final_stack.py --check rc 0; validate.py passed; evidence_manifest.py --check passed (11,681 files); python3 -m unittest tests.test_final_stack Ran 72, OK

Local commands run

$ python3 scripts/final_stack.py --check          # at 791eab02
sources: catalogs/landscape/skills-lifecycle.json sha256 changed (7293ca6d2a0a -> b7bf21a3720c)
$ python3 scripts/final_stack.py --write
{"layers": 34, "status": "written", ...}   rc 0
$ python3 scripts/final_stack.py --check
rc 0
$ python3 scripts/evidence_manifest.py --check
{"files": 11681, "status": "passed"}
$ python3 -m unittest tests.test_final_stack
Ran 72 tests in 152.163s
OK

Decision record

None: generated output only.

Follow-ups

• The CC's landing script validates the merge onto current main with scripts/validate.py only; it must also run python3 scripts/final_stack.py --check (and any other generated-artifact currency check) on that merge, so a semantic conflict between two green PRs stops the second landing. CC correction, with a regression that fails before the fix.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-12T00:13:00.070846Z	e93cf46	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.