T002b: plan 038's second bookkeeping batch, T094 and T095 to T104, the identity response shape and the single-writer chains (plan 038)

[brettheap]

Lane: openxfactory-4 (openXfactory-4-openDox_extraction)

T002, second bookkeeping batch, plan 038: T094 and the slice entries T095 to T104, the identity response shape, the single-writer chains, and the ticks. Bookkeeping, so this PR carries no Arc: line. It touches no openspec/changes/ path, so no Rule 6 window applies. It began stacked on #1251's head; #1251 has landed (1837ea75) and main is merged in (543f6ce1), so the diff against main is this batch alone.

From plan 038's tasks.md, T002

• Task: T002, "Release-2 base, and the re-measure at the ruling" (landed in T002: release 2's base and plan 038's bookkeeping, items 1 to 15 (plan 038) #1251; this is its second batch of bookkeeping, the brief of the holder's T002b).
• Realizes: none (bookkeeping; FR-025). Falsifier: T002 names none. Its gates are the brief's, quoted under "Review and gates".
• Ruled / Decisions: none of its own. Every item is a ruling already posted on opensoft/openxFactory#656, or a landing already merged, encoded as worded and cited by comment id or merge commit.

The items

#	Where	What changed	Record
1	tasks.md: T094, T095 to T104, T073	T094 ticked, with its result quoted: 436 composed reds over 51 files, outside 12.5's set (Base 2; 533 at Base 1). The T095+ placeholder becomes ten entries, T095 to T104, each with its slice name, Files, After and Falsifier from R2-INV-R9's outline and the holder's rulings, Lane: 3 (openXfactory-3). T073's After and Files name them. The map's means, the rulings (R9-R1 (a), R9-R2 (a), W1 to W7) and the OQ defaults are recorded once, above the entries	map R2-INV-R9.md; 6021830607; claim 6021862323; rulings 6021830531
2	T095, T101, T104, T097	T095: the two confirmed departures from OQ-R9-1 (plane_host_for untouched, an autouse fixture registers the declared host; DECLARED_HOST_SUITES guarded structurally). T101: tests/declared_exclusion.yaml for ONE entry (reasons [doc_health], note dropped, the only list loses the file, count stays 66). T104: tests/test_binding_stylesheets.py, the pin 572 to 574. T097: its served-display respelling is R9-R1 (a) applied	6022291206; the T097 line is 6023517122 (the holder confirmed the citation, 6026622117)
3	plan.md: the single-writer table; tasks.md Files and After lines	W7's chains: tests/conftest.py T020, then T021 and T026 in landing order, then T095, T073, T074; tests/test_host_plane.py T020, T026, T095; declared_exclusion.yaml T101, T073, T074; the four T074 test files T103 then T074; the census T025, T104, T015, T016, T057 (the row splits, so test_web_boundary.py keeps its own chain). T015's and T074's After gain T104 and T103	6021830531, 6022291206
4	tasks.md: T072, T074, T075 falsifiers	The four folds of #1253, in the arc change's own wording: T072 asserts that ONLY CR, LF and CRLF split rows; T074's seam tests assert that an empty-seam read names the seam AND its registrar; T075's host-wiring test shows a leg declaring only SOME of the four seams refused, and a leg declaring the six and none of the four accepted; T074's protected-suite oracle computes 12.5's set as 12.5 does (git grep -l -e 'open-pr' -e 'open_pr' -e 'FakePullRequests'), from the pre-arc and the final tree, the floor of 16 on each, and takes the union	openxFactory#1253 to fc4fa0ff; Copilot 5427373153
5	spec.md FR-011; tasks.md T041	FR-011's JSON shape gains identity, emitted and bounded as openDox-spec's finding schema bounds it (no excerpt, text, content or quote key, no number, strings of at most 200 characters, {category, entry} for a pathless finding, {collided_id} for a collision). T041's falsifier gains a response-shape test asserting exactly that bound. The coverage row for FR-011 names T041. The serialized-size cap was already T041's at the base (T041's text says so, and T042 "stores what T041 bounds"), so nothing moved	holder 6018624750
6	tasks.md ticks	T011, T014, T021, T023, T025, T026 and T060 ticked, T070's tick gains #1253, and T002's own landing is recorded. Each merge commit was verified with gh pr view <n> -R <repo> --json mergeCommit (listed below)	the landings
7	tasks.md: T072	A Files line (src/opendox/lines.py, tests/test_lines.py); the Ruled line gains 6023517122: head_sha (a), its own public head_sha parity-tested against serve._head_of, serve.py untouched; the line split (a), doxbench_defaults.py untouched. Folding either private helper is recorded as unscheduled and optional, and is not scheduled	holder 6023517122
8	contracts/health-finding.md:91	The sentence reads: a stored identity makes a cross-run collision between STORED findings detectable; an exception-only finding is never stored; whether the engine reports it remains T046's concern. Nothing else on the line changed	holder 6018624750; Copilot 5433292692
9	plan.md; tasks.md	Copilot's three items at #1251's head 1eb8e9eb, accepted by the holder at its landing: (a) the pin and landing-order row for T073 names T005 and T095 to T104 as prerequisites, and T095+ reads T095 to T104 at the critical path, the lane table and the revision note; (b) the combined conftest.py and test_host_plane.py row splits, and the cross-lane summary gains T026 (and the other chains of item 3); (c) the same split in T020's, T021's and T026's Files lines	holder replies 4201056969, 4201057311, 4201057577; READY note 6026651962

The ticks, verified

task	pull request	merge commit	merged
T011	opensoft/openDox-code#92	09b8d44a	2026-10-06T19:15:55Z
T014	opensoft/openDox-code#93	a7a1c4d3	2026-10-06T22:23:06Z
T021	opensoft/openXdox-code#40	f70bc9c3	2026-10-06T19:07:10Z
T023	opensoft/openXdox-code#42	d45a0939	2026-10-06T17:45:33Z
T025	opensoft/openDox-code#91	84f8ed83	2026-10-06T17:33:31Z
T026	opensoft/openXdox-code#43	36bbef79	2026-10-06T22:35:40Z
T060	opensoft/openDox#20, the tag dox-v1.2 (tag object 58538ff3, on 6a9f4902), opensoft/openDox#21	6a9f4902, c7f75845	17:46:59Z, tag 17:58:45Z, 19:02:39Z
T070	openxFactory#1253 (T070b, added to its tick)	fc4fa0ff	2026-10-06T18:56:42Z
T002	openxFactory#1251 (its own landing)	1837ea75	2026-10-06T22:31:42Z

• T021 landed with Copilot r4199337845 an ACCEPTED LIMIT (holder READY note 6023492215); T021's entry records it.
• T025's entry says its 34 nodes are "quoted at T029"; that stays T029's, and the entry says so.
• T011's server node is T014's, as its own Falsifier says.

Skipped, because already present at the base: T020's and T024's ticks (#1251 item 13) and T004's tick (#1245, 260234b5), all confirmed with git show <commit>:<tasks.md> | grep.

T071 is NOT ticked. Brett's word, "Ratify it (Recommended)" (#656 6023375303), is recorded on T071's entry, but the change's ratification-record PR has not landed (no such PR is open or merged on opensoft/openxFactory at this writing). The box stays open.

Readings the holder accepted (6026622117), disclosed as the brief requires

• W7 omits T026 from the openXdox-code chains. The single-writer table keeps T026 where its own ruling (6016648451) puts it, and lane 3's claim (6021862323) says T026's PR lands before T095. So the conftest chain reads T020, then T021 and T026 in landing order, then T095, T073, T074; and test_host_plane.py reads T020, T026, T095, as W7 gives it with T026 added.
• R9-R2's last sentence ("If the re-scoped test runs alone, it leaves the declaration, and the count moves with it, as the declaration's own rules require") is recorded in T100 as worded. declared_exclusion.yaml is NOT added to T100's Files: the holder's file list at 6022291206 names it for T101 only.
• Edits outside tasks.md, ruled in scope as each item names its place: plan.md (items 3, 9), spec.md FR-011 (item 5) and contracts/health-finding.md:91 (item 8).

Other notes on where an item needed a reading

• Counting. The task count reads 90 rows: the placeholder T095+ is replaced by T095 to T104 (81 - 1 + 10).
• Plan 034's task numbers. The entries cite plan 034's T103 (doxBench R-4: sending a new turn silently discards a pending proposal #80, in T099's Host header) and plan 034's T086 (W2, in the rulings) as "plan 034's", because plan 038 now has its own T103.
• OQ-R9-3. The map did not measure the respelled gate-console and wheel-model skips; T097 and T103 say so, and the map's 127 passed and 5 skipped is quoted as the measurement.
• Counts of slices are copied in the map's own form (for example "16 nodes, and +5 on R9-R1 (a)"), not summed.
• T095's chain after T026. T095's After names T021 and T026, both landed.
• Not mirrored from the arc's 4.1: T075's falsifier gains the some-of-four refusal and the six-and-none acceptance, which T070b: fold Copilot's four items into realize-doc-health-direction-arc before the ratify word (plan 038) #1253 folded. The arc's two older refusals (part-way through the seams; at the column call) are not in T075, since T070b: fold Copilot's four items into realize-doc-health-direction-arc before the ratify word (plan 038) #1253 did not add them.
• T046 and T057 carry no response-shape falsifier for identity: item 5 names T041's.

Review and gates

• python3 scripts/validate-openspec-cli-pin.py --all, in the clone named openxFactory, at 691648c6: exit 0, Totals: 113 passed, 1 failed (114 items), 0 UNDISPOSITIONED failures. The one failure is the dispositioned add-chain-attestation finding, the same on main.
• openxFactory pytest. The full local run was stopped at about 44% at a coordinator drain, so it is NOT a result and is not claimed. The repository's own gate, pytest-suite in CI at 691648c6, completed SUCCESS (2026-10-06T23:32:38Z to 23:58:56Z).
• Doc-health, scripts/doc-health.py --single-repo . --as-of 2026-10-07, branch 691648c6 against origin/main 0992369a in the same clone: the two reports are byte-identical (sha256 ce17aadd6d96e484170e2ec4784e44972e33c7d1a6c65830ea14a1035f2ae976; Findings: 31 critical, 26 error, 69 warning, 20 info. New regressions vs previous report: 0.). So no new error.
• CI at 691648c6: all 14 check runs are SUCCESS (rollup SUCCESS): pytest-suite, merge-master-approval (the red inherited from main since Archive add-factory-mcp-conformance: realization #1243 → 92010d3e, packet closed #1252 was cleared by Advance the pinned decision core to fe9a6f5b91886e4f07296dc6a264deb345b1618f #1138), openspec-cli-pin, doc-health-py314, openxdox-consumer-gate, wallet-validation, clearing-dispatch-gate, signed-execution-chain-gate, former-id-arrival-gate, release-tag-gate, openreposhape-pin, the two lane-line runs and SonarCloud.
• main has moved to 0992369a since the last merge (543f6ce1). GitHub reports this PR MERGEABLE, and the ruleset is not strict, so main is not merged in again (a merge would restart the 27-minute gate).

Copilot at	verdict	findings	answered
691648c6 (final; review 5435686665)	Changes recommended	1 (thread 4201443690): T041's falsifier cannot verify what T046's health list --json and T057's HTTP route emit; the review summary adds that the new T095 to T104 collide with plan 034's task numbers cited unqualified at spec.md:662, spec.md:1222 and clarify-questions.md:437	accepted limit (#656 5988818366): plan-record accuracy, not a bypass, and the T041 placement is the holder's own instruction (item 5). Answered (4201487553) and resolved

1 thread, 0 unresolved. The holder ruled both points YES at 6027706377 and has them encoded in a THIRD batch, not here: the identity falsifier split across T041, T046 and T057, and the plan 034 references qualified. This PR therefore carries T041's wording as the brief gave it.

Files changed

• specs/038-opendox-document-tool-self-maintenance/tasks.md, plan.md, spec.md
• specs/038-opendox-document-tool-self-maintenance/contracts/health-finding.md

What is NOT done

• T071 stays open (its ratification record has not landed). No box of File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144 is ticked, and no task other than those listed is ticked.
• No scenario or spec delta beyond FR-011's JSON-shape bullet is touched, and nothing is under openspec/changes/. README.md is untouched.
• The T095 to T104 entries record the slices; none of their work is done here.

🤖 Generated with Claude Code

Summary by Sourcery

Record plan 038’s second bookkeeping batch, formalize the health response identity shape, and update repair-slice dependencies and completion records.

Enhancements:

• Record the second bookkeeping batch for plan 038, including the completed T094 map, concrete T095–T104 repair slices, updated dependency and single-writer chains, and verified task landings.
• Clarify the bounded identity field in the health JSON response contract and associate its response-shape coverage with T041.
• Expand the recorded falsifiers for line splitting, seam registration, host wiring, and protected-suite coverage.

Chores:

• Update plan and task bookkeeping to reflect completed work, landing commits, revised task dependencies, and the still-open T071 ratification record.

[sourcery-ai]

Reviewer's Guide

This bookkeeping-only PR updates plan 038’s task records to reflect the completed R9 measurement and its ten repair slices, verified landings, dependency and single-writer chains, folded falsifiers, and open T071 status; it also formalizes the bounded emitted identity field in the health-finding response contract.

File-Level Changes

Change	Details	Files
Expanded plan 038 bookkeeping with completed measurements, concrete repair-slice tasks, verified landing records, and updated dependency/single-writer tracking.	Replaced T095+ with T095–T104 and recorded T094’s 436-red map, slice ownership, falsifiers, dependencies, rulings, and lane assignments. Updated plan and task dependency tables for conftest, host-plane, census, exclusion, and T074 test-file writer chains. Recorded verified landing commits for T011, T014, T021, T023, T025, T026, T060, T070, and T002 while leaving T071 open. Added the folded falsifier requirements for line splitting, seam diagnostics, protected-suite coverage, and host-wiring behavior. Clarified task count, critical path, cross-lane handoffs, and the scope/readings accepted from review.	specs/038-opendox-document-tool-self-maintenance/tasks.md specs/038-opendox-document-tool-self-maintenance/plan.md
Defined the externally emitted health-finding identity response shape and aligned its task coverage and collision semantics.	Added identity to the FR-011 JSON response contract with bounded, string-only values and constrained pathless/collision forms. Extended T041’s falsifier and FR-011 coverage mapping with the response-shape assertion. Clarified that only stored findings participate in detectable cross-run identity collisions, while exception-only findings are not stored.	specs/038-opendox-document-tool-self-maintenance/spec.md specs/038-opendox-document-tool-self-maintenance/tasks.md specs/038-opendox-document-tool-self-maintenance/contracts/health-finding.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Copilot]

Copilot review overview

🟡 Changes recommended

Several falsifiers cannot enforce their stated behavior, and new task IDs make existing cross-plan references incorrect.

Review effort: Balanced
Findings: 1

Open (1)

• Move emitter assertions to the tasks that implement them · New

What changed in this PR

Records plan 038’s second bookkeeping batch and formalizes remaining execution contracts.

Changes:

• Adds T095–T104 repair slices, dependencies, and completion records.
• Updates single-writer chains and arc falsifiers.
• Defines the emitted identity response shape and collision wording.

File	Description
tasks.md	Adds slices, ticks, dependencies, and falsifiers.
plan.md	Updates writer chains and landing order.
spec.md	Extends FR-011’s JSON response shape.
contracts/​health-finding.md	Clarifies cross-run collision detection.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 days and 20 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[brettheap]

READY (holder, manual landing) at 691648c

Lane: openxfactory-4 (openXfactory-4-openDox_extraction)

Holder, at READY: T002 batch 2, plan 038's bookkeeping items 1 to 9 plus the ticks. Landed under plan 038's "lane openxfactory-4 lands every PR" (#656 6013547504).

• Gates at the head:
  • all 14 checks pass (rollup SUCCESS): pytest-suite, merge-master-approval, openspec-cli-pin, doc-health-py314 and SonarCloud among them;
  • the pinned gate exits 0, with 0 undispositioned;
  • doc-health is byte-identical to main 0992369a, with 0 new regressions;
  • the files are four under specs/038-…/, with no Rule 6 path;
  • 0 closing keywords.
• Copilot 5435686665, "Changes recommended", is ACCEPTED under 5988818366. Its finding: T041's falsifier cannot verify what T046 and T057 emit. The placement was the holder's own (item 5), and holder ruling 6027706377 splits the bound across T041, T046 and T057. Batch 3 (r2/t002c-bookkeeping-3) encodes that. The thread is answered and resolved.
• Next: batch 3 merges main after this lands.

[brettheap]

Lane: openxfactory-4 (openXfactory-4-openDox_extraction)

LANDED — lane openxfactory-4, 2026-10-07T00:30:06Z, PR #1257 → c70bdbd (opensoft/openxFactory main; plain gate)

Batch 2 landed; Copilot 5435686665 ACCEPTED under 5988818366, its refinement (6027706377) rides batch 3.