T002: release 2's base and plan 038's bookkeeping, items 1 to 15 (plan 038)

[brettheap]

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

T002, plan 038: release 2's base (evidence/r2-base.md), and plan 038's tasks.md bookkeeping, items 1 to 15. Bookkeeping and evidence, so this PR carries no Arc: line. It touches no openspec/changes/ path, so no Rule 6 window applies.

From plan 038's tasks.md, T002

• Task: T002, "Release-2 base, and the re-measure at the ruling". Record in evidence/r2-base.md every repository's main (research.md's R0 command), the box census, and PACKET_MERGE=94b6f7f1 for F11.1, with lane 3's composed re-run quoted against R2-INV-P4F's 174. README: links evidence/r2-base.md. After: T004. Lane: 4 (lane 3 for the composed run).
• Realizes: none (bookkeeping; FR-025). Falsifier: T002 names none. Its gates are the brief's, and are quoted under "Gates" below.
• Ruled / Decisions: T002 carries none. Part 2 encodes rulings already posted on #656, each cited by comment id, and takes no decision of its own.

Part 1: evidence/r2-base.md (new), linked from the README's feature-038 entry

Each figure is a command quoted with its output, or lane 3's measurement quoted and attributed.

• Every repository's main (the R0 command, run 2026-10-06T16:09:44Z to 16:10:31Z, and again at 16:26:12Z): openDox-code 34c20641, openXdox-code 56e1c238 (then c6d15b27, T020's Derive-possibles register merge 2026-07-24 #39, committed 16:10:44Z), openDox d77f8cbf, openXdox 9564d5d9, openDox-spec 7db9438b, openXdox-spec f088b097, openxFactory 51456835, xFactory 1047586d, codexFactory 563212a1. The file gives each full SHA with its commit date and subject, against the R0 values of plan time, and what moved.
• The box census: plan 034's box_census.py over File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's tasks.md at 51456835 reads total 125 Counter({'x': 74, ' ': 42, '~': 9}). At ce64afc9 it reads the same, and diff of the two full outputs is empty: delta 0. Batch Q (T005: batch Q, the release-2 answers' amendments in #1144 (plan 038) #1248) landed between them, adding 526 lines and removing none.
• PACKET_MERGE=94b6f7f1 (94b6f7f13b45c351b9142345738965c974b7dd37), on origin/main's first-parent line; 83 first-parent commits since, 3 with the Arc: trailer (release 1's consumer pins).
• Lane openXfactory-3's composed re-run, quoted from lane3-to-lane4.log (09:52:07Z and 09:52:31Z), claimed on #656 6013610393: "174 red vs 174 (170 failed + 4 errors, 668 passed ...)"; "moved: none"; "5 suites / 210 cases"; openDox installed from openDox-code main a9ac96f9 while openXdox-code's pyproject.toml:126 and openxFactory's nested openDox/code pin dede32b4 (v0.1.0); openxFactory main 0f2a87f6 to 92010d3e. I verified one thing there: of the 48 files that differ, the two under scripts/ are scripts/ideation_dashboard/nightly_lane.py and scripts/validate-factory-mcp.py. Nothing was re-run.

Part 2: plan 038's bookkeeping

Every item is a holder ruling or a Brett ruling already posted on opensoft/openxFactory#656, encoded as worded. The files are tasks.md, plan.md, data-model.md, contracts/health-finding.md, contracts/cli-http-health.md and checklists/requirements.md.

#	Task	What changed	Record
1	T022	Files gain new tests/test_composed_placements.py (openXdox-code#41)	holder 6016356225
2	T023	Files gain new tests/test_swb_session_transport.py (the bound and unbound probes in one committed file; #42)	holder 6016676145
3	T026	Files gain tests/test_protected_suite_check.py, and T020's tests/conftest.py and tests/test_host_plane.py after T020 lands; 'cluster' respells to "group neighbourhood"; the single-writer table's chain	holder 6016356225, Brett 6016648451
4	T029	Files gain the two floor lines MIN_SELECTED and MIN_PASSED of openXdox-code's validate.yml, raised ONCE at its final head after merging main; no other PR raises them; a new single-writer row	holder 6017860539
5	R-1 (a), widened	SIX spans of tests/test_staging_workbench.py (_CREATE_HARNESS, _SESSION_HARNESS, _run_create, _run_session, _hostile_descriptors, _HOSTILE_HARNESS), served display, in T026, plan.md § R-1 and the ruled-answers row	Brett 6016648451
6	F12.1	--chains, carried out by T026 and T029; the amendments table gains the row	Brett 6016648451
7	T073	After gains T095+; new T094 (lane 3, read-only, claimed 6017801219) and T095+; T073's PR stays a DRAFT until they land; the lane table, the critical path, the slice tables and the dependency list follow	holder 6016982816
8	T073 open_until	doc_health keeps its words plus lane 3's clause; status-exemption-rail and openxfactory-contracts read the ruled sentence, quoted	holder 6016982816
9	T076 / F9.2	the WRITTEN DISPOSITION naming realize-doc-health-direction-arc as F9.2's carrier, in T076, T084, the box-accounting row and plan.md's ARC-5	holder, ARC-5 (a) 6013547504
10	T003	ticked, CLOSED ON THE RE-CHECK	holder 6017901451
11	T074	Files gain the six openXdox-code files of the arc change's design.md § 10; the single-writer table: validate.yml T029 (floors) then T074 (LEFT_OUT)	holder, from #1247's design.md § 10
12	identity	stored (a health_findings column, canonical sorted-key JSON, capped) and emitted, bounded as T040's schema bounds it: contracts/health-finding.md, data-model.md § Finding, contracts/cli-http-health.md, plan.md, T041, T042 and T046; the cross-run collision stays an accepted limit, detectable now, whether the engine reports it being T046's	holder 6018624750
13	ticks	T005 #1248 91e961a0; T008 codeXfactory/codexFactory#515 f1b019fe; T010 openDox-code#89 34c20641; T040 openDox-spec#17 7db9438b; T070 #1247 51456835; and, on the coordinator's later word, T020 openXdox-code#39 c6d15b27 and T024 openXdox-code#38 8b64fae0. Each was verified with gh pr view <n> -R <repo> --json mergeCommit	landed 2026-10-06
14	T073	Files gain new tests/test_declared_rail_registration.py (the conftest rail block's 5 lone cases with stand-in rails)	holder 6020698021, answering 6020683941
15	T026	the H-2 in-test respellings move from 17 to 20: test_gate_off_descriptor_is_the_real_cli_invocation, test_gate_off_session_affordances_are_the_real_cli_invocations and test_the_notebook_refresh_is_a_descriptor_in_BOTH_gate_postures, admitted under CF-4; plan.md's CF-4 row notes it	holder 6020859092

T002 itself is ticked.

Items skipped because already present: none. Each was searched for at origin/main (git show origin/main:<file> | grep -c), and none was in place.

Where an item could not be encoded exactly as worded, or needed a reading:

• Item 9: no task of § "Close" archives File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144 (the archive act stays the holder's, ARC-5 (a)). The coordinator accepted placing the disposition in T084, the last task to edit File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's tasks.md, and in T076 and the F9.2 accounting row.
• Item 3, the chain: the rulings order T020 before T026, and T020 before T021, but not T021 against T026. The table says "T021 and T026, in landing order", as the coordinator confirmed.
• Item 12's grep: the brief's \| is a markdown-table escape, so I ran it with plain |. Four hits remain, each the note that reverses the old wording ("reversing the engine-internal refinement"). The ruling gives no cap value, so none is written: the engine caps it, and the cap is T041's.
• The commit trailer names the model that wrote it, Claude Sonnet 5.5, as the session's attribution rule requires, where the writer rules spell Claude Opus 5.5 (1M context).

The holder's answers on this PR's four open questions

1. tests/test_declared_exclusion.py is NOT in T073's Files: T073 measured its lone CI green while touching only its own four files. It IS in T074's Files (item 11).
2. FR-011 and an identity response-shape falsifier are DEFERRED to the holder's next bookkeeping batch, with T094's T095 to T104 entries. This PR keeps to its list, so spec.md is as origin/main has it. (Copilot asked; the edit was made at 76b9428b and taken back at 7ddfda5e.)
3. The identity cap is T041's: the contract module owns the field bounds, and T042 stores what T041 bounds. T041's and T042's entries, data-model.md § Finding and contracts/health-finding.md say so (80c6fee7). No value is written.
4. T003: the constitution's analyze gate was met by round 1 (evidence/analyze-round-1.md) and its re-check (6013547504). T003 was a discretionary second round, so the closure (6017901451) stands.

Review and gates

Copilot at	verdict	findings	answered
8b0a535d	Changes recommended	5: FR-011 and the identity's response shape; an exact aggregate cap; the T003/T004 states; the F9.2 disposition against ARC-5; the task count	the T003/T004 states, ARC-5 and the count were fix-now, fixed in 76b9428b. The cap is an accepted limit (no value is written, by the holder's word); FR-011 is the holder's (open question 2)
da00b298	Changes recommended	3 new: FR-011 against the bookkeeping scope; T003 without a fresh analyze; T020's tick against the old body	FR-011 taken back in 7ddfda5e; T003 is the holder's (open question 4); the body is corrected (item 13)
7ddfda5e	Needs a closer look	0 new threads; the 2 it listed as "previously missed" are those two	answered, see the threads
80c6fee7	Needs a closer look	2 body-level findings: identity should be NOT NULL in the store's model; r2-base.md called its figures an input to T004's ruling, but T002 follows T004	both fix-now, fixed in fb57b851
f0f6923d (final)	Changes recommended	1: the "stored identity makes a collision detectable" sentence overstates it for an exception-only finding, which is never stored	accepted limit (#656 5988818366): the sentence is the holder's own wording (6018624750), and what T046 can detect from stored rows is T046's. Answered and resolved; no push

9 threads, 0 unresolved. Every reply cites its commit or ruling.

• python3 scripts/validate-openspec-cli-pin.py --all, in the clone named openxFactory, at f0f6923d: 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, locally at 8b0a535d (CI venv, -m "not postgres", TMPDIR under ~/.local/state): 1 failed, 9206 passed, 7 skipped, 338 deselected, 9 warnings, 598 subtests passed in 2589.39s. The one failure is tests/hermes_runtime_contracts/test_validator_cli.py::test_release_mode_field_is_preserved_on_the_real_repository[--require-realization-realization], a 30s TimeoutExpired. It fails the same way on origin/main in the same clone (1 failed, 1 passed in 54.40s), and the CI job passes it, so it is pre-existing and environmental. My later commits change documents only.
• Doc-health, scripts/doc-health.py --single-repo ., branch f0f6923d against origin/main c44c1610 in the same clone: the two reports are byte-identical (sha256 3b2e1f59db747178…; Findings: 31 critical, 26 error, 69 warning, 20 info. New regressions vs previous report: 0.). So no new error.
• CI at f0f6923d: all 15 check runs completed at the head: pytest-suite success (19:00:34Z to 19:27:22Z), SonarCloud Code Analysis success, doc-health-py314, openxdox-consumer-gate, openspec-cli-pin, wallet-validation, clearing-dispatch-gate, signed-execution-chain-gate, former-id-arrival-gate, release-tag-gate, openreposhape-pin and the three lane-line runs all success. One is RED, merge-master-approval, and it is inherited from main: its floor evaluation stops at floor_incomplete, "4 covered-pending path(s) exceed the tolerance of 3", the four being openspec/specs/corpus-adapter-seam, domain-mapping-declaration, factory-mcp-conformance and packet-citation-report, each added_to_base_after_pin. This PR touches no openspec/specs path. Archive add-factory-mcp-conformance: realization #1243 → 92010d3e, packet closed #1252 (the archive that promoted factory-mcp-conformance) merged at 18:58:07Z, and this run (18:59:37Z) is the first gate run after it; every other open PR's last run predates it. It passed on this PR at 7ddfda5e and 80c6fee7. A rerun reads the same base, so the pin or floor refresh (Advance the pinned decision core to fe9a6f5b91886e4f07296dc6a264deb345b1618f #1138, "Advance the pinned decision core") is what clears it; the holder rules on landing over it.
• main moved once more after these gates, to a2dc658d (prefer-triad-project-shape 5.1: the doctrine and register description restate the Triad as preferred, confers nothing #1254, which touches contracts/schemas/project-register.schema.yaml, docs/project-repo-schema.md and openspec/changes/prefer-triad-project-shape/tasks.md). It shares no file with this PR, and git merge-tree reports a clean merge. I did not merge it in, since each merge restarts the 27-minute gate; the holder can run gh pr update-branch before landing if wanted.

Files changed

• specs/038-opendox-document-tool-self-maintenance/evidence/r2-base.md (new)
• specs/038-opendox-document-tool-self-maintenance/tasks.md, plan.md, data-model.md, checklists/requirements.md
• specs/038-opendox-document-tool-self-maintenance/contracts/health-finding.md, contracts/cli-http-health.md
• README.md (the feature-038 entry's evidence list, one link)

What is NOT done

• No requirement, scenario or spec delta is touched: spec.md is as origin/main has it, and nothing is under openspec/changes/.
• No box of File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144 is ticked, and T071 and the other tasks are left as they stand.
• T046's falsifier is unchanged: whether the engine reports a cross-run collision is named as its concern in contracts/health-finding.md only.
• Lane 3's composed run is quoted, not repeated.

🤖 Generated with Claude Code

Summary by Sourcery

Record release 2's baseline evidence and incorporate the latest plan rulings, task status, and health-finding contract updates into feature 038.

New Features:

• Add release 2 base evidence covering repository revisions, task census, packet merge, and the composed-suite re-measurement.
• Document health-finding identity as a bounded field that is stored and exposed through CLI and HTTP health results.

Enhancements:

• Update plan and task bookkeeping with completed work, revised dependencies, ownership, rulings, and follow-up repair tasks.
• Record the closure of the analyze task and several landed implementation tasks, including the associated evidence and merge references.
• Clarify composed-test coverage, protected-suite bookkeeping, F9.2 disposition handling, and validation workflow ownership.

Documentation:

• Link the new release 2 base evidence from the feature documentation index.
• Update release 2 contracts, data model, plan, task records, and requirements checklist to reflect the latest rulings and bookkeeping.

Chores:

• Mark T002 and related completed tasks and merge commits in the feature bookkeeping.

[sourcery-ai]

Reviewer's Guide

This bookkeeping-focused PR records release 2's repository and test baseline, links the evidence, and synchronizes plan/task records with previously posted rulings and landed commits; it also updates the health-finding contract and data model to store and emit bounded identity data. No implementation code, requirements, spec delta, or openspec change is introduced.

File-Level Changes

Change	Details	Files
Adds a release-2 baseline evidence record covering repository tips, task-box census, F11.1 packet merge ancestry, and the quoted lane-3 composed re-measurement.	Records full repository main SHAs, dates, subjects, and changes since the plan-time R0 baseline. Captures the 125-box census, 42 open boxes, zero census delta, and PACKET_MERGE first-parent verification. Quotes lane 3's 174-red composed result, passing-suite counts, pins, and explicitly notes that the run was not repeated. Links the new evidence from the feature-038 README entry.	specs/038-opendox-document-tool-self-maintenance/evidence/r2-base.md README.md
Updates feature-038 planning and task bookkeeping to encode previously issued rulings and landed work without introducing new requirements or decisions.	Marks T002, T003, T005, T008, T010, T040, and T070 complete with merge references and adjusts task counts and dependency/order tables. Records changes to T022, T023, T026, T029, T073/T094+, T074, T076/F9.2, and related single-writer, lane, critical-path, and protected-suite rules. Adds the six-span R-1 widening, F12.1 --chains behavior, T073 draft dependency on repair slices, and declared-rail test coverage bookkeeping. Documents the F9.2 archive disposition and expands the arc-change file ownership list.	specs/038-opendox-document-tool-self-maintenance/tasks.md specs/038-opendox-document-tool-self-maintenance/plan.md
Changes the health-finding contract and data model so identity is persisted and exposed instead of remaining engine-internal.	Adds identity to CLI JSON and HTTP response requirements. Defines canonical JSON storage, schema-aligned field restrictions, serialized-size capping, and engine-authored identity forms. Revises collision wording to make cross-run collisions detectable through stored identity while retaining reporting as T046's concern. Adds the identity column and updates the finding model and refusal rules.	specs/038-opendox-document-tool-self-maintenance/contracts/health-finding.md specs/038-opendox-document-tool-self-maintenance/contracts/cli-http-health.md specs/038-opendox-document-tool-self-maintenance/data-model.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

Task-state contradictions and underspecified identity API behavior must be reconciled before approval.

Review effort: Balanced
Findings: 2 · 3

Open (5)

• Specify identity in FR-011 and CLI/HTTP task tests · New
• Define an exact aggregate identity size limit · New
• Resolve contradictory T003 and T004 task states · New
• Align archive disposition with ARC-5 plan and task record · New
• Correct checklist task count or remove T095+ placeholder · New

What changed in this PR

Records release 2 baseline evidence and synchronizes feature 038’s planning, task bookkeeping, and health-finding contracts.

Changes:

• Adds release baseline and composed-suite evidence.
• Records task completions, rulings, dependencies, and repair slices.
• Makes finding identity stored and publicly emitted.

File	Description
README.md	Links release-2 evidence.
specs/​038-opendox-document-tool-self-maintenance/​tasks.md	Updates task state and sequencing.
specs/​038-opendox-document-tool-self-maintenance/​plan.md	Records post-ruling decisions.
specs/​038-opendox-document-tool-self-maintenance/​evidence/​r2-base.md	Captures release baseline measurements.
specs/​038-opendox-document-tool-self-maintenance/​data-model.md	Adds persisted finding identity.
specs/​038-opendox-document-tool-self-maintenance/​contracts/​health-finding.md	Defines identity storage and emission.
specs/​038-opendox-document-tool-self-maintenance/​contracts/​cli-http-health.md	Exposes identity through CLI and HTTP.

---

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

[Copilot]

Copilot review overview

🟡 Changes recommended

The analyze gate is closed without the constitution-required run, and the diff contains scope discrepancies with the PR description.

Review effort: Balanced
Findings: 4 · 1

Open (5)

• FR-011 contract changes despite bookkeeping-only scope · New
• T003 marked complete without required analyze gate · New
• Define an exact aggregate identity size limit
• Specify identity in FR-011 and CLI/HTTP task tests
• T020 completion conflicts with approved PR scope · New

Resolved since last review (3)

• Correct checklist task count or remove T095+ placeholder
• Align archive disposition with ARC-5 plan and task record
• Resolve contradictory T003 and T004 task states

[Copilot]

Copilot review overview

🔵 Needs a closer look

The analyze gate is improperly closed, and the identity contract and cap ownership remain inconsistent.

Review effort: Balanced
Findings: 3 · 1

Open (4)

• T003 marked complete without required analyze gate
• Define an exact aggregate identity size limit
• Specify identity in FR-011 and CLI/HTTP task tests
• T020 completion conflicts with approved PR scope

Resolved since last review (1)

• FR-011 contract changes despite bookkeeping-only scope

Previously missed (2)

In code that hasn't changed since last review

T003 closes without required fresh analysis

specs/​038-opendox-document-tool-self-maintenance/​plan.md:252

The Constitution Check cannot close T003 without the required analyze run. .specify/memory/constitution.md:127-132 mandates tasks → analyze → implement and says /speckit.analyze MUST report no critical findings before implementation; this row itself says the re-check was not a fresh run, while the checklist remains unchecked. The constitution also supersedes other process descriptions (:141-148), so a holder ruling cannot waive this gate. Run and disposition a fresh analysis of the ruled revision before marking T003 complete, or restore T003 to pending.

Serialized-size cap is inconsistent across parallel tasks

specs/​038-opendox-document-tool-self-maintenance/​tasks.md:874

This leaves one serialized-size invariant for T041 and T042 to choose independently, but those tasks are parallel and T042 does not depend on T041 (tasks.md:888 versus :923). They can therefore implement or test different limits for validation and storage. Define the cap once in the contract/plan and require both tasks to consume it, or order T042 after the owner of that value.

[Copilot]

Copilot review overview

🔵 Needs a closer look

The identity persistence invariant and T002 evidence chronology need correction.

Review effort: Balanced
Findings: None

Resolved since last review (4)

• T003 marked complete without required analyze gate
• Define an exact aggregate identity size limit
• Specify identity in FR-011 and CLI/HTTP task tests
• T020 completion conflicts with approved PR scope

Previously missed (2)

In code that hasn't changed since last review

Require identity column to be NOT NULL

specs/​038-opendox-document-tool-self-maintenance/​data-model.md:198

identity is required by the T040 finding schema, but this storage model does not declare the new column NOT NULL as it does for the other required provenance fields. That permits T042 to define a nullable column and persist a finding that cannot satisfy the public finding shape; make the at-rest invariant explicit.

Correct T002 and T004 chronology and evidence usage

specs/​038-opendox-document-tool-self-maintenance/​evidence/​r2-base.md:235

T002 is explicitly sequenced after T004 (tasks.md:133), so measurements captured by T002 cannot be inputs to T004's already-recorded ruling. Keeping this claim reverses the plan's chronology and misstates the evidence's governance role; limit the consumers to the later checkpoints.

[Copilot]

Copilot review overview

🟡 Changes recommended

The collision documentation incorrectly claims detectability where exception records retain no prior identity.

Review effort: Balanced
Findings: 1

Open (1)

• Narrow collision detection claim for exception-only findings · New

[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 3 days and 2 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[Copilot]

Copilot review overview

🟡 Changes recommended

Writer-chain and landing-order records remain internally inconsistent.

Review effort: Balanced
Findings: 3

Open (3)

• Update landing prerequisites for T095+ dependency · New
• Split conftest.py and test_host_plane.py writer paths · New
• Incorrectly shared writer chain for test_host_plane.py · New

Resolved since last review (1)

• Narrow collision detection claim for exception-only findings

[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

[brettheap]

READY (holder, manual landing) at 1eb8e9e

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

Holder, at READY: T002, release 2's base and plan 038's bookkeeping, items 1 to 15. Landing on Brett's word "land #1251 when green" (2026-10-06 ~22:1xZ).

• The head: 1eb8e9eb is the holder's update-branch merge of main 9171d14a, made after Advance the pinned decision core to fe9a6f5b91886e4f07296dc6a264deb345b1618f #1138 (lane openXfactory-5, on Brett's word) moved the review-lane pin onto the re-swept floor. That cleared the inherited merge-master-approval red, floor_incomplete since Archive add-factory-mcp-conformance: realization #1243 → 92010d3e, packet closed #1252. Plan 038's content equals the frozen f0f6923d.

• Gates at the head:

  • every check passes (rollup SUCCESS): pytest-suite, merge-master-approval, openspec-cli-pin, openxdox-consumer-gate, lane-line, wallet-validation, release-tag-gate, signed-execution-chain-gate, former-id-arrival-gate, clearing-dispatch-gate, doc-health-py314, openreposhape-pin and SonarCloud; Sourcery is skipped;
  • the files are README.md and specs/038-… only, with no Rule 6 path;
  • 0 closing keywords in the body or commits.

• Copilot "Changes recommended", ACCEPTED under 5988818366:

  • at f0f6923d, the identity-collision wording, which is the holder's own (6018624750);
  • at 1eb8e9eb, three plan-record items: the landing-order row for T073, and splitting the conftest.py/test_host_plane.py chains.

  None is a bypass. All are folded into T002 batch 2 (r2/t002b-bookkeeping-2, stacked on this PR), and each thread is answered and resolved.

[brettheap]

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

LANDED — lane openxfactory-4, 2026-10-06T22:31:49Z, PR #1251 → 1837ea7 (opensoft/openxFactory main; plain gate)

Landed on Brett's word "land #1251 when green". Copilot's four items (identity wording; T073 landing-order row; conftest/test_host_plane chain split) are ACCEPTED under 5988818366 and folded into T002 batch 2.