[fdaviddpt]

/oss:doctor flagged .oss/README.md and .oss/statusline.py as drifted from the vendored oss 0.42.3 template. scaffold.py --apply re-synced them, plus three 01-oss rule files and vocabulary/01-oss/00-index.tsv.

These files are rewritten by every scaffold run, so nothing here is hand-edited. No issue to close: a doctor repair, not the fix for a tracked issue.

🤖 Generated with Claude Code

[AI-generated]

[fdaviddpt]

Maintainer review (tick wait+review step, skills/manager/phases/review.md):

Premise: /oss:doctor flagged drift between .oss/README.md/.oss/statusline.py and the vendored oss 0.42.3 template, plus three 01-oss rule files and vocabulary/01-oss/00-index.tsv out of sync with them. scaffold.py --apply re-synced all five. Sound premise -- per this repo's own CLAUDE.md ("vendored-oss.md"), everything under .oss/ and every 01-oss layer file is scaffold-owned and rewritten on every /oss:scaffold --apply; a hand-edit there is lost, so this PR's job is exactly "catch the tree up to the template," nothing more.

Blast radius: all 5 changed files are within that scaffold-owned set (.oss/README.md, .oss/statusline.py, two 01-oss rule bodies, vocabulary/01-oss/00-index.tsv) -- no 00-manual (hand-edited) file touched, consistent with "nothing here is hand-edited."

CI finding, now fixed: the one failing leg (fragment, job #112270873460) was the changelog-fragment gate: "No changelog fragment in this pull request... or label the pull request 'no-changelog' when the change is genuinely invisible to users." This change is exactly that case -- a mechanical re-sync of files the repo's own docs say are vendor-managed and never hand-edited, so there is nothing here for an end user of this plugin to read about in a changelog. Added the no-changelog label rather than writing a fragment describing a vendored-file resync. Re-run the fragment check.

Decision: content ready-to-merge, pending the re-run of the fragment leg now that the label is set.