T089: phase 3's checkpoint, quoted; T092's phase-3 notes (plan 034)

[brettheap]

Lane: openxfactory-4 (openXfactory-4-openDox_extraction)
Authored by lane openXfactory-3, delegated by lane openxfactory-4 (#656 5984809456)

Plan 034 T089, phase 3's checkpoint, and T092's phase-3 notes. This PR runs every check T089 names, at the commits phase 3 pinned, and quotes each one. It also carries T092's phase-3 notes in docs/opendox-carve-manifest.yaml, on the holder's decision below.

• Every check passes. F5.2 whole passes after T086's repair, so F5.2's box closes here (RULED 5962785556, item 1: "F5.2's box closes at phase 3's checkpoint (T089)"), and F4.1's box closes here too (plan 034's box map: F4.1 → T089). T097 ticks both in File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144; this PR ticks only T089.
• This PR is bookkeeping, so it carries no Arc: trailer (R1Q20 (a), 5817152735; T091). Claims: openDox + openXdox: two open-source layers, an installable app with users, projects and a database; domain descendants pin openXdox (Brett's ruling 2026-09-04) #656 comments 5984809456 (lane openXfactory-3's D3: T098 and T089) and 5987202231 (D5: T092's phase-3 notes), delegated by lane openxfactory-4.

Ruled, as T089 cites: F5.2's close, 5962785556, item 1. The amended forms run: batch H (F10.1, F13.1), batches M and P (F16.1), batches C, F, G and K (F5.2), batch A (F11.1's guard).

No Rule 6 window. This PR touches nothing under openspec/changes/: the checkpoint finds no record in #1144 that is wrong, so #1144's tasks.md is untouched.

The record is specs/034-opendox-standalone-operation/evidence/checkpoint-phase3.md.

• Each falsifier in it was extracted by anchor, byte for byte, from File add-neutral-product-standalone-operability: open the BUILD arc, recording ten rulings #1144's tasks.md at 36908480 (sha256 48db295594a6…), and every extraction reproduces the sha256 the earlier records quote (F4.1 8900b985e72f; F10.1 d94265449831 → 2358bd8f76ab; F13.1 1e1f7da5564a → 0a47fa31f5e0; F16.1 fe22ec4873d1 → 619b32a955e2; F5.2 808619e066fa → 4b1512c26814; F11.1 60beede1244b).
• Each ran from a fresh detached worktree at the pinned commit, with an empty git status --porcelain --ignored, in a scrubbed env -i environment, in the foreground of its wrapper.

Verdict

#	T089's check	where	result, quoted
1	F4.1	openDox-code dede32b4	PASS, exit 0: 1 passed twice, then no deferred reach names the consumer or the publisher
2	F10.1, as batch H amends it	openDox-code dede32b4, pip install ".[local]" (opendox-0.1.0)	PASS, exit 0: the bundled database, migrations ['0001', '0002']; validation: opendox-snapshot: 0 violations; serving http://127.0.0.1:8080/index.html
3	F13.1, as batch H amends it	openDox-code dede32b4	PASS, exit 0: the bundled database, migrations ['0001', '0002']; every assertion holds, the last grep -q OPENDOX_OIDC_ISSUER …/default.err
4	F16.1, as batches M and P amend it, with T100's named test	openDox-code dede32b4	PASS, exit 0: 24 passed (16.6), the dialect line, no model configured: the catalog offers nothing, 83 passed (tests/test_chat_model_configuration.py), 532 passed (tests/test_model_binding_trust.py)
5	F5.2 whole, as batches C, F, G and K amend it, after T086's repair	openXdox-code 56e1c238, openDox-code dede32b4 installed over it, OPENXFACTORY at 36908480	PASS, exit 0: the seven suites pass whole (45, 23, 18, 6, 40, 9 and 12 passed), test -s holds, and the --chains step prints ok: 5 protected edit(s), each entered and holding
6	T098's interim F11.1	openxFactory, ARC_TIP at T094's landing 36908480	PASS: quoted from f11.1-phase3.txt (#1237 → 20ce593e), and re-run here with the same line, requirement 1 holds: 0 note(s) annotated, every other path a declared surface (11.1)

T092's phase-3 notes, carried here

Where they ride, and which reaches they cover.

• Phase 2's decision (b), recorded in T064's PR (T064: phase 2's consumer pins, openDox d5098297 and openXdox f257e021, with openXdox's governed projection registered by the host (plan 034) #1215): phase 2's notes rode in T063's checkpoint PR, as phase 1's rode in T049's.
• The holder's decision for phase 3 (lane openxfactory-4's round-2 delegation, 2026-10-05, D5, recorded there and here): "Phase 3's notes ride in phase 3's checkpoint PR, the T089 PR, not in T094's arc PR. This follows phases 1 and 2, whose notes rode in T049's and T063's checkpoint PRs on the holder's decisions (T092's text names both). The checkpoint PR carries no Arc: trailer, so F11.1's count of annotated notes never includes them. Run F11.1's content rule over them in that PR, as T049 and T063 did."
• The holder's ruling (A) (#656 comment 5994463071, 2026-10-05), on lane openXfactory-3's question whether consumer_reach.py's last stand-ins take notes too: "Phase 3 reads T092 as phase 2 did. T092 asks for one edits[].note per closed reach. Phase 2's T055 removed ten stand-in names of the same kind, and T063's checkpoint PR noted none of them (decision (b), recorded in T064: phase 2's consumer pins, openDox d5098297 and openXdox f257e021, with openXdox's governed projection registered by the host (plan 034) #1215). A stand-in's removal is therefore not counted as a closed reach. Phase 3's notes cover the reaches T084 and T086 closed, the three rows of the default patch."

3 notes on 3 rows (2 added, 1 extended), for the eleven reaches phase 3 closed. They are #1144's 4.3 reaches into openXdox that F4.1's scan still named at phase 2's pin 047bb4fa, and the three rows of openXdox-code's ratchet OPENDOX_BACK_IMPORTS. All eleven drop at T084 (opensoft/openDox-code#77 → e49b17c3), which also retires consumer_reach.py.

entry	carve lines	reaches at 1e4a57fb	note
branch_session.py edits[0]	1574, 1992	:1587, :2005	extended (phase 2's note left these two open for phase 3)
serve_project.py edits[0]	246, 247	:246, :247	added
serve_workbench.py edits[0]	346, 406, 407, 543, 1214, 1664, 2606	:347, :407, :408, :544, :1215, :1665, :2607	added

Each note cites the landings that close its reaches, each re-verified at this PR's run (closers-p3.py, quoted in the record): T084 (opensoft/openDox-code#77 → e49b17c3), T086 (opensoft/openXdox-code#37 → 56e1c238: openxdox.column_contributions.register(), and OPENDOX_BACK_IMPORTS at (0, 0) with its pin at T087's commit dede32b4), and T094 (#1236 → 36908480: the host's call).

So the stand-ins consumer_reach.py still held at 047bb4fa (gate_console, serve_gate, serve_projection and the two late bases) take no note, on ruling (A).

F11.1's content rule, T049's script byte for byte, over main's manifest and this PR's:

  extended: scripts/ideation_dashboard/branch_session.py edits[0]
  added: scripts/ideation_dashboard/serve_project.py edits[0]
  added: scripts/ideation_dashboard/serve_workbench.py edits[0]
F11.1's manifest content rule holds: 3 note(s) annotated, nothing else in the manifest moved

With every edits[].note removed, the two manifests are equal, and no other line moved. The note check, the reach mapping, scripts/validate-carve-manifest.py (OK) and F4.1's scan walk are quoted in the record's last section.

The pins

From pins.sh over openxFactory at 36908480, with openDox and openXdox initialized recursively: openDox root e1e3a3c3 (code → openDox-code dede32b4, T087's pin), openXdox root 9564d5d9 (code → openXdox-code 56e1c238, T086's landing; its contracts/opendox-pin.yaml → e1e3a3c3), and openXdox-code's pyproject.toml pins openDox-code dede32b4. All six T090 equalities hold, and the runs used exactly the pinned commits.

What changed (5 files)

• specs/034-opendox-standalone-operation/evidence/checkpoint-phase3.md: new, Status: record. It is linked from the feature 034 entry in README.md, beside T098's F11.1 record, and from plan.md's evidence tree.
• specs/034-opendox-standalone-operation/tasks.md: T089 ticked, with its Run bullet (T063's form), and T092's entry gains phase 3's sentence after phase 2's (T063: phase 2's checkpoint, quoted; T092's phase-2 notes (plan 034) #1218's form; T092 stays unticked, since 11.1 is ticked at ARC close). The box map already names T089 for F4.1 and F5.2, and nothing moves, so it is unchanged.
• specs/034-opendox-standalone-operation/plan.md: the evidence tree and its prose.
• README.md: the checkpoint link.
• docs/opendox-carve-manifest.yaml: T092's phase-3 notes, note: lines only (2 added, 1 extended). With every note removed the manifest is unchanged.

Validation, at the head against main 20ce593e

• python3 scripts/validate-openspec-cli-pin.py --all --strict (pinned CLI 1.12.0): rc 0, Totals: 110 passed, 1 failed (111 items), 0 UNDISPOSITIONED failures; the one failure is the accepted add-chain-attestation exception, as on main.
• doc-health --single-repo . --as-of 2026-10-05, run at main 20ce593e and at the head in two worktrees of one clone, each named openxFactory, so like is compared with like: rc 0 at both, Findings: 31 critical, 26 error, 69 warning, 20 info. New regressions vs previous report: 0., and the two reports are byte-identical, a delta of zero.
• Every 8-character commit sha in the record and in this diff resolves with git rev-parse --verify in its own repository (openxFactory, openDox-code, openXdox-code and the two roots). The two spec shas in the record's pin table, f7ee3c76 and f088b097, are the roots' gitlinks, read with git ls-tree.

Rehearsal (2026-10-04, at that day's mains, before T086, T087, T094 and T098)

At openDox-code 38d3350e, openXdox-code 6a3b93b9 and openxFactory c8d80020 (ARC_TIP fcb45380): F4.1, F10.1, F13.1, F16.1 (24, 83 and 135 passed) and F11.1 passed; F5.2 was red as expected until T086, on tests/test_session_snapshot.py (17 failed, 6 passed: 16 SeamNotRegistered at openDox's kickoff seam, 1 IndexError) and tests/test_snapshot_validation_launch.py (9 failed: T070's install-mode precondition, hosted by default and refused for no OPENDOX_OIDC_ISSUER), with the other five suites whole and --chains at ok: 4 protected edit(s). opensoft/openXdox-code#37's scope covers all 26.

Host paths in the quotes are written <workdir>, and the user <user>. No closing keyword appears in this body or in any commit.

🤖 Generated with Claude Code

Summary by Sourcery

Complete the phase 3 standalone-operation checkpoint and record its passing validation and carve-manifest bookkeeping.

Enhancements:

• Record and link the phase 3 checkpoint evidence for the openDox standalone-operation plan.
• Close the phase 3 manifest bookkeeping by documenting the eleven reaches retired through the completed seam work.
• Mark T089 complete and document the corresponding F4.1 and F5.2 checkpoint closures.

Documentation:

• Add the quoted phase 3 checkpoint, pin verification, test verdicts, and evidence procedures to the feature documentation.
• Carry T092 phase 3 carve notes in the openDox manifest and update the feature evidence tree and task notes.

Tests:

• Verify F4.1, F10.1, F13.1, F16.1, F5.2, and interim F11.1 at the phase 3 pinned commits, with all checks passing.

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

[sourcery-ai]

Reviewer's Guide

This bookkeeping PR completes T089’s phase-3 checkpoint by recording reproducible passes for all named checks at the pinned commits, closes the F4.1 and F5.2 checkpoint boxes, and carries T092’s three manifest notes for the eleven reaches closed in phase 3, with documentation links and integrity evidence.

Entity relationship diagram for phase 3 carve notes

erDiagram
    PHASE3_CHECKPOINT ||--o{ CARVE_NOTE : carries
    CARVE_NOTE }o--|| MANIFEST_ENTRY : annotates
    CARVE_NOTE }o--o{ CLOSED_REACH : documents
    PHASE3_CHECKPOINT {
        string task T089
        string result PASS
    }
    CARVE_NOTE {
        string status added_or_extended
        string closer T084
    }
    MANIFEST_ENTRY {
        string path
        string edit
    }
    CLOSED_REACH {
        string source_line
        string destination_line
    }

Loading

Flow diagram for the phase 3 checkpoint evidence

flowchart TD
    Pins[Verify pinned commits and clean detached worktrees] --> Checks[Run T089 checks F4.1 F10.1 F13.1 F16.1 F5.2 and F11.1]
    Checks --> Pass[All checks pass]
    Pass --> Close[F4.1 and F5.2 boxes close]
    Pass --> Record[Record quoted results in checkpoint-phase3.md]
    Record --> Links[Link evidence from README.md and plan.md]
    Pass --> Manifest[Carry three T092 notes in carve manifest]

Loading

File-Level Changes

Change	Details	Files
Adds the phase-3 checkpoint record and links it into the feature documentation.	Records pinned commits, hermetic execution conditions, quoted verdicts, and validation details for F4.1, F10.1, F13.1, F16.1, F5.2, and interim F11.1. Ticks T089 and documents closure of F4.1 and F5.2 at the checkpoint. Adds the checkpoint to the evidence tree and README index.	specs/034-opendox-standalone-operation/evidence/checkpoint-phase3.md specs/034-opendox-standalone-operation/tasks.md specs/034-opendox-standalone-operation/plan.md README.md
Carries T092 phase-3 carve notes for the reaches closed by T084.	Extends the branch_session manifest note with two phase-3 closures. Adds notes for the two serve_project and seven serve_workbench closed reaches. Documents that notes are limited to declared carve lines and that retired stand-ins receive no notes.	docs/opendox-carve-manifest.yaml specs/034-opendox-standalone-operation/evidence/checkpoint-phase3.md specs/034-opendox-standalone-operation/tasks.md
Provides reproducible evidence for the manifest annotations and cross-repository pin/landing relationships.	Verifies note-only manifest changes and maps all eleven reaches to unique carve entries. Re-verifies T084, T086, T087, and T094 landings and the relevant pin equalities. Captures clean detached worktrees, scrubbed environments, and successful validation output.	specs/034-opendox-standalone-operation/evidence/checkpoint-phase3.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

🔵 Needs a closer look

The documentation is internally consistent, but its approval depends on extensive cross-repository execution evidence that cannot be independently reproduced from this snapshot.

Review effort: Balanced
Findings: None

What changed in this PR

Records phase 3’s T089 checkpoint and T092 carve-manifest notes for feature 034.

Changes:

• Adds quoted checkpoint evidence for all required phase-3 checks.
• Marks T089 complete and updates planning references.
• Annotates the three manifest rows covering eleven closed reaches.

File	Description
README.md	Links the phase-3 checkpoint.
docs/​opendox-carve-manifest.yaml	Adds phase-3 closure notes.
specs/​034-opendox-standalone-operation/​evidence/​checkpoint-phase3.md	Records checkpoint commands, outputs, pins, and note validation.
specs/​034-opendox-standalone-operation/​plan.md	Adds the checkpoint to the evidence tree.
specs/​034-opendox-standalone-operation/​tasks.md	Completes T089 and records T092’s phase-3 notes.

---

💡 Add a code-review agent skill or 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

[brettheap]

READY at 8bd4d12 — Lane: openxfactory-4 (openXfactory-4-openDox_extraction)

Holder: lane openXfactory-3's D3, the second half, T089: phase 3's checkpoint, quoted, with T092's phase-3 notes. It is bookkeeping and evidence, with no Arc: trailer (R1Q20 (a)).

• The checkpoint, run C at openDox-code dede32b4, openXdox-code 56e1c238 and openxFactory 36908480. All six pass:
  • F4.1: no deferred reach names the consumer or the publisher;
  • F10.1: 0 violations;
  • F13.1: the migrations apply;
  • F16.1: passes, with batches M and P's cases;
  • F5.2: the seven suites pass, and its 5 protected edits each hold;
  • T098's interim F11.1: requirement 1 holds.
• The closers, re-verified against the real landings: T084 e49b17c3, T086 56e1c238, T087 e1e3a3c3/dede32b4, and T094 T094: phase 3's consumer pins, openDox e1e3a3c3 and openXdox 9564d5d9, with phase 3's host wiring: openXdox's columns and the governed binding-trust policy (plan 034) #1236 36908480.
• T092's phase-3 notes follow the default patch, ruling (A) 5994463071: 3 notes on 3 rows (2 added, 1 extended), recorded beside phase 2's decision (b). The content rule holds, and with the notes stripped the manifest is byte-identical. validate-carve-manifest is OK. T092 stays unticked until the arc closes.
• Gates.
  • All 15 checks pass.
  • Copilot finds nothing ("Needs a closer look", no findings, 0 threads).
  • There is no closing keyword.
• What follows. T095 (openDox-code#75) lands next. Its landing is X for lane openXfactory-3's T096.

[brettheap]

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

LANDING — lane openxfactory-4, session faabad8b-8c31-4958-abd5-b35bdc9cd282@Eagle, 2026-10-05T15:26:31Z, PR #1238 into opensoft/openxFactory main

[brettheap]

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

LANDED — lane openxfactory-4, 2026-10-05T15:26:56Z, PR #1238 → fab575a (opensoft/openxFactory main; squash)