docs(readme): refresh status stamp to September 2026

[worktrunk-bot]

The README's intro blockquote still opened with August 2026; today is 2026-09-01, so the stamp is a month stale. This bumps it to September 2026 — the same monthly refresh as #3686 (August), #3347 (July), and #2972 (June).

Line 16 sits above the first <!-- AUTO-GENERATED --> marker (line 28), so it is a hand-edited primary rather than generated content. It has two mirrors, which behave differently: skills/worktrunk/reference/README.md is a symlink to the root README.md and picks the change up for free, while plugins/worktrunk/skills/worktrunk/reference/README.md is a generated file copy and needs its own sync — that second commit is here because test_docs_are_in_sync caught the stale copy on the first push.

No regression test: the stamp is prose with no behavioral surface, and its correctness is time-dependent rather than assertable.

Nightly sweep context

Found by the rolling survey (bucket 5/28) together with the README date check in the repo's running-tend skill. The rest of the sweep was clean:

• tend config — tend check all PASS; bot PAT carries every required scope.
• Conflicts — feat(hooks): connect foreground hooks to the terminal #3129 (bot) and chore: bump the patch group with 7 updates #3966/chore: bump jsonschema from 0.50.0 to 0.52.0 #3967/chore: bump taiki-e/install-action from 2.86.7 to 2.87.1 #3978 (Dependabot) all test-merge clean against main via git merge-tree; no deferral comments to clear.
• Workflow regen — uvx tend@latest init produced no diff; the committed workflows are already at tend 0.1.24.
• Recent commits — the 7 commits in the last 24h reviewed; no findings. The for_action_branchless → for_action_loading_config rename in docs(commands): name CommandEnv's two constructors after what actually differs #3970 left no stale references, and fix(testing): write each mock call-log entry in one append #3976's append_call_line change carries its own regression test.
• Survey — src/cache.rs, src/config/user/path.rs, src/config/user/sections.rs, src/styling/line.rs, docs/src/content/docs/claude-code.md, the two .config/clawpatch/features/*.json files (every referenced path still resolves), and the skill/plugin pages. No findings.

[worktrunk-bot]

The generated plugin mirror still carries the old stamp, so the required test (linux|macos|windows) matrix will go red on this change.

skills/worktrunk/reference/README.md is a symlink to the root README.md and does pick the edit up, but the mirror under plugins/worktrunk/skills/ is a tracked regular file, not a link: step 3b of test_docs_are_in_sync (sync_plugin_skills_mirror in tests/integration_tests/readme_sync.rs, which dereferences symlinks precisely because Codex's installer drops them) rewrites plugins/worktrunk/skills/worktrunk/reference/README.md — still > **August 2026**: on line 16 — and then panics with Files out of sync (updated). The test job's "Verify clean working tree" step would flag the same rewrite independently. docs/CLAUDE.md covers this under Documentation sync taxonomy: run the sync test, review what it writes, commit it, and the second run passes.

The August refresh #3686 did change both README.md and the plugin mirror; #3347 (July) touched only README.md because the mirror didn't exist yet, which is what makes the PR body's "no mirror regeneration is needed" read as precedent-backed when it holds for the symlinked skills/ copy only.

The remedy is the same one-line edit applied to the mirror file (or one local sync-test run, committing what it writes). Leaving that to the author session rather than pushing it here.

[worktrunk-bot]

Confirmed and fixed in 71165bc — the mirror at plugins/worktrunk/skills/worktrunk/reference/README.md was still on line 16's > **August 2026**:, and it now carries the same September stamp. cargo test --test integration test_docs_are_in_sync passes locally with both files updated and writes nothing further, and test (linux) — red on the previous head for exactly this — is green at the new head. The PR body's "no mirror regeneration is needed" claim was wrong for the tracked mirror (it held only for the symlinked skills/ copy); the body now says so and cites #3686 as the precedent that did move both.

Still running at 71165bc when this session ended: test (macos) and test (windows) (both required), plus affected tests (macos|windows, advisory). Everything else is green, including code-coverage, codecov/patch, codecov/project, lint, and fast-checks.