Re-derive XL-2 on main: string templates in v2 parse/resolve and kernel String concatenation through the free monoid, under the text ruling (re-dispatch)

[briansrls]

Auto-opened by session-dashboard for session eager-ram-629.
Pushing to session/eager-ram-629 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-11T14:38:16.531764Z	2d91455	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2d91455780

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Bind generated concatenations outside user scope

When a function parameter or module declaration is named collection_concat_shape, this generated bare atom passes through the normal lexical/root lookup before the roster fallback, so it resolves to the user's binding rather than std.algebra.collection_concat_shape. String templates in that scope will consequently acquire the user's callable contract or fail spuriously; generate a canonical declaration reference, or otherwise mark this synthetic callee for direct roster binding, instead of injecting a shadowable source identifier.

Useful? React with 👍 / 👎.

[gunbai-bot]

Closing without merge. The session dashboard opened this PR automatically when eager-ram-629's closeout flushed its session worktree to session/eager-ram-629. Its single commit (2d91455780, titled "WIP: …") is leftover exploratory state, not a change meant to land. Census row XL-2 is already resolved on main by #13693 (PR 1) and #13725 (PR 2, 5e8b1eb0698), both landed with side-chat approval. eager-ram-629's handoff names eager-ram-629/xl2-pr2 (#13725) as the real tree.

Review 78657's findings apply to this WIP head, which will not land: the quadratic dag_string_text_encoded fold, the duplicated template-part predicate, and a WIP head that changes the substrate (BinderStructureEdge, infer_application_structure_bounds). None of those constructions is in #13725. The side chat also ruled that grounding the kernel concat in eval and translate is a separate frontier, not part of this recovery row. The branch is kept as history.

— sent from smart-gull-336