T026, U-7: the allow-list for 12.5's governed suites, with R-1 (a)'s span kind (plan 038, H-2)

[brettheap]

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

Arc: neutral-product-standalone-operability

T026, U-7: the allow-list for 12.5's governed suites, with R-1 (a)'s span kind (plan 038)

The After set has landed:

• T020 (T020, U-1: the governed host for the governed suites that drive the gate verbs (plan 038, P4F-5) #39, at c6d15b2). This branch is up to date with main f70bc9c, which also holds T024 (T024, U-5: the H-1 shim, ideation_dashboard.session_git answers with opendox.session_git (plan 038, CF-3) #38), T023 (T023, U-4: swb-session.js spells the model's two names at its call sites again (plan 038) #42) and T021 (T021, U-2: the gate console's schemas, each read where its owner keeps it, nothing vendored (plan 038, P4F-4) #40). main was merged in at e6d99691, 3226d5c, 9e0979c and 9c29855, never by rebase;

• T004 (Feature 038: the Speckit specification for release 2 of add-neutral-product-standalone-operability (#1144) openxFactory#1245, at 260234b5);

• T005's batch Q (T005: batch Q, the release-2 answers' amendments in #1144 (plan 038) openxFactory#1248, at 91e961a0), which gives 12.5's oracle call --chains. openxFactory main's add-neutral-product-standalone-operability/tasks.md:3055 now reads python3 scripts/protected_suites.py --chains --landings="$(cat "$W/x-arc.txt")" --suites="$(cat "$W/governed.txt")".

• Realizes: 12.5 (part).

• Falsifier (tasks.md): the oracle prints ok: … each entered and holding; the nodes, composed, quoted.

• Ruled:

  • R2Q8, CF-4 (H-2), R-1 and W-1, with plan 038 by Brett Heap, everything as recommended (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) openxFactory#656 comment 6013547504).
  • Brett's ruling on this task's four points (comment 6016648451, every answer the recommended one):
    1. 12.5's call takes --chains, and T026 lands as one PR.
    2. and 3. R-1 (a)'s spans widen to six, the helpers hand each harness the SERVED display, and T020's host registration covers tests/test_staging_workbench.py, edited by T026 in T020's two files once T020, U-1: the governed host for the governed suites that drive the gate verbs (plan 038, P4F-5) #39 landed.
    3. T026's Files gain tests/test_protected_suite_check.py.
  • The holder respelled the 'cluster' node to group neighbourhood, as measured.

What this PR does

32 entries are appended to tests/protected_suite_respellings.yaml, giving 51 in all. Each is one edit inside its named test or span, with its exact old and new text, and the entries for each suite are chained by blob.

suite	entries	what
test_session_gates.py	3	CF-4: cmd_gate_* read from openxdox.cli_gate
test_session_verbs.py	5	CF-4: cmd_gate_* 4, and Group W openxdox.generator.live_topic_health
test_session_confinement.py	3	CF-4: serve_projection.hosted_index
test_doxbench_share.py	2	CF-4: each swept module at its one home; the record schema read through openxdox.contracts.verified_bytes, digest-checked against copies.yaml (Copilot's finding)
test_staging_workbench.py	19	see below

The 19 staging entries, in chain order (allow-list entries 33 to 51):

• 33: the 'cluster' node, respelled to group neighbourhood.
• 34, 37, 38 and 39: CF-4 Group S2, the four slice-S5 spellings of the create and session columns.
• 35 and 36: R-1 (a)'s two in-test relocations, :1291 and :1333. Each route is one export const …_ROUTE of swb-session.js, and neither the view nor the model names one.
• 40 to 49, R-1 (a)'s six spans (seven span: entries) and three in-test respellings:
  • _CREATE_HARNESS (two entries), _SESSION_HARNESS and _HOSTILE_HARNESS: each imports its route from the column RULED Q3 moved it to (CREATE_ROUTE from swb-create.js, sessionRoute from swb-session.js) and the reader from display.js. Each installs setDisplay(readDisplay({ display: cases.display })) before anything derives, as the shell does. BRAINSTORM_AREA and STAGING_AREA become the model's capturedArea() and organizedArea().
  • _run_create, _run_session and _hostile_descriptors: each copies the sibling files its harness imports (and what they import), with a package.json that makes node read them as modules, as test_session_confinement.py's harness does. Each hands its harness /capabilities["display"], by the statement serve.build_server() makes, replayed as test_gate_loop_views.py's _served_display replays it.
  • Three in-test respellings, flagged below.
• 50 and 51: the docstrings of the two relocated tests now say what their assertions hold (Copilot's findings).

scripts/protected_suites.py, R-1 (a)'s span kind. An admitted entry may name, in place of test, a span: one module-level constant, or one module-level helper function (its decorators included). The entry's old text must lie inside that statement before the landing, and its new text inside it at the landing. Three further rules apply:

• Counted fail-closed. The span's name must have exactly one binding in the module, counting every binding form in every scope: assignment, augmented or annotated assignment, for or with target, walrus, del, def or class, an import or a star import, an except … as alias, a match capture, a type parameter and a parameter.
• Alone on its lines. No other statement may share a line with the span.
• Never a span: a class, an import, a test, two targets, an annotation alone, or an added name. Only an admitted entry may name a span.

The module's usage block and help now give 12.5's call with --chains, as batch Q has it.

tests/test_protected_suite_check.py: 33 span cases (87 in the module).

FLAGGED for the holder's word: three in-test respellings beyond the plan's 17

These are CF-4's kind. T026's measurement reported them at comment 6016415390 (point 2), and comment 6016648451 ruled that point. They close the last three of the suite's nodes, which the served display alone does not reach. Each is entered as a respelling naming that history, and each stands or falls on your word:

1. test_gate_off_descriptor_is_the_real_cli_invocation: cli.cmd_gate_create_document becomes cli_gate.cmd_gate_create_document, imported in the test from openxdox.cli_gate. The old spelling raised AttributeError.
2. test_gate_off_session_affordances_are_the_real_cli_invocations: cli.cmd_gate_edit_document, cmd_gate_open_pr and cmd_gate_abandon_session become cli_gate.…, likewise.
3. test_the_notebook_refresh_is_a_descriptor_in_BOTH_gate_postures: REPO_ROOT / "scripts" / "sync-notebooklm-books.py" becomes the one directory on the import path that holds the script, which is openxFactory's scripts/ in the composed run (R1Q23 (a)). A run that finds it in none, or in more than one, fails. The old path raised FileNotFoundError.

No assertion is weakened in any of the three, and every argument and flag assertion stays.

T020's two files, edited once #39 landed (commit 242889b)

T020's registration has to cover tests/test_staging_workbench.py. Without it every harness helper refuses ProfileNotRegistered, as measured below. The edit is to T020's tests/conftest.py and to the scan in tests/test_host_plane.py:

• "test_staging_workbench.py" joins GOVERNED_HOST_SUITES, with a comment giving the reason, kept as a block of its own apart from T021's lines;
• the scan also recognises a gate verb spelled as a command line (_GATE_COMMAND = re.compile(r"""["']gate ([a-z][a-z-]*)""")), the way this suite's descriptors spell it. Measured over the 16 governed suites, only test_staging_workbench.py matches it and not the argument-vector spelling.

T021 (#40) also edits tests/conftest.py. Whichever of the two lands second merges main.

The falsifier

The oracle, in 12.5's call as main now has it (--chains), at a simulated squash landing of this head. The landing is one local commit on main f70bc9c carrying exactly this branch's tree and the Arc: trailer, and it is never pushed. The inputs are 12.5's own:

• the governed set by its git grep: 16, the same 16;
• the Arc: landings since e28930bf: 14, T020's, T024's, T023's and T021's among them.

admitted: c41063d6aaad tests/test_gate_loop_views.py, by entry 1 of tests/protected_suite_respellings.yaml
admitted: 839492d905f4 tests/test_gate_loop_views.py, by entry 2 of tests/protected_suite_respellings.yaml
admitted: 56e1c238681a tests/test_branch_session.py, by entry 18 of tests/protected_suite_respellings.yaml
admitted: 2f7003912aa7 tests/test_doxbench_share.py, by entries 31, 32, in that order, of tests/protected_suite_respellings.yaml
admitted: 2f7003912aa7 tests/test_session_confinement.py, by entries 28, 29, 30, in that order, of tests/protected_suite_respellings.yaml
admitted: 2f7003912aa7 tests/test_session_gates.py, by entries 20, 21, 22, in that order, of tests/protected_suite_respellings.yaml
admitted: 2f7003912aa7 tests/test_session_verbs.py, by entries 23, 24, 25, 26, 27, in that order, of tests/protected_suite_respellings.yaml
admitted: 2f7003912aa7 tests/test_staging_workbench.py, by entries 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, in that order, of tests/protected_suite_respellings.yaml
ok: 8 protected edit(s), each entered and holding

rc=0. In the pre-batch-Q form, which passes no --chains, a landing of this branch reads FAIL: the arc edited protected suites outside the reviewed allow-list: tests/test_doxbench_share.py, … with rc=1. That is why batch Q was ruled.

The oracle on mutants of the real list (--chains), each refused:

A a chain step's before_blob broken: rc=2
    FAIL: tests/protected_suite_respellings.yaml breaks its own rules, so nothing is subtracted: entry 44: its before_blob is not the after_blob of the entry before it for tests/test_staging_workbench.py, so the two do not chain
B the last staging step dropped: rc=1
    refused:  f7ebecbcc37e tests/test_staging_workbench.py: entries 33-50: tests/test_staging_workbench.py at the landing is 66d16b72080ccbaece5be1aef81446aaa01500bc, not the chain's 54852fa5250b2c4d0630088154aa4bac6517bffe; entries 3…
    FAIL: the arc edited protected suites outside the reviewed allow-list: tests/test_staging_workbench.py
C a span entry names another span: rc=1
    refused:  f7ebecbcc37e tests/test_staging_workbench.py: entries 33-51: step 10: the entry's old text is not inside _run_session before the landing; entries 34-51: tests/test_staging_workbench.py before the landing is 655afc8b57224…
    FAIL: the arc edited protected suites outside the reviewed allow-list: tests/test_staging_workbench.py
D a span entry names a test instead: rc=1
    refused:  f7ebecbcc37e tests/test_staging_workbench.py: entries 33-51: step 10: the entry's old text is not inside test_toggle_keyword_is_order_preserving_and_idempotent before the landing; entries 34-51: tests/test_staging_workbe…
    FAIL: the arc edited protected suites outside the reviewed allow-list: tests/test_staging_workbench.py
E a respelling entry names a span: rc=2
    FAIL: tests/protected_suite_respellings.yaml breaks its own rules, so nothing is subtracted: entry 43: names a span, and only an admitted entry may (R-1 (a)); a respelling entry names its test

R-1 (a)'s span guards: 22 mutants of scripts/protected_suites.py, each run against the committed tests/test_protected_suite_check.py. 21 are killed. M4 survives because it is equivalent: a nested binder also lies inside its compound statement's lines, so the shared-line guard refuses it too. M22, which removes both guards, is killed.

M1 a respelling may name a span: killed (first: test_a_span_entry_that_breaks_the_rules_subtracts_nothing[respelling])
M2 a span may be spelled as a test: killed (first: test_a_span_entry_that_breaks_the_rules_subtracts_nothing[a-test])
M3 a name bound twice may be a span: killed (first: test_what_is_never_a_span_is_refused[shadowed])
M4 a block-only binding may be a span: SURVIVED
M5 a del is not a binding: killed (first: test_a_second_binding_in_any_form_or_scope_is_never_a_span[del])
M6 an except alias is not a binding: killed (first: test_a_second_binding_in_any_form_or_scope_is_never_a_span[except-alias])
M7 a match capture is not a binding: killed (first: test_a_second_binding_in_any_form_or_scope_is_never_a_span[match-capture])
M8 a star import is not a binding: killed (first: test_a_second_binding_in_any_form_or_scope_is_never_a_span[star-import])
M9 a parameter is not a binding: killed (first: test_a_second_binding_in_any_form_or_scope_is_never_a_span[parameter])
M10 a class may be a span: killed (first: test_what_is_never_a_span_is_refused[class])
M11 a helper function is never a span: killed (first: test_an_edit_inside_a_named_helper_function_is_admitted)
M12 two targets may be a span: killed (first: test_what_is_never_a_span_is_refused[two-targets])
M13 an annotation alone may be a span: killed (first: test_what_is_never_a_span_is_refused[annotation-only])
M14 a helper's decorators lie outside it: killed (first: test_a_helpers_decorator_is_inside_its_span)
M15 a shared line is allowed: killed (first: test_a_span_that_shares_a_line_with_another_statement_is_refused)
M16 old outside the span is not checked: killed (first: test_an_old_text_outside_the_span_is_refused)
M17 new outside the span is not checked: killed (first: test_a_new_text_that_leaves_the_span_is_refused)
M18 an added span is not refused: killed (first: test_what_is_never_a_span_is_refused[class])
M19 the span's first line is outside it: killed (first: test_an_edit_spanning_a_whole_named_constant_is_admitted)
M20 a span entry keeps the test key: killed (first: test_this_repositorys_allow_list_keeps_its_rules)
M21 span entries take the test path: killed (first: test_an_edit_spanning_a_whole_named_constant_is_admitted)
M22 M4 and M15 together: killed (first: test_what_is_never_a_span_is_refused[block-only])
M0 unmutated: 87 passed in 9.05s

The served display, measured in the test process (Brett's (2)+(3): "INFERRED … MEASURE it"). This was an uncommitted probe test, run composed at 3eead0fe (242889b on the integration of that time; the helpers' statement is unchanged since):

• with no host registered, the helpers' statement refuses ProfileNotRegistered;
• under the governed host (OpenxFactoryProfile), it reads host_facet: declared and host_profile: openxfactory-engineering, with areas captured: ideation/brainstorm/ and organized: ideation/staging/;
• that result equals the display of a live GET /capabilities from serve.build_server() under the same registration: EQUAL: True, 3163 bytes of sorted JSON.

The nodes, composed, in R1Q23 (a)'s form:

• openxFactory main 92010d3e, with its submodules initialized recursively and its scripts/ on PYTHONPATH;
• openDox-code#91 45f5c55d installed (W-1 (A));
• T022's runbook placement linked (its script, T022, U-3: the runbook placed from the composed tree, git-ignored, nothing vendored (plan 038, P4F-3) #41), the colour variables unset and TERM=dumb;
• each suite run alone;
• openXdox-code main f70bc9c (T020, T021, T023 and T024 landed) as the base, and this head merged onto it on a local branch that is never pushed (0478b5f1).

run	16 governed suites	test_host_plane.py	test_protected_suite_check.py
without this PR (main f70bc9c)	842 nodes: 800 passed, 42 red (staging 29, verbs 5, confinement 3, gates 3, share 2)	9 passed	54 passed
with this head 9c29855 (0478b5f1)	842 nodes: 842 passed	9 passed	87 passed
earlier, this PR WITHOUT the edit to T020's files (at 856047a, on main 56e1c23 with #41 and #42 merged)	test_staging_workbench.py: 37 failed, 46 passed, every failure ProfileNotRegistered	9 passed	n/a

42 nodes go red to green, none goes green to red, and none is still red.

CI at the head 9c29855

• Checks: validate success (run 37517336710), SonarCloud success, copilot-pull-request-reviewer success.
• CI's own pytest step, run alone (CI's install, openDox at its pin dede32b4): selected=1146 passed=1142 skipped=4 failures=0 errors=0, against the floors MIN_SELECTED 1099 and MIN_PASSED 1095 and EXPECT_SKIPPED 4. The holder ruled (lane log, 13:57Z) that T029 raises the floors once, and T020 to T026 leave them.
• Copilot: reviewed at 9c29855, "Needs a closer look" (a governance-sensitive validator and a large chained allow-list), Findings: None. 9 threads over its reviews, each answered with its fixing commit and resolved; 0 unresolved.

Files changed

scripts/protected_suites.py, tests/protected_suite_respellings.yaml, tests/test_session_gates.py, tests/test_session_verbs.py, tests/test_session_confinement.py, tests/test_doxbench_share.py, tests/test_staging_workbench.py (T026's seven), plus three files the ruling at comment 6016648451 adds to T026's Files:

• tests/test_protected_suite_check.py, the holder's answer to point 4;
• T020's tests/conftest.py and tests/test_host_plane.py, Brett's points 2 and 3, edited once T020, U-1: the governed host for the governed suites that drive the gate verbs (plan 038, P4F-5) #39 landed.

What remains, and its trigger

• The holder's word on the three flagged respellings. Nothing else in this PR waits.
• If main moves before landing, the lander merges it, never by rebase.

🤖 Generated with Claude Code

[sourcery-ai]

Reviewer's Guide

Adds R-1 (a)'s span-kind support to the protected-suite allow-list, allowing admitted edits inside pre-existing module-level constants while enforcing strict schema, naming, AST scope, and before/after containment checks.

Flow diagram for validating an admitted span edit

flowchart TD
    A[Allow-list entry] --> B[_check_keys]
    B --> C{admitted entry names span?}
    C -->|No| D[_check_spellings validates test]
    C -->|Yes| E[_check_spellings validates module-level name]
    E --> F[_span_lines parses before text]
    F --> G{Exactly one module-level assignment?}
    G -->|No| H[Reject entry]
    G -->|Yes| I[_inside_the_span checks old text]
    I --> J[_inside_the_span checks new text]
    J --> K{Both contained in span?}
    K -->|No| H
    K -->|Yes| L[Admit edit]

Loading

File-Level Changes

Change	Details	Files
Extend protected-suite allow-list entries to admit edits within existing module-level constants via a new span target.	Document the span semantics and validation rules for admitted entries. Add schema/key validation so admitted entries use either test or span, while respelling entries remain test-based. Validate span names and resolve them to exactly one module-scope assignment, excluding functions, classes, imports, duplicate bindings, and multi-target assignments. Verify span edits are contained within the named constant both before and after the landing, without allowing the span itself to be added.	scripts/protected_suites.py

---

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

Span validation has confinement gaps, lacks tests and manifest entries, and leaves contradictory test documentation.

Review effort: Balanced
Findings: 1 · 1 · 4

Open (6)

• Account for all module-scope binding forms · New
• Prevent spans from including adjacent same-line statements · New
• Add automated coverage for span allow-list validation · New
• Record admitted span edits in the allow-list · New
• Update docstring to reflect route ownership · New
• Correct documentation for relocated route constants · New

What changed in this PR

Implements plan 038’s protected-suite allow-list updates and repairs governed tests after the openDox/openXdox split.

Changes:

• Adds module-level span allow-list validation.
• Records governed test respellings and relocated ownership assertions.
• Updates tests for relocated CLI, projection, schema, and web modules.

File	Description
scripts/​protected_suites.py	Adds span validation.
tests/​protected_suite_respellings.yaml	Records governed edits.
tests/​test_staging_workbench.py	Updates web ownership assertions.
tests/​test_session_verbs.py	Respells relocated CLI/generator references.
tests/​test_session_gates.py	Respells gate verb references.
tests/​test_session_confinement.py	Uses the relocated projection module.
tests/​test_doxbench_share.py	Locates split modules and packaged schema.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

Span uniqueness misses valid Python binding forms, and chain documentation still contradicts the governing 12.5 ruling.

Review effort: Balanced
Findings: 1 · 2 · 1

Open (4)

• Account for all module-scope binding forms
• Update chain-enabled caller model and documentation for F12.1/12.5 · New
• Prevent spans from including adjacent same-line statements
• Add automated coverage for span allow-list validation

Resolved since last review (3)

• Correct documentation for relocated route constants
• Update docstring to reflect route ownership
• Record admitted span edits in the allow-list

[Copilot]

Copilot review overview

🟡 Changes recommended

The staging-workbench harnesses derive display data without registering the required openDox host, causing ProfileNotRegistered.

Review effort: Balanced
Findings: 1

Open (1)

• Register staging workbench host in governed host fixture · New

Resolved since last review (7)

• Account for all module-scope binding forms
• Update chain-enabled caller model and documentation for F12.1/12.5
• Prevent spans from including adjacent same-line statements
• Correct documentation for relocated route constants
• Update docstring to reflect route ownership
• Record admitted span edits in the allow-list
• Add automated coverage for span allow-list validation

[Copilot]

Copilot review overview

🔵 Needs a closer look

The governance-sensitive validator and large chained allow-list require final human validation despite passing CI.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Register staging workbench host in governed host fixture

[Copilot]

Copilot review overview

🟡 Changes recommended

The schema test bypasses the repository’s mandatory packaged-copy digest verification.

Review effort: Balanced
Findings: 1

Open (1)

• Read packaged schema via verified contract APIs · New

[Copilot]

Copilot review overview

🔵 Needs a closer look

The governance-sensitive AST validator and large historical blob chain warrant final human review.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Read packaged schema via verified contract APIs

[sonarqubecloud]

Quality Gate passed

Issues
2 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

[Copilot]

Copilot review overview

🔵 Needs a closer look

This draft changes a governance boundary and a large blob-chained allow-list while three entries still await holder approval.

Review effort: Balanced
Findings: None

[sourcery-ai]

Sorry @brettheap, your pull request is larger than the review limit of 150,000 diff characters

[brettheap]

READY at 9c29855

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

Holder, at READY: T026 (U-7), the allow-list for 12.5's governed suites, with R-1 (a)'s span kind. Lane openXfactory-3's READY-CANDIDATE is 6026548899.

• The three flagged in-test respellings are ALREADY ADMITTED under CF-4 by holder ruling 6020859092:

  • cli_gate in the two gate-off descriptor tests;
  • the sync script's one home on the import path in the notebook-refresh test.

  T026's count moves from the plan's 17 to 20. T002 batch 2 records it.

• Gates at the head:

  • CLEAN against main f70bc9c3, as this ruleset requires;
  • checks: validate (run 37517336710) and SonarCloud succeed, and Sourcery is skipped;
  • Copilot at 9c29855c raises no findings;
  • 9 threads, 0 unresolved;
  • 0 closing references and 0 keywords.

• The falsifier: --chains reads "ok: 8 protected edit(s), each entered and holding"; composed, the 16 governed suites go 800/842 → 842/842 with 0 regressed; the lone CI form reads 1146/1142/4.

• Next: openXdox-code's ruleset is strict. After this lands, each queued PR merges main.

[brettheap]

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

LANDED — lane openxfactory-4, 2026-10-06T22:35:47Z, PR #43 → 36bbef7 (opensoft/openXdox-code main; plain gate)

Brett: plan 038 RULED incl. lane openxfactory-4 lands every PR (#656 6013547504); Start release 2 (#656 6001702967)