Deck reader: case-insensitive node names and .equiv pseudonyms

[loom-fleet-dispatch]

Closes #156

Part of #76.

Summary

• Case-insensitive node names (all modes). Names keys every node name by its lowercase form, so N3 declared and n3 referenced are one node in every position: node declarations, in-plane node declarations (and contact equiv_rect/connection nodes), E endpoints, .external, .equiv. A case-only repeat (n1 then N1) is a line-numbered duplicate-definition error naming both spellings and the first line. Output choice: names are lowercased (the default <+>/<-> port label); an explicit .external label is a label, not a node name, and is kept as written. unknown node errors still quote the name as the deck wrote it.
• .equiv pseudonyms (all modes, User's Guide §1.3.7). The first defined name in the list is canonical. Other defined names alias to it as before. Undefined names become pseudonyms for it wherever they stand in the list. If no name in the list is defined, the error is no defined node in .equiv. Declaring a node under a pseudonym's name is the duplicate error, which names the pseudonym's line. There are still no forward references for E endpoints and .external.
• --fasthenry-compat only: .equiv naming one node twice (.equiv x x, or two names already joined) is a ParseWarning and a no-op, and the rest of the list is still joined. Natively it is still an error.
• docs/fasthenry-compat.md: reversed the "Node/element names case-sensitive" row and added the rationale (guide §1.1/§1.3, the guide's own §1.2 N3 / .equiv nin n3 deck, and the change from a silent reinterpretation to an explicit duplicate error). Added rows for pseudonyms and for the compat self-equiv warning, and reworded the group= row (group names stay case-sensitive as this reader's own extension). Also updated the module docs, the ParseOptions/ParseWarning docs, the --fasthenry-compat help text and the CHANGELOG.

Tests (fasterhenry-cli/src/inp.rs)

• node_names_are_case_insensitive_in_every_position: a mixed-case deck equals the lowercase one, and the port labels are checked.
• in_plane_node_names_are_case_insensitive: in-plane nodes in mixed case, used as segment endpoints and in .equiv and .external.
• case_only_duplicate_node_names_are_errors: plain and in-plane collisions, plus the exact-repeat message.
• forward_node_references_are_errors
• equiv_undefined_names_become_pseudonyms: alias first, last, middle and mixed-case, plus the guide's nin/n3 shape.
• equiv_with_no_defined_node_is_an_error
• defining_a_node_after_it_became_a_pseudonym_is_an_error
• equiv_of_a_node_with_itself_warns_under_compat: native error, compat warning with deck equality, and a repeat inside a longer list.

Verification

• cargo test -p fasterhenry-cli: 132 passed
• cargo clippy --workspace --all-targets -- -D warnings: clean
• cargo fmt --all -- --check: clean

Clean-room: implemented from the issue spec and the public User's Guide only. No FastHenry source or example decks were consulted.

🤖 Generated with Claude Code

---

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

[loom-fleet-dispatch]

Code review completed for head 2b47666; no blocking code findings from inspection of the full diff and issue #156. Approval remains conditional on completed CI.

Verification:

• git merge-tree --write-tree origin/main HEAD exited 0: merges without conflicts.
• check-review-feedback.sh --number 164 --head-sha 2b47666f163c387ca5ffdd8478fbb27f70d7278c reported CLEAR, zero formal reviews and zero inline comments.
• Test scoping: cargo test -p fasterhenry-cli selected for the changed CLI crate. Execution unavailable: timeout: failed to run command ‘cargo’: No such file or directory. The PR's 132-test, clippy and formatting results are builder-reported, not independently reproduced. No TDD declaration is present (advisory only).
• gh pr checks 164, rechecked after a bounded 40-second wait: Rust jobs for Ubuntu, ARM and macOS remain pending; clean-room, dependency licenses, package dry-run and license bundle checks pass. No completed check failed.

Releasing loom:reviewing and keeping loom:review-requested for a fresh Judge pass after CI settles. No approval or changes-requested verdict is issued.

[loom-fleet-dispatch]

Judge pass: still carries a fresh loom:reviewing claim (claimed 2026-10-06T01:09:05Z, idle 26m) — standing down without reclaiming. Not stomping.

Stand-down passes against this claim: 7 of 3 before the bounded fallback force-reclaims it. This comment is edited in place on each pass rather than reposted (#5123, #6514).

[loom-fleet-dispatch]

Landing order recorded — this PR overlaps other open work

Planned by the merge-sequencing pass (#9686): this PR lands AFTER #162, because it changes files #162 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 #162 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 #162 is in flight, never a genuine review finding.

---

Automated by loom-daemon claim reconciliation (#9686, plan seq-50a92217)

[loom-fleet-dispatch]

✅ Approved!

Reviewed fasterhenry-cli/src/inp.rs (name-table rewrite, apply_equiv, tests), docs/fasthenry-compat.md, cli.rs help and CHANGELOG at head 2b47666.

• Case folding: Names is keyed by node_key (ASCII lowercase) with a single lookup/define path, so declarations, in-plane nodes, E endpoints, .external and .equiv all agree. Duplicate errors name both spellings and the first line. An explicit .external label is kept as written.
• .equiv: the first defined name is canonical and undefined names become pseudonyms pointing at its slot. lookup follows alias chains, so a later alias of the canonical node still resolves. No-defined-name and declare-after-pseudonym are line-numbered errors. The self-equiv case is a native error and a compat ParseWarning that keeps joining the rest of the list.
• Tests: the eight new tests cover every position, in-plane nodes, case-only duplicates, forward references, pseudonym placement (first/middle/last/mixed case), and the compat/native split.
• CI (gh pr checks): clean-room, cargo-deny, package, cargo-about and Rust on ubuntu, ubuntu-arm and macOS all pass; merge state CLEAN; check-review-feedback.sh → CLEAR.
• Not re-run locally: the PR's stated test counts (132 passed, clippy/fmt clean) are from the author; I relied on CI for the same head rather than rebuilding on the shared worker.

PR description uses Closes #156 with Part of #76, which is correct.

loom dashboard

[loom-fleet-dispatch]

Champion: Cannot Auto-Merge

The live required-check freshness guard refused this PR because its classic branch-protection GraphQL lookup returned Resource not accessible by integration. Restore credential access before retrying. Keeping loom:pr; no guard bypassed.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Cannot Auto-Merge

Required-check freshness guard failed closed (exit 2): classic branch-protection lookup returned Resource not accessible by integration. CI passes; current authentication cannot verify freshness. No merge attempted.

Keeping loom:pr for re-evaluation.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

This PR meets all safety criteria for automatic merging:

• Judge approved (loom:pr label)
• Merge-risk judgment passed: the enumerable load-bearing changes are the node-name table and .equiv resolution in one parser module, with eight focused regression tests and a detailed function-level Judge review; no external state is written and the commit is fully revertable
• Diff size: 504 lines (+471/-33) — informational, not a gate
• No critical files modified
• No merge conflicts
• Updated recently (5 hours ago)
• All CI checks passing

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]

Landing order recorded — this PR overlaps other open work

Planned by the merge-sequencing pass (#9686): this PR lands AFTER #161, because it changes files #161 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 #161 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 #161 is in flight, never a genuine review finding.

---

Automated by loom-daemon claim reconciliation (#9686, plan seq-942fb103)

[loom-fleet-dispatch]

Champion Auto-Merge

This PR meets all safety criteria for automatic merging:

• Judge approved (loom:pr; fresh verdict for 2b47666)
• Merge-risk judgment passed: the load-bearing hunks are the parser name-key table and .equiv alias/pseudonym logic in one module; the Judge traced those exact paths and edge cases, CI covers the focused tests, the change writes no external state, and revert fully restores prior behavior
• Diff size: 504 lines (+471/-33) — informational, not a gate
• No critical files modified (fresh paginated file-list check)
• No merge conflicts
• Updated recently
• All CI checks passing

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

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Merge Failed

Auto-merge failed because the required-check freshness guard could not query branch protection (Resource not accessible by integration). The guard failed closed; nothing merged and loom:pr remains.

Restore the integration token's branch-protection read permission or perform an equivalent verified manual merge.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh approval covers current head. Full diff read: Names/node_key centralize case folding and duplicate diagnostics; apply_equiv adds pseudonyms and compat self-join warnings; default labels fold while explicit labels persist. Regression tests cover every name position and alias/error cases. Four axes pass: changes confined to deck parsing plus docs/help, detailed Judge inspection backed by green CI, fully revertible. Fresh complete file list has no critical paths; MERGEABLE, real activity within 24h; seven checks pass, codesmith 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 returned Resource not accessible by integration. Nothing merged; keeping loom:pr. Restore branch-protection read permission before retrying.

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Current-head approval is fresh. Read the parser change and regression coverage: behavior is confined to deck parsing, the Judge review names the affected functions and CI verification, and a revert fully undoes the change. All four risk axes pass, with no prior risk hold. Fresh paginated file inspection passed the critical-file loop. The PR is MERGEABLE, real activity is within 24 hours, and seven CI checks pass with the optional check skipped.

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 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: PR Is Stale

Not updated within the recency window (24h) — routed out of the auto-merge queue for a rebase/refresh.

Next steps:

• Rebase onto the latest main and resolve any drift
• Re-request Judge review to return it to the auto-merge queue

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Verdict anchored to the current head — no marker had been recorded

This PR carries loom:changes-requested, but no verdict-SHA marker was ever written for that verdict, so it was unverifiable: nothing could tell whether it still described the tree in front of it, and it would have survived a force-push undetected — the exact pre-#5686 hazard.

This comment records the head SHA as of now, 2b47666f163c387ca5ffdd8478fbb27f70d7278c. It is not a review and implies no judgment about this tree: the loom:changes-requested label is unchanged. From here on the verdict is invalidatable — if the head moves off 2b47666f163c387ca5ffdd8478fbb27f70d7278c, the stale-verdict pass clears loom:changes-requested and returns the PR to loom:review-requested.

Anchoring bounds future exposure; it cannot reconstruct which tree was actually reviewed. If the head already moved before this comment, treat the verdict with corresponding suspicion.

---

Automated by loom-daemon claim reconciliation (#6319)

[loom-fleet-dispatch]

Judge review of head 56abbb2: no blocking correctness issue found in the four-file diff. Inspected centralized node-name folding, pseudonym creation, alias resolution/compaction, duplicate diagnostics, compat self-equivalence handling, and documentation against #156. The existing worktree matches the PR head and is clean; git rev-list --count HEAD..origin/main returned 0. check-review-feedback.sh returned CLEAR (0 formal reviews, 0 inline comments). No TDD declaration is present; advisory only.

Verification is incomplete: cargo test -p fasterhenry-cli, cargo clippy --workspace --all-targets -- -D warnings, and cargo fmt --all -- --check could not execute because cargo is unavailable on this host. Builder-reported results were not independently verified. gh pr checks currently shows the macOS, Ubuntu ARM, and Ubuntu Rust jobs pending; the other five checks pass. Releasing loom:reviewing and retaining loom:review-requested for a later pass once CI settles. No approval verdict issued.

[loom-fleet-dispatch]

Judge pass: still carries a fresh loom:reviewing claim (claimed 2026-10-07T06:53:09Z, idle 1m) — standing down without reclaiming. Not stomping.

Stand-down passes against this claim: 1 of 3 before the bounded fallback force-reclaims it. This comment is edited in place on each pass rather than reposted (#5123, #6514).

[loom-fleet-dispatch]

✅ Approved!

The implementation satisfies #156. I reviewed the centralized ASCII case-folding in the node registry, declaration/pseudonym duplicate handling, alias-chain resolution and compaction, .equiv canonical-node selection, native-versus-compat self-equivalence behavior, port-label spelling, and the accompanying tests/docs. I found no blocking correctness issue.

Test Scoping

Strategy: changed crate (fasterhenry-cli) via completed CI; local scoped execution was attempted with a private Cargo target but was not runnable because this Judge host has no cargo executable.

CI evidence: all seven checks on 56abbb2b5efb5ef6b347f6eda9c76bfddc264dd5 are successful, including Rust on Ubuntu, Ubuntu ARM, and macOS, clean-room verification, packaging, dependency licensing, and the third-party license bundle.

Additional gates: merge state is CLEAN; the branch is 0 commits behind origin/main; formal-review reconciliation is CLEAR (0 formal reviews and 0 inline comments); git diff --check passed. The PR has no TDD: declaration, noted as advisory per the Judge policy.

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh Judge approval covers head 56abbb2. Full diff inspection finds node_key, Names registry, apply_equiv and default port labels form a bounded node-name parsing change. 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. The required-check freshness guard could not read classic branch protection: Resource not accessible by integration. The installed daemon also lacks merge-pr chain-lock. 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: Names centralizes case folding and duplicate diagnostics; apply_equiv registers pseudonyms and compat self-join warnings; explicit port labels preserve spelling. 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 56abbb2b; no prior merge-risk hold. Full diff inspection finds the node-key registry and .equiv alias/pseudonym paths plus eight focused regression tests. The change is confined to deck name parsing, the Judge review cites the exact behavior and current-head CI 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 required CI checks pass.

Proceeding through the guarded merge script.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion: Cannot Auto-Merge

The guarded merge failed closed because the required-check freshness lookup for classic branch protection returned Resource not accessible by integration. The installed daemon also lacks merge-pr chain-lock.

Nothing merged; keeping loom:pr for re-evaluation. Restore branch-protection read access and roll a compatible daemon before retrying.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Champion Auto-Merge

Fresh approval covers the current head; no prior risk or critical-file hold. Full diff read: node_key and Names centralize case folding, duplicate diagnostics and pseudonym lookup; apply_equiv chooses the first defined canonical node and handles self-equivalence by mode, with eight focused regressions. The specific Judge review cites code and test evidence. All four risk axes pass: enumerated feature-local changes, specific verification, and full revertability without external state effects.

PASS: No critical files modified (or only version-only carve-out files). Fresh paginated loop passed; MERGEABLE, real activity 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

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: Merge Deferred

Current-head approval is fresh, but the required-check freshness guard exited 2: branch-protection lookup returned Resource not accessible by integration. This pass cannot establish merge eligibility. Nothing merged and labels remain unchanged. Restore integration access to the branch-protection lookup 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 node-name parsing and .equiv alias resolution, eight focused regressions, and docs/help. The Judge traced case folding, duplicate diagnostics, pseudonym chains, self-equivalence behavior, and labels; 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: PR Is Stale

Last real activity was 2026-10-07T06:55:41Z (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

[loom-fleet-dispatch]

Stale review verdict cleared — head SHA moved

This PR's loom:changes-requested verdict was rendered against 2b47666f163c387ca5ffdd8478fbb27f70d7278c, but the current head is 56abbb2b5efb5ef6b347f6eda9c76bfddc264dd5. A review verdict is a statement about a specific tree, so it does not survive a rebase, a force-push, or new commits.

• Verdict cleared: loom:changes-requested (recorded for 2b47666f163c387ca5ffdd8478fbb27f70d7278c)
• Returned to the review queue: loom:review-requested (current head 56abbb2b5efb5ef6b347f6eda9c76bfddc264dd5)

Judge will re-evaluate the tree that is actually here now. No judgment about the new tree is implied either way — the old verdict simply no longer describes it.

---

Automated by verdict-staleness-guard.sh (#5686)