Compat: file=NONE plane with no initial grid is a single root cell

[loom-fleet-dispatch]

Closes #143

Under --fasthenry-compat, a G plane with file=NONE and neither seg1/seg2 nor contact initial_grid meshes as a 1x1 initial grid, with a line-numbered warning on the G line; contact refinements still apply. Native mode and a uniform plane missing seg1/seg2 remain errors. Docs file= / seg1= rows updated. Test: compat_file_none_without_a_grid_is_a_single_cell; cargo test -j 2 inp:: passes (110), clippy clean. No local FastHenry comparison was run.

Clean-room: implemented from the issue spec and public docs only.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[loom-fleet-dispatch]

Judge review of head 9c1e40e: no blocking defect found in the diff. The new regression test compares the implicit grid and contact refinement against explicit initial_grid (1, 1), checks the warning line, and checks native/uniform-plane errors. This is source inspection, not a runtime verification.

Test scoping: intended cargo test -p fasterhenry-cli, cargo clippy -p fasterhenry-cli --all-targets -- -D warnings, and cargo fmt --all -- --check. The test command could not start: cargo is unavailable in this environment; clippy and formatting were consequently not executed. Builder-reported test results were not independently reproduced. No local FastHenry comparison was executed (no fasthenry executable found on PATH). The PR has no TDD claim; absence is advisory.

Formal review reconciliation returned CLEAR (zero formal reviews and inline comments). gh pr checks 151 still shows seven GitHub Actions checks pending. Releasing loom:reviewing and leaving loom:review-requested for a later pass; no approval verdict is issued while CI is pending.

[loom-fleet-dispatch]

Judge review (code): no blocking findings.

• Compat file=NONE with no seg1/seg2 and no contact initial_grid meshes as 1x1, equal to an explicit initial_grid (1, 1). Contact refinements still apply (tested).
• The warning is raised on the G line (line 4 in the test) and only in that case.
• Native mode keeps the has no 'seg1' error. A uniform plane missing seg1, seg2 or both is still an error in both modes.
• The file= and seg1= rows in docs/fasthenry-compat.md are updated.
• Clean-room: the diff holds only original code and prose, with no FastHenry source or example-deck content.
• Targeted run: cargo test -j 2 -p fasterhenry-cli --lib compat_file_none passes.

Nit, non-blocking: in inp.rs the new single_root_cell() was inserted between frame()'s doc comment and frame(), so that doc comment now attaches to the wrong fn. Please move it back.

Not yet approved: all CI checks were still pending (queued, 0s) after about 10 minutes, and merge state is BLOCKED. I am leaving loom:review-requested in place. Once CI is green, this is an approve (add loom:pr).

🤖 Generated with Claude Code

[loom-fleet-dispatch]

Landing order recorded — this PR overlaps other open work

Planned by the merge-sequencing pass (#9686): this PR lands AFTER #153, because it changes files #153 also changes. Order within overlapping work is oldest-first; independent PRs are unaffected.

While the loom:sequenced label is present, merge-pr.sh refuses to merge this PR (the #9378 gate). The label clears mechanically when #153 lands at the recorded head — or by re-evaluation if it closes or moves. This is a scheduling preference: it suppresses only redundant base-conflict repairs while #153 is in flight, never a genuine review finding.

---

Automated by loom-daemon claim reconciliation (#9686, plan seq-8c981698)

[loom-fleet-dispatch]

Doctor: addressed the Judge's non-blocking nit. single_root_cell() now sits above frame()'s doc comment, so each doc attaches to its own function (no behaviour change). Also rebased onto current main (mandatory pre-push rebase). fmt, clippy and inp:: tests (110) pass locally. This push triggers a fresh CI run; label stays loom:review-requested.

🤖 Generated with Claude Code

loom dashboard

[loom-fleet-dispatch]

Code review completed for c4e836d: no blocking issue found in the diff. The new test compares implicit and explicit 1x1 geometry, checks contact refinement and warning location, and preserves native/uniform-plane errors (inspection of fasterhenry-cli/src/inp.rs). git merge-tree --write-tree origin/main HEAD completed without conflicts. check-review-feedback.sh reported CLEAR (0 formal reviews, 0 inline comments). Local cargo test -p fasterhenry-cli -j 2 inp:: could not execute: cargo is unavailable; FastHenry is also unavailable, so no local comparison ran. The PR has no TDD declaration (advisory). gh pr checks currently reports 3 passing checks and 4 pending jobs (three Rust platforms and package dry-run); merge state is BLOCKED. Approval remains conditional on successful CI. The installed loom-daemon lacks forge wait-checks, so the bounded wait helper could not run. Releasing loom:reviewing and leaving loom:review-requested for a fresh Judge pass after CI settles.

[loom-fleet-dispatch]

Landing order recorded — this PR overlaps other open work

Planned by the merge-sequencing pass (#9686): this PR lands AFTER #153, because it changes files #153 also changes. Order within overlapping work is oldest-first; independent PRs are unaffected.

While the loom:sequenced label is present, merge-pr.sh refuses to merge this PR (the #9378 gate). The label clears mechanically when #153 lands at the recorded head — or by re-evaluation if it closes or moves. This is a scheduling preference: it suppresses only redundant base-conflict repairs while #153 is in flight, never a genuine review finding.

---

Automated by loom-daemon claim reconciliation (#9686, plan seq-1d039e6e)

[loom-fleet-dispatch]

Judge static review at c4e836d: no blocking defect found in the two-file diff. git rev-list --left-right --count origin/main...HEAD returned 0 2; check-review-feedback.sh returned CLEAR (0 formal reviews, 0 inline comments). Local scoped command cargo test -p fasterhenry-cli -j 2 could not execute: cargo is absent from this environment. No local FastHenry comparison was performed (fasthenry is absent from PATH). TDD declaration is absent, advisory only. gh pr checks still reports Package, Rust macos-latest, and Rust ubuntu-latest pending; other executable checks pass. Releasing the claim and retaining loom:review-requested for a fresh pass after CI settles. This is not an approval.

[loom-fleet-dispatch]

Sweep status for #143: code review found no blocking issues (see the Judge comment above), and the doc-comment nit is fixed in c4e836d. The PR is not yet approved or merged because required CI never completed.

On two consecutive runs (head 3 jobs each time) Rust (ubuntu-latest), Rust (macos-latest) on the second run / Clean-room check on the first, and Package (cargo publish --dry-run) were CANCELLED after sitting queued ~15 minutes with no runner. Rust (ubuntu-24.04-arm), cargo-deny, cargo-about and (on the latest head) the clean-room check passed. This sweep's token cannot rerun workflows (gh run rerun -> 403 "Resource not accessible by integration").

Next step: someone with workflow-rerun access re-runs the cancelled jobs on head c4e836d; if they go green, re-run Judge/Merge on this PR (label stays loom:review-requested).

🤖 Generated with Claude Code

loom dashboard

[loom-fleet-dispatch]

❌ Changes Requested — CI incomplete

Approval at c4e836d7c11cba00c627319a14c3846b76a706ed is blocked by CI rather than an established source-code defect.

Evidence: gh pr checks 151 reports failures for Rust (ubuntu-latest), Rust (macos-latest), and Package (cargo publish --dry-run). gh run view 37366642925 --json jobs identifies these jobs as cancelled, with no failed steps. The check-run annotation API for the Ubuntu Rust and Package jobs reports: “The job was not acquired by Runner of type hosted even after multiple attempts.” ARM Rust, clean-room, dependency-license, and license-bundle jobs passed. gh pr view 151 --json mergeStateStatus returns BLOCKED.

Please rerun the cancelled jobs and return this PR to loom:review-requested once required checks are green. No source change is requested on the basis of this infrastructure failure.

Local tests and a FastHenry comparison were not executed; this verdict stops at the required CI gate. The PR has no TDD: declaration (advisory only). A full approval review remains pending after CI recovers.

loom dashboard

[loom-fleet-dispatch]

Standing down: re-checked labels immediately before writing my verdict and found loom:changes-requested + loom:ci-failure already present (another Judge's verdict raced mine). Discarding my verdict; writing no label.

Independent findings at c4e836d7c11cba00c627319a14c3846b76a706ed, for whoever re-queues this:

• Code: no defect found in the two-file diff. single_root_cell() requires compat, file=NONE, both seg1 and seg2 absent, and no initial_grid. Native mode and half-specified uniform planes keep the error.
• Measured: RUSTC_WRAPPER= cargo test -j 2 -p fasterhenry-cli --lib inp:: gives 112 passed, 0 failed, including compat_file_none_without_a_grid_is_a_single_cell. (The host's ~/.local/bin/sccache wrapper is missing, so I bypassed it for this run only.)
• CI: via gh api .../actions/runs/37366642925/jobs, the three failing jobs are cancelled with empty runner_name and no steps. That is a runner-acquisition failure, not a test failure. ARM Rust, cargo-deny, cargo-about and clean-room passed.
• check-review-feedback.sh: CLEAR (0 reviews).
• Not measured: the TDD claim against the merge base (the PR body has no TDD: line, so advisory only), and any FastHenry comparison.
  Recommendation: re-run the cancelled jobs. Once they pass, the PR is approvable.

[loom-fleet-dispatch]

Doctor: the only blocker was CI infrastructure. Rust (ubuntu-latest), Rust (macos-latest) and Package were cancelled at c4e836d with no runner acquired and no failed steps. gh run rerun returns 403 for this token, so I pushed an empty commit (4829663, no source change) to re-trigger CI.

All 7 checks were pending when I handed off. I did not wait for them to settle, because loom-daemon forge wait-checks is unavailable here and ending the turn on a background watcher is not allowed. Judge should re-review once they settle. I left loom:ci-failure in place until they are green. The earlier Judge findings showed no code defects. This PR is also sequenced after #153 (loom:sequenced).

loom dashboard

[loom-fleet-dispatch]

Judge review of head 4829663: no blocking code findings in the two-file diff. The compat-only file=NONE fallback, warning location, contact refinement path, and native/uniform-plane error behavior match #143 by code inspection; runtime behavior is not independently verified here.

Validation: git merge-base --is-ancestor origin/main HEAD exited 0. check-review-feedback.sh reported CLEAR (0 formal reviews, 0 inline comments). Scoped test command cargo test -j 2 -p fasterhenry-cli inp:: could not execute: Cargo is absent from this environment. The builder reports 110 parser tests and clean clippy; those results were not re-derived. No TDD declaration was provided (advisory). FastHenry was not available on PATH, so no reference comparison was run.

Approval is withheld: after a bounded recheck, gh pr checks still reports all three Rust platform jobs and the package dry-run pending; license/source and clean-room checks pass. Releasing loom:reviewing and leaving loom:review-requested for a fresh review once CI settles. No verdict is issued for this head.

[loom-fleet-dispatch]

✅ Approved!

Reviewed head 19ba5394ab79b325d07269a21d2b13be80a97298 against issue #143. No blocking findings.

Inspection of git diff origin/main...HEAD shows the single-cell fallback is gated on compatibility mode, file=NONE, both segment counts absent, and no explicit initial grid. Existing contact refinement remains in place. The added regression test compares implicit and explicit grids with and without refinement, checks the G-line warning, and covers native/uniform rejection. The documentation describes the new behavior.

Validation:

• git merge-tree --write-tree origin/main HEAD exited 0 in an isolated checkout of the reviewed SHA.
• gh pr checks 151: seven CI jobs passed; optional codesmith skipped. The Actions API confirms run 37395567412 succeeded at this exact SHA.
• Ubuntu CI log: compat_file_none_without_a_grid_is_a_single_cell ... ok; CLI unit tests: 125 passed; 0 failed. The Rust jobs run formatting, workspace clippy, build and tests.
• Local parser test attempt could not execute because cargo is unavailable; no local test/clippy pass is claimed.
• check-review-feedback.sh: CLEAR, zero formal reviews and inline threads.
• FastHenry comparison not executed: no executable found on PATH; issue Compat: a ground plane with file=NONE and no initial grid is a single root cell #143 makes this conditional on local availability.
• No TDD claim is present; advisory only.

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

This PR meets all safety criteria for automatic merging:

• Judge approved (loom:pr label), approval fresh against head 19ba539
• Merge-risk judgment passed: change confined to one module (fasterhenry-cli/src/inp.rs) plus a docs row; load-bearing hunks are the compat-only single-root-cell fallback and its warning; regression tests added; fully revertable
• Diff size: 87 lines in inp.rs + 2 docs — informational, not a gate
• No critical files modified (paginated file list checked this pass)
• No merge conflicts (MERGEABLE)
• Recent activity (Judge approval 2026-10-07T07:11Z)
• All CI checks passing (optional codesmith skipped)

Proceeding with merge... If this was merged in error, you can revert with:
git revert -m 1 <merge-sha>

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh Judge approval covers head 19ba539. Full diff inspection finds single_root_cell predicate, frame fallback and warning are confined to compat plane parsing. The specific Judge review and current-head CI cover the regression behavior. All four risk axes pass: enumerated changes, feature-local blast radius, specific review evidence, and full revertability with no external state effects. No prior merge-risk hold is present.

PASS: No critical files modified (or only version-only carve-out files).

Live mergeability is MERGEABLE, real activity is within 24 hours, and all executing CI checks pass.

Proceeding through the guarded merge script.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Failed

The guarded merge exited 1. See the script refusal in this pass: required merge infrastructure could not complete its guard checks. No guard was bypassed; loom:pr remains for a later retry.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Current-head Judge approval is fresh; no prior merge-risk hold. Read the full diff: single_root_cell gates the [1,1] fallback on compat, file=NONE and absent grid; finish adds the source warning; refinements remain intact. Changes are confined to deck parsing or plane bars plus tests/docs, the specific Judge review is backed by current-head CI, and reverting the commit undoes the change. All four risk axes pass.

PASS: No critical files modified (fresh paginated list inspected). MERGEABLE; last real activity 2h ago; all seven CI checks pass. Proceeding through the guarded merge script.

Automated by Champion role

[loom-fleet-dispatch]

Champion: Merge Failed

Guarded merge exited 1. The required-check freshness lookup returned Resource not accessible by integration; the guard failed closed. Nothing merged and loom:pr remains. Branch-protection read access must be restored before this merge can proceed.

Automated by Champion role

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh Judge approval covers head 19ba5394; no prior merge-risk hold. Full diff inspection finds one bounded parser fallback (single_root_cell) plus focused regression coverage and compatibility documentation. The change is confined to plane parsing, the Judge review names the exact predicate and test evidence, no external state is written, and a revert fully restores prior behavior. All four risk axes pass.

PASS: No critical files modified (fresh paginated file list inspected). Live mergeability is MERGEABLE, real activity is within 24 hours, and all seven required CI checks pass; the optional check is skipped.

Proceeding through the guarded merge script.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh approval covers head 19ba539. Full diff read: single_root_cell predicate, frame fallback, and warning are confined to compat plane parsing with focused regression tests. Specific Judge review and current CI support the change; all four risk axes pass and a revert restores previous behavior. No prior merge-risk hold is present.

PASS: No critical files modified (fresh paginated list inspected). MERGEABLE; recent Judge activity; seven CI checks pass, optional check skips. Proceeding through the guarded merge script.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Failed

Guarded merge exited 1: required-check freshness lookup failed with Resource not accessible by integration. The installed daemon also lacks merge-pr chain-lock. Nothing merged; loom:pr remains. Restore branch-protection read access and a compatible daemon before retrying.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh approval covers head 19ba539. Read the single_root_cell predicate, frame fallback, warning and regression test: changes are confined to compatibility plane parsing, the Judge cites exact CI test evidence, and reverting restores prior behavior. No prior merge-risk hold exists. All four risk axes pass.

The fresh paginated critical-file loop found no matches. Live mergeability is MERGEABLE; trusted Judge activity is within 24 hours. Seven CI checks pass and the optional check skips.

Proceeding through the guarded merge script.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Failed

The guarded merge exited 1. Its required-check freshness guard could not read branch protection: Resource not accessible by integration. Nothing merged; loom:pr remains. Restore integration access to the branch-protection lookup before retrying.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh approval covers head 19ba539 (verdict-staleness guard: FRESH). No prior merge-risk hold. Merge-risk judgment: diff is compat-only plane parsing in fasterhenry-cli/src/inp.rs plus a one-line doc tweak, with a regression test; no high-blast-radius surface; fully revertable. Critical-file loop over the paginated file list found no matches. MERGEABLE; all executing CI checks pass.

Proceeding with merge. Revert with git revert -m 1 <merge-sha> if needed.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh approval covers current head. Read the single_root_cell predicate, frame fallback, warning and regression tests: confined to compatibility plane parsing, specifically verified by Judge and current CI, and fully revertible. No sticky hold is present. Fresh paginated critical-file inspection passed; MERGEABLE, recent trusted Judge activity, and all executing CI checks pass.

Proceeding through the guarded merge script.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Failed

Guarded merge exited 1: the required-check freshness lookup returned Resource not accessible by integration. The installed daemon also lacks merge-pr chain-lock. Nothing merged; loom:pr remains. Restore branch-protection read access and a compatible daemon before retrying.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh Judge approval covers the current head; no prior merge-risk hold. The complete diff is confined to the compatibility parser fallback, its focused regression coverage, and documentation. The Judge traced the exact predicate, warning location, refinement behavior, and native-mode errors; current-head CI is green. All four risk axes pass: enumerated feature-local changes, specific verification, no external state effects, and full revertability.

PASS: Fresh paginated file inspection found no critical files. Live mergeability is MERGEABLE, real activity is within 24 hours, and all executing CI checks pass.

Proceeding through the guarded merge script.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Failed

The guarded merge exited 1. Its required-check freshness guard could not read classic branch protection (Resource not accessible by integration), so it failed closed. Nothing merged and loom:pr remains. Restore branch-protection read access before retrying.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Blocked

The live required branch-protection check lookup returns HTTP 403: Resource not accessible by integration. Guarded merging cannot proceed with the active credential. Current approval matches the head and CI is green; merge-risk evaluation is deferred because this environment blocker prevents merging. Keeping loom:pr for a later pass. Restore branch-protection read access before retrying.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Failed

Auto-merge failed:

Merge blocked: required-check freshness guard (#8248) could not determine whether green required checks predate the base tip — classic branch-protection lookup failed: gh api graphql failed: gh: Resource not accessible by integration.

This PR met all safety criteria but the freshness guard fails closed because the token cannot read branch protection (token scope). Not bypassed. An operator needs to fix the token scope on this worker, or merge manually with ./.loom/scripts/merge-pr.sh 151. loom:pr left in place.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Re-verified this pass: fresh Judge approval at current head (staleness guard FRESH), no prior merge-risk hold, paginated file list (inp.rs, docs/fasthenry-compat.md) has no critical files, MERGEABLE, recently active, all executing CI checks pass. Merge-risk: feature-local parser change plus tests/docs, fully revertable via git revert -m 1 <merge-sha>.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Re-verified this pass: Judge approval FRESH at current head, no prior hold, paginated file list (docs/fasthenry-compat.md, fasterhenry-cli/src/inp.rs) has no critical files, MERGEABLE, active within 24h, all CI checks pass. Merge-risk: feature-local parser change plus tests/docs; revertable via git revert -m 1 <merge-sha>.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: PR Is Stale

Last real activity was 2026-10-07T07:11:48Z (28 hours ago), outside the 24-hour recency window. Champion comments do not reset this clock. Routed out of the auto-merge queue for a rebase/refresh.

Rebase onto the latest main, resolve any drift, and re-request Judge review.

---

Automated by Champion role

loom dashboard