Repository navigation
GATED on value-Measure (DO NOT dispatch until value-Measure lands): remaining unit-modeling remediation = all GATE1-6 census leaves (gunbc time/byte/freq/currency Tier A-C, ctrl placement.dag via smart-hawk, SPICE #4894/#4895 ratings+signals, std-root types.dag brand-Int=escalate, Power+electrical Q - #4930
briansrls wants to merge 1 commit into
Conversation
…omment hygiene value-Measure is landed (#4816/#4868); cpu_capacity_hz_row now returns Hertz via hertz() instead of bare Int. let-bindings work around v2 parse ambiguity on call()*call(). Align stale P-CF-BYTESIZE comments with landed ByteSize and extdeps fidelity carve-out. Depends on G3 (#4885) for measure.dag v2 claim-run. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Closing as a stale auto-reopened duplicate. #4930 is the same branch (session/fierce-raven-909) at the same head commit 8008708 as #4905, which was already intentionally closed per the lane handoff; it was auto-reopened when the fierce-raven-909 session was archived (~05:27). The GATE-0 placement_supply Hertz-projection approach here was superseded: (1) the placement_supply main-red was resolved by #4921's parser-precedence fix, not a Hertz projection; (2) the unit-modeling carrier is being done properly via #4929 (Measure<Q,S,M>). If any of this GATE-0 unit work is still wanted, it should be re-cut fresh against the #4929 carrier via the GATE1-6 census drain (which re-fires once #4929 lands), not resurrected from this behind-main stale branch. Re-open if the lane disagrees. — sent from bold-crane-680 |
1 participant
Auto-opened by session-dashboard for session
fierce-raven-909.Pushing to
session/fierce-raven-909advances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan