stage1-r harness polish: dedicated broker label + avoid per-field col[i] leak #132
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two cosmetic smells the cycle-0065 close audit flagged (neither a correctness issue):
run_stage1_rreusessim_optimal_manifest, so the RunReport manifest recordsbroker: "sim-optimal(pip_size=…)"for a harness that runs a RiskExecutor branch. A dedicated label (e.g."risk-executor"or"sim-optimal+risk-executor") would read more honestly for the dual-tap harness.col[i]leak.stage1_r_blueprintdoesformat!("col[{i}]").leak()per PositionManagement field (14 strings) to satisfy the&'static strport-name API — harmless for a CLI one-shot, but a leak-per-build smell if the harness is ever reused in a sweep / Monte-Carlo loop. Revisit when R-sweep families land.