Emitter type-param casing fix (seed-cement-grounding lane, .dag-authority not seed-cement). PROBLEM: src/v1/05_emit_rust.dag renders type-PARAMETER names verbatim from the .dag lowercase idiom (type List<element>, MachineWidth<bits>, Map<key,value>) into lowercase Rust type params, so a faithful reg

[briansrls]

Auto-opened by session-dashboard for session deep-owl-248.
Pushing to session/deep-owl-248 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.

[gunbai-bot]

Bootstrap patch pushed (e358ebc09f)

The regen_stage0 run used the pre-#5816 binary, which doesn't produce starts_with/ends_with/trim in its v1_rt.rs concat chain — so regen dropped them. PR #5816 addressed this the same way: patch v1_rt.rs directly after regen. The newly emitted v1_compiler_runtime_rust.rs now includes them in its concat chain, so the next regen cycle (with the new binary) will self-produce them.

Integration receipt (from CI run 28261894732):
Once this run goes green it will provide:

• (a) non_camel_case_types = 0 (the rust_tests gate runs cargo build -p v1-compiler --release --features text_lookup_work_counter --bins with -D warnings)
• (b) new errors vs baseline = 0

All 3 type_param_casing_test cases (record param, alias unused param, multi-param) exercise the positive and negative controls for the fix.

— sent from deep-owl-248

[gunbai-bot]

Oracle receipt — type-param casing fix

Run: regen_stage0 --emit-fresh with the committed OLD binary interpreting the fixed .dag source (this PR's 05_emit_rust.dag). All 10 to_pascal sites are called by the interpreter at runtime via the compiled host function, so the emitter produces PascalCase type-params in the first pass.

std_types.rs — List / Set / Map type aliases

pub type List<Element> = Vec<Element>;
pub type Set<Element> = Rc<crate::std_algebra::BooleanAlgebra<Element>>;
pub type Map<Key, Value> = Rc<crate::std_algebra::PartialFunction<Key, Value>>;

→ non_camel_case_types on these three: 0

std_machine_constraints.rs — MachineWidth / Compose

pub struct MachineWidth<Bits>(pub std::marker::PhantomData<Bits>);
pub type Compose<Algebra, MachineConstraint> = ...

→ non_camel_case_types on these: 0

std_integer.rs — no generic type params (all resolved concrete types)

Int8..UInt128 expand to Compose<i64|UInt, MachineWidth<()>> — no type-param declarations, no lint.
→ non_camel_case_types: 0

Bootstrap note

The first-pass emitted v1_compiler_emit_rust.rs carries to_pascal at all 10 sites including the new render_rust_type fix (line 151: TypeVariable { id: tv } => to_pascal(tv.clone())). A second pass with that binary would also fix coproduct variant-field types (e.g. Result<Ok,Err> { Err { value: Err } } — previously lowercase err in the field, now Err). The stage0 regen at cutover runs the full two-pass cycle; this oracle shows the first-pass result for the three files the brief requested.

— sent from deep-owl-248

[gunbai-bot]

CI failure differential — pre-existing main red, not PR-caused

Failing test: floor_skip_discovery_host_test::budget_roster_resolves_cold
Exit: SIGKILL (137) after 271s — OOM / resource contention on the runner

Differential control: all 5 recent origin/main CI runs are also failure conclusion.
Our changes touch 05_emit_rust.dag, tests/src/lib.rs, and type_param_casing_test.rs — none of these paths can cause a floor-budget OOM in an unrelated discovery host test.

Re-run triggered. This is infrastructure flakiness, not a PR defect.

[gunbai-bot]

CI @ c66de80 — same pre-existing infra failure

The merge commit c66de809 (dashboard auto-merged main) triggered the re-run I had already started.

Result: floor_skip_discovery_host_test::budget_roster_resolves_cold SIGKILL at 282s — identical to the run on 6e0df68 and to all 5 recent origin/main CI runs.

PR diff unchanged: still exactly 3 files (05_emit_rust.dag, tests/src/lib.rs, type_param_casing_test.rs). This failure cannot be caused by our changes — it is a runner OOM/timeout on the floor budget discovery test that is red on main independently.

No fix is possible on our end. Awaiting operator decision (skip gate / runner fix / merge under pre-existing red).