Repository navigation
fix\(harness-ops\): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker - part 1 of 2 #13289
Description
Part 1 of 2 of #13286, split at intake (owner Q93). The done-when below is copied from #13286 as written.
Done when
- Every FIX and CODE row the recheck recorded is fixed on
main, or its pull request records it as holding or not fixed, with the reason. - A line that restated a wrong volatile value states our decision with a pointer, as-of date and recheck trigger, per
.claude/rules/skill-bodies-state-current-rules.md, rather than a new restated value. - No pull request here loosens a permission, a guard or what an agent may do unattended.
- A behavior change carries a test that fails on the old code, or, for skill text, says what covers it. Named behavior changes:
/bugs:scangates always pass aneffort(their variant's, or the session's level when that is higher, or the session's level with no role map), and its run metadata labels an omitted effortunsetinstead ofsession, because the skill cannot see which model a spawn lands on.
Metadata
Metadata
Assignees
Type
Fields
Work status
agent-ready
Activity
github-actions commentedon Nov 4, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
I understood this as part 1 of 2 of #13286, split at intake. It asks for the docs-conformance fixes from the 2.1.297..2.1.318 recheck to land on main. It also asks for the changelog marker to move, and for a test or coverage note on each behavior change, including the
/bugs:scaneffort handling.The recheck's FIX and CODE rows are recorded on the parent, not here, so the work starts by reading them there. #13290 is the sibling part 2 of 2. It covers the other half of the same work, so it is not a duplicate.
Automated triage, applied by the lanes App.
github-actions commentedon Nov 4, 2026
kyle-sexton commentedon Nov 4, 2026
kyle-sexton commentedon Nov 4, 2026
Status. Parked at
status: confirmed, out of the issue lane, so it does not duplicate work already in flight.Agent choice, not an owner answer.
Laptop Lane 7 owns the parent #13286 (its trusted spec) and is building the groups as one pull request each: #13271, #13282 and #13283 are open with
Refs: #13286. GitHub Support has asked Lane 7 to post on #13286 which groups its pull requests cover and which parts the lane may take; a part released by that post goes back to the lane then.kyle-sexton commentedon Nov 4, 2026
Done. Every FIX and CODE row of the recheck is fixed on main or recorded with its reason, in the six merged fix PRs: #13269, #13271, #13278, #13282, #13283, #13288. Rows not fixed, with reasons, are listed in #13283 and #13314. The /bugs:scan behavior change is in #13271.