Repository navigation
docs: cut restated upstream behavior left by the stamp sweep (harness-config, harness-memory) #15512
Description
Problem
The stamp sweep in #15464 (docs: drop stamps from pointer records (harness-config, harness-memory)) 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
These passages paraphrase an upstream page. Their stamps are removed; the prose stays for a follow-up.
harness-config/skills/audit-instructions/reference/criteria.md:- :370, imports load at launch;
- :1364, the bare
ultracodekeyword; - :1453, a thinking-mode or
budget_tokenschange restarts the cache; - :1557, effort raises tool use;
- :1677, leading-thinking enforcement;
- :1977,
disable-model-invocationhides the description.
audit-instructions/reference/conflict-criteria.md:- ~180-183, Explore and Plan skip CLAUDE.md;
- ~297-299, PostToolUse cannot block;
- ~470-479, the precedence tables;
- ~655-657, dontAsk, deny and
disallowed-toolsremove the tool.
${…}resolution, in three places:audit-pass/SKILL.md:461-466,audit/SKILL.md:465andaudit-permission-grants/SKILL.md:196.audit-permission-grants/SKILL.md:214: a checked-in skill can grant itself tool access.audit/reference/audit-checklist.md:- :138-139,
skillOverridesscope; - :195, the
fallbackModelcap source; - :304,
/statusshows the managed source.
- :138-139,
audit-permission-grants/reference/criteria.md:267-273: parenthesis and trailing-text parsing.audit-permission-state/reference/criteria.md:425-435: the content-scoped ask caveat.audit-pass/reference/finding-identity.md:125-126: SARIF versioned fingerprints.audit-prompting-postures/reference/postures.md:59-63: Fable 5.2 self-review.setup/reference/wsl-profile.md:35-41: deny-rule limits.harness-memory/skills/audit/reference/official-guidance.md:282-291: the compaction table.harness-memory/skills/audit/reference/criteria.md:- :171-173, the listing-entry zero-cost rule;
- :229-230, the C5 rationale.
harness-memory/skills/stateless/context/desktop.md:15-22: the Help Center guided steps.
Kept, unsure
audit-instructions/reference/criteria.md:- about 39 I8, I10, I17-d, I23 and I27-I37 records kept their trigger as decisions about our own model scope. A strict behavior reading would remove those triggers too.
- :1155, the four-hop number is incidental to an AGENTS.md import trigger.
- :1644, I18's trigger watches the block-type set.
audit-pass/reference/finding-identity.md:46, :61, :179andsuppression.md:86: verbatim spec quotes, kept as copied strings.audit-permission-grants/reference/criteria.md:78: nested-skill discovery paths, read as a hardcoded list.audit/reference/required-permissions.md:286: copied strings beside a comparison with our own standards floor.harness-memory/skills/audit/reference/official-guidance.md:192: issue-state strings.- "Last updated" lines on our own criteria files:
harness-memorycriteria.md:11, which the update action bumps, andconflict-criteria.md:20. These are versions of our own files, not upstream stamps.
I30 record description (contract 6.0.0, #15468)
audit-instructions/reference/criteria.mdI30 Detect now says that a pointer record carries no stamp. A stored value, meaning a recorded number or string, carries an as-of date and a recheck trigger. I30's finding, a dated stamp with no trigger, applies to those. Behavior is unchanged:emit-findings.shand the tests do not cite the old wording.- The decision triggers kept in criteria.md (I8, I10, I17-d, I23, I27-I37) stay as named triggers on our own decisions.
Review thread
- Thread on stateless/reference/official-guidance.md, about the env-vars note "rows carry no section anchors". I replied with counter-evidence and resolved it. That note records no number or string, so under D26 it is not a stored value.
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: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: a docs follow-up to #15464 and #15468. Passages in harness-config and harness-memory that restate upstream behavior should each be cut to an anchored pointer, kept as this repository's own rule with its reason, or recorded as intentionally kept. Any cut that changes what a skill tells the agent needs an eval or a stated basis. The "Kept, unsure" list is for review only.
Nothing is missing. The choice per item is an implementation decision, not a primary-design question. Similar sweeps for other plugins are open (e.g. batches 5-7, playbooks, docs/), but they cover different files, so this is not a duplicate. I found no merged PR that already fixes it.
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 harness-config and harness-memory is cut to an anchored upstream pointer, kept as this repository's own rule with its reason, or recorded as kept, with a stated basis for any cut that changes agent behavior.
Related work
Open questions
RECOMMENDED: Cut to an anchored upstream pointer by default. Keep a passage only when it states a decision the repository owns, and give its reason in place. Basis: judgment
RECOMMENDED: Accept a stated rationale for cuts that only shorten text. Require an eval run for cuts that remove a trigger or detection rule from an audit skill. Basis: judgment
RECOMMENDED: Yes, locate by content under plugins/harness-config and plugins/harness-memory, since line numbers have moved. Basis: plugins/harness-config/skills/audit-instructions/reference/criteria.md:353
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.**.