Repository navigation
docs: cut restated upstream behavior left by the stamp sweep (playbooks) #15509
Description
Problem
The stamp sweep in #15461 (docs: drop stamps from pointer records (playbooks)) found these passages restating upstream behavior. Under contract 6.0.0 (#15468) restated behavior is not stamped; it is cut to a pointer or rewritten as this repository's own rule. The sweep left them unchanged because cutting them changes what a skill tells the agent.
Items
The prose below is kept and its stamp removed. A later change should cut it.
skills/boris/reference/orchestration.md~L53, ~L60, ~L68, ~L75: paraphrase the blog's failure modes, the dynamic-versus-static argument, the six patterns and the use cases.skills/boris/reference/autonomy.md~L354: paraphrases how/goalchecks its condition.skills/boris/reference/loops.md:17,:30: paraphrase the goal docs (no turn cap; a bare/goalshows spend).skills/boris/reference/foundations.md~L193: paraphrases whenPostToolBatchfires.skills/boris/reference/customization.md~L18: paraphrases which terminals take Shift+Enter.skills/boris/reference/adoption.md:10: paraphrases the thread's guardrails.skills/boris/SKILL.md:82: restates the Ultracode toggle on/effort.skills/skill-authoring/reference/precompute-context.md~L60-61: paraphrases the permission-checks section (a refused command aborts the skill load).skills/skill-authoring/reference/skill-criteria.md:13-15: paraphrases the prompt audit's cruft criterion.reference/model-adaptation/opus-4-8.md:148,sonnet-5.md:158: paraphrase the Fable guidance on over-prescription.reference/model-adaptation/sonnet-5.md:51-52: paraphrases the effort page saying the scale is set per model.skills/fable-5/context/verification.md(the Managed Agents automation record): restates the blog's re-check and delivery checks. It keeps its stamp for the command string.skills/fable-5/context/context-economy.md:22: restates thekeep:"all"behavior.skills/repo-sweep/scripts/state.sh:39,tick.sh:22: describe jq.exe text-mode stdout on Windows.
Kept, unsure
skills/skill-authoring/SKILL.md:34: the post's 9 category names and tip titles are strings copied from the post. Whether a whole-skill restatement counts as a stored value is unsettled.- Sources read dates that have no figure beside them. They are a read log rather than a stamp form:
opus-4-8.md~L150-152haiku-5-5.md:244,:246sonnet-5-5.md~L286, ~L289sonnet-5.md:183-186opus-5.md:185
Kept, no anchor checked
skill-criteria.md:387prompt-caching.md:43haiku-5-5.md:208sonnet-5-5.md:264
Out of scope
lib/prerequisites.{sh,mjs} and scripts/fetch-docs.sh are shared copies of the root lib/ canonicals.
docs/contracts/upstream-drift/README.md:152-156 still asks a "no docs page covers" record to keep its date. That text predates D26, which overrides it, so the contract needs its own follow-up.
Do
Per item: cut to the anchored pointer, keep as our own rule with its reason, or record why it stays. A cut that changes agent behavior needs an eval or a stated basis.
Activity
github-actions commentedon Nov 12, 2026
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: a docs cleanup for the playbooks plugin. It lists passages left by the stamp sweep (#15461) that restate upstream behavior. Under contract 6.0.0 (#15468), each should be cut to a pointer, rewritten as this repository's own rule, or recorded as intentionally kept. The issue names the files and items and says what to do with each, so nothing is missing. Where a cut changes what a skill tells the agent, it needs an eval or a stated basis. The sibling "stamp sweep" batch issues cover other areas, so I don't treat them as duplicates. I found no merged pull request that already fixes this.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 12, 2026
Not admitted to the issue lane: no trusted-human acceptance criteria: a listed human must put the confirmed
- [ ]criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Nov 12, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: Each listed passage in the playbooks plugin is cut to its anchored upstream pointer, rewritten as this repository's own rule with a reason, or recorded as intentionally kept.
Related work
Open questions
RECOMMENDED: Cut to the existing Pointer line where one already sits under the prose (orchestration.md sections 81-84 each have one). Keep as own rule only where the text carries a repo-specific instruction. Basis: plugins/playbooks/skills/boris/reference/orchestration.md:56-78
RECOMMENDED: Accept a one-line basis in the PR description naming the upstream page that still covers the behavior; require no new eval for pure pointer cuts. Basis: judgment
RECOMMENDED: Out of scope for edits; record each as kept with a reason, and file separate follow-ups for the unsettled stored-value question at skill-authoring/SKILL.md:34. Basis: judgment
RECOMMENDED: Yes, locate by content and the issue's description of the paraphrased behavior. Basis: plugins/playbooks/skills/boris/reference/foundations.md:190-209
Sources read
To answer, post a comment that starts with this line:
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.