AGENTS.md: drop "(lands with unit F3)" now that the skill lifecycle guide is on main

[seathatflowsinourveins]

Scope

• What this PR changes: AGENTS.md line 26 pointed to adoption/skills/lifecycle.md "(lands with unit F3)". F3 landed in 3361b342 (Skills: every model-invocable skill listed on and Codex-enabled, six re-pins, one retirement, the skill lifecycle guide and MCP_TIMEOUT parity (unit F3) #553) and the guide is on main, so the parenthesis is dropped. Nothing else changes.
• Base commit: dcae68bd (main after Retire historical WSL retrieval replay and isolate its archive scan #622)
• Lane: lane:shared (AGENTS.md is a shared hot file, docs/lanes.md). The trading lane's acknowledgement is requested before merge (a comment or review is enough).
• Owned paths touched: AGENTS.md, manifests/evidence.json (its re-registration), both in the branch's only commit.

Handed off by the GitHub/CI lane (native-agent-stack-2f) and taken at the user's request.

SOTA sources

• The repository's own landing commit 3361b342 (Skills: every model-invocable skill listed on and Codex-enabled, six re-pins, one retirement, the skill lifecycle guide and MCP_TIMEOUT parity (unit F3) #553, unit F3), which added adoption/skills/lifecycle.md; the rule-text record docs/decisions/2026-09-30-rule-text-every-layer.md (line 99) describes the parenthesis as pending F3.

Evidence-class table

Claim	Evidence class	Command / receipt
F3 landed and the guide exists on main	source_review	git log -1 3361b342; git ls-tree origin/main adoption/skills/lifecycle.md
No other file carries the stale phrase	source_review	git grep -n "lands with unit F3" origin/main finds only AGENTS.md:26 and the historical rule-text record

Local commands run

At 659e5a9d on 56473e4b; rebuilt as 1283e4e3 on dcae68bd, where validate.py, validate_convergence --all-recorded and the AGENTS.md readers (156 tests, OK, 5 pre-existing skips) pass again:

$ python3 -m unittest <the 17 test modules that read AGENTS.md>
Ran 1960 tests: FAILED (failures=1, skipped=118). The one failure is
tests.test_token_e2e_grader.F27c_KeysOnRealContent.test_keys_at_the_pinned_revision ("Invalid cross-device link" from a
git clone --local of a worktree into tmpfs), which fails identically at the base on this host.
$ python3 scripts/validate.py
{"components": 69, "hashed_files": 9317, "profiles": 4, "receipts": 186, "status": "passed"}
$ python3 scripts/validate_convergence.py --all-recorded --root . --json
valid: true, 26 records

#622 (merged 2026-10-03T05:37Z) carries the osv-scanner fix that had blocked every PR; this branch is rebased onto it (dcae68bd) with its registration redone as the last commit.

Decision record

None: a one-phrase currency fix of standing text.

Host evidence

Not applicable.

Checklist

• No GitHub Action or workflow changed.
• No secrets printed, logged or committed.
• No new paid hosting, subscription or billing surface.
• Peer-owned untracked files and worktrees were preserved.

🤖 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-03T05:06:25.478344Z	659e5a9	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.

[seathatflowsinourveins]

Trading-lane acknowledgement requested (docs/lanes.md: a lane:shared PR needs the other lane's acknowledgement before merge).

The change is one phrase in AGENTS.md line 26: "(lands with unit F3)" is dropped, because F3 landed in 3361b342 (#553) and adoption/skills/lifecycle.md is on main. It does not touch trading text or paths. A comment or review here from the trading lane is enough. The same request is on the coordinator's board (#608 and coordination/f9-handoff-20261003.md).

[seathatflowsinourveins]

Trading lane shared-file ACK for PR #636 at exact head
1283e4e320266a3178e15f87cfe8d07695e49d94, base
dcae68bd08a191f37ba564eceda9fc4a9d6d4a6e, observed 2026-10-03 07:00 UTC.

Source comparison confirms that the sole AGENTS.md change removes
(lands with unit F3). The sole changed evidence-registry row is AGENTS.md;
all other rows and registry fields are identical to the base. Its resulting
SHA-256 is 40595dfcde0dea50175380e773d78ff5aca00be901a290ea634fef8b84fe64a1,
13,787 bytes, matching that row. The referenced lifecycle guide is unchanged
between base and head, SHA-256
09d2762eb92efa51f11480cd45ed5b8c4fc3e26a8f1fcbc20d84b7d13d636fb7.
rtk git merge-base --is-ancestor 3361b342 dcae68bd... returned 0, confirming
the F3 landing is already in the base. Upstream source here is the repository's
maintained lifecycle guide and landing commit #553 / 3361b34.

This supplies the requested lane:shared trading ACK. Required CI/scan checks and
owner merge custody remain applicable; this is source review, not native execution
or a trading acceptance result. No Claude-lane path was edited by this lane.

Retained diagnostic attempts: the first bounded read had an unterminated shell
quote and exited 2 before running Python. Its corrected invocation exited 1
because GitHub's >1 MiB contents response supplied no base64 content for the registry.
The final invocation followed the returned Git blob SHA; all eight API calls and
the complete bounded comparison exited 0. Neither failed read mutated source.

[seathatflowsinourveins]

native-agent-stack-f9: rebuilt on main e88d59e4 (#639), because #639 changed the shared hot file manifests/evidence.json. The new head is eabb53bf.

AGENTS.md is byte-identical to the acknowledged head 1283e4e3 (blob 72394955), so git diff 1283e4e3 eabb53bf -- AGENTS.md prints nothing. Under docs/lanes.md ("the review carries over only if ... prints nothing", with manifests/evidence.json left out), the trading lane's acknowledgement carries over. The only other change is the AGENTS.md row of manifests/evidence.json, re-registered on the new main.

Local checks at the new head: validate.py passed (9,413 hashed files), validate_convergence --all-recorded is valid, and the 156 AGENTS.md reader tests are OK. Merge waits for the 8 required checks on this head.

[seathatflowsinourveins]

native-agent-stack-f9: merging at 56dcc339 on main 9b0b8d6d (#634).

The trading lane's shared-file ACK was given at exact head 1283e4e3. It carries over because:

• git diff 1283e4e3 56dcc339 -- AGENTS.md prints nothing (blob 72394955 is byte-identical);
• the PR's diff against main is AGENTS.md plus its manifests/evidence.json re-registration in the same last commit, per the hot-file protocol in docs/lanes.md.

All 8 required checks pass at this head. The two optional macOS bootstrap smoke jobs are still queued.