docs: remove recheck triggers the stamp sweep left on pointer records

Problem

The Q11 stamp sweep removed as-of dates from pointer records but in some places kept the recheck trigger, leaving a trigger with no date. That matches neither form in upstream-drift contract 6.0.0 (#15468): a pointer carries neither, a stored value carries both. The contract already allows these leftovers to be removed "by a later sweep or on touch"; this issue is that later sweep. Reviewers flagged three on touch (#15502, #15503), which were fixed there.

Candidates

A heuristic, not a verdict: in each file a sweep PR changed, the count of Recheck trigger lines with no As of in the four lines above went up against main 35a9e39. Some hits may be a stored value whose date sits further up, a table column, or prose about triggers; judge each.

77 files (count of new hits, sweep branch):

plugins/user-interface/reference/principles.md (+2, ui-performance)
plugins/user-interface/reference/types/touch-web.md (+1, ui-performance)
plugins/user-interface/reference/types/web/typography.md (+1, ui-performance)
plugins/user-interface/reference/types/web/typography/line-behavior.md (+1, ui-performance)
plugins/user-interface/skills/glossary/reference/accessibility.md (+1, ui-performance)
plugins/user-interface/skills/glossary/reference/color.md (+1, ui-performance)
plugins/user-interface/skills/glossary/reference/interaction.md (+1, ui-performance)
plugins/user-interface/skills/glossary/reference/rendering-performance.md (+1, ui-performance)
docs/contracts/authoring-formats/README.md (+1, docs)
docs/contracts/execution-target/CHANGELOG.md (+1, docs)
docs/contracts/hook-observability/README.md (+2, docs)
docs/contracts/loop-lane/README.md (+3, docs)
docs/contracts/loop-lane/posting-lanes.md (+1, docs)
docs/contracts/routing-as-data/CHANGELOG.md (+1, docs)
docs/contracts/routing-as-data/README.md (+1, docs)
docs/contracts/standards/CHANGELOG.md (+1, docs)
docs/contracts/workspace-environment/CHANGELOG.md (+1, docs)
docs/plugin-philosophy.md (+12, docs)
docs/upstream/claude-dev-sonnet-5-5-blog.md (+1, docs)
docs/upstream/mattpocock-skills.md (+1, docs)
docs/upstream/opus-5-5-usage-guide.md (+1, docs)
docs/upstream/x-com-addyosmani-status-2117512471930167377.md (+1, docs)
plugins/harness-config/skills/audit-automation-gaps/SKILL.md (+1, harness-config-memory)
plugins/harness-config/skills/audit-instructions/context/report-keying.md (+1, harness-config-memory)
plugins/harness-config/skills/audit-instructions/reference/criteria.md (+40, harness-config-memory)
plugins/harness-config/skills/audit-prompting-postures/SKILL.md (+1, harness-config-memory)
plugins/harness-config/skills/audit-prompting-postures/reference/postures.md (+2, harness-config-memory)
plugins/harness-config/skills/audit/reference/required-permissions.md (+2, harness-config-memory)
plugins/session-flow/reference/off-thread-work.md (+1, batch5)
plugins/session-flow/skills/audit-sessions/SKILL.md (+1, batch5)
plugins/session-flow/skills/orchestrate/context/sources.md (+1, batch5)
plugins/source-control/reference/branch-update-criteria.md (+1, batch5)
plugins/source-control/reference/stacked-prs.md (+1, batch5)
plugins/source-control/skills/babysit-loop/reference/telemetry-upsert.md (+1, batch5)
plugins/source-control/skills/babysit-prs/reference/orchestration.md (+1, batch5)
plugins/discovery/reference/parent-contract.md (+2, batch6a)
plugins/review/agents/architecture-guardian.md (+1, batch6a)
plugins/review/agents/brief-reviewer.md (+1, batch6a)
plugins/review/agents/ci-log-auditor.md (+1, batch6a)
plugins/review/agents/code-reviewer.md (+1, batch6a)
plugins/review/agents/doc-drift-detector.md (+1, batch6a)
plugins/review/agents/security-reviewer.md (+1, batch6a)
plugins/review/skills/code-review/SKILL.md (+2, batch6a)
plugins/review/skills/explain-change/SKILL.md (+1, batch6a)
plugins/review/skills/fanout/SKILL.md (+4, batch6a)
plugins/review/skills/fanout/context/fix-pass-mode.md (+1, batch6a)
plugins/review/skills/fanout/context/run-everything-mode.md (+1, batch6a)
plugins/review/skills/quality-gate/context/code.md (+1, batch6a)
plugins/review/skills/quality-gate/context/pr.md (+1, batch6a)
plugins/review/skills/quality-gate/context/spec.md (+1, batch6a)
plugins/review/skills/security-review/SKILL.md (+1, batch6a)
plugins/work-items/skills/morning-brief/SKILL.md (+3, batch6a)
plugins/work-items/tools/work-item-tracker/CONTRACT.md (+2, batch6a)
plugins/code-tidying/skills/audit-dead-code/context/lanes.md (+1, batch6b)
plugins/code-tidying/skills/tidy-diff/SKILL.md (+1, batch6b)
plugins/disk-hygiene/skills/clean/SKILL.md (+1, batch6b)
plugins/disk-hygiene/skills/clean/reference/safety-model.md (+3, batch6b)
plugins/docs-hygiene/reference/config.md (+1, batch6b)
plugins/docs-hygiene/skills/audit-derivability/SKILL.md (+2, batch6b)
plugins/architecture/skills/map-components/SKILL.md (+1, batch6c)
plugins/architecture/skills/map-containers/SKILL.md (+1, batch6c)
plugins/architecture/skills/map-context/SKILL.md (+1, batch6c)
plugins/architecture/skills/map-data/SKILL.md (+1, batch6c)
plugins/machine-health/skills/audit/reference/windows/check-catalog.md (+6, batch6c)
plugins/context-guard/reference/reader-contract.md (+2, batch7a)
plugins/implementation/agents/scoped-implementer.md (+1, batch7b)
plugins/instruction-placement/skills/migrate/reference/sources.md (+1, batch7b)
plugins/instruction-placement/skills/realign/context/apply-recipes.md (+1, batch7b)
plugins/plugin-quality/agents/auditor.md (+1, batch7b)
plugins/context7/skills/lookup/context/lookup.md (+1, batch7c)
plugins/rate-limit-guard/reference/reader-contract.md (+1, batch7c)
plugins/attribution/skills/audit/reference/rubric.md (+1, batch7d)
plugins/naming/skills/name-it-better/context/sources.md (+2, batch7d)
plugins/overengineering/skills/audit/SKILL.md (+1, batch7d)
plugins/songwriting/agents/object-writer.md (+1, batch7d)
plugins/songwriting/skills/object-writing/SKILL.md (+1, batch7d)
plugins/speech/reference/elevenlabs.md (+1, batch7d)

Do

Per hit: a pointer record drops the trigger (and any "recheck when" clause); a recorded number or string gets its date back. Land after the sweep PRs merge, so the files are read on main.

Understood: the stamp sweep removed as-of dates from pointer records but left some "Recheck trigger" lines undated, which matches neither form in the upstream-drift contract (#15468). You want a follow-up sweep across the 77 listed files. A pointer record drops the trigger. A recorded value gets its date back.

The scope and the per-hit rule are clear. The work is docs-only but touches many files, so it will likely need splitting. The issue says to land it after the sweep PRs merge. Open issues #15509 to #15515 are related sweep follow-ups (cutting restated upstream behavior), not duplicates. They may touch the same files, so ordering matters.

_{Automated triage. A maintainer reviews it.}

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).

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: Every undated Recheck trigger line in the listed files is judged: removed where the record is a pointer, or given its As of date where it is a stored value, so each record matches one form of upstream-drift contract 6.0.0.

Related work

docs: cut restated upstream behavior left by the stamp sweep (user-interface, performance) #15510 (related): Sibling sweep follow-up for user-interface; may touch the same files.
docs: cut restated upstream behavior left by the stamp sweep (docs/) #15511 (related): Sibling sweep follow-up for docs/; overlaps the docs/ files listed here.
docs: cut restated upstream behavior left by the stamp sweep (harness-config, harness-memory) #15512 (related): Sibling sweep follow-up for harness-config; overlaps criteria.md and other harness-config files.
docs: cut restated upstream behavior left by the stamp sweep (batch 5) #15513 (related): Sibling sweep follow-up for batch 5; overlaps the session-flow and source-control files.
docs: cut restated upstream behavior left by the stamp sweep (batch 7) #15515 (related): Sibling sweep follow-up for batch 7; overlaps the batch7 files.
docs: fix retired docs slugs and unstamped recheck triggers found by the copied-content sweep #6498 (related): Earlier closed sweep for unstamped recheck triggers; precedent for the same fix.
docs: pointers carry no as-of date or recheck trigger #15449 (related): Closed PR that made pointers carry no as-of date or recheck trigger.
docs: drop stamps from pointer records (playbooks) #15461 (related): One of the stamp-sweep PRs this issue follows up.

Open questions

Should this be split into one run per sweep branch group (ui-performance, docs, harness-config-memory, batch5, batch6a-c, batch7a-d) instead of one 77-file change?
RECOMMENDED: Yes, one run per group, with harness-config criteria.md (+40 new hits) on its own, since one run cannot reliably judge that many hits. Basis: judgment
Have all the sweep PRs merged so the files can be read on main, and should this wait for sibling issues #15510-#15515 to land first?
RECOMMENDED: Wait for the sweep PRs and the sibling issues, because they edit the same files and the issue says to land after the sweep merges. Basis: 15510
Is the per-hit rule decidable by a run alone: how does it tell a pointer from a stored value when the record holds an observed behavior, table column or prose about triggers?
RECOMMENDED: Use the contract's test: a recorded number or string copied or measured from upstream is a stored value and gets its date back; anything else is a pointer and drops the trigger. Leave table columns and prose about triggers unchanged. Basis: docs/contracts/upstream-drift/README.md:90
When a stored value's date is restored, what date should be used, given the sweep removed the original?
RECOMMENDED: Recover the original As of date from git history of the sweep PR diff; if unrecoverable, re-read the source and stamp today's date. Basis: judgment

Sources read

docs/contracts/upstream-drift/README.md:117: a pointer carries no as-of date and no recheck trigger
docs/contracts/upstream-drift/README.md:123: a stored value adds an as-of date and a recheck trigger
docs/contracts/upstream-drift/README.md:645: at 5.0.0 pointer stamps are removed by a later sweep or on touch
plugins/harness-config/skills/audit-instructions/reference/criteria.md: 86 Recheck trigger lines in the checkout, so volume is large

To answer, post a comment that starts with this line:

**Decision recorded.** <answer>

_{Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.}

Navigation Menu

Repository navigation

docs: remove recheck triggers the stamp sweep left on pointer records #15521

Problem

Candidates

Do

Related

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

docs: remove recheck triggers the stamp sweep left on pointer records #15521

Description

Problem

Candidates

Do

Related

Activity

github-actions commented on Nov 12, 2026

melodic-automation-lanes commented on Nov 12, 2026

melodic-automation-lanes commented on Nov 12, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions