briansrls · Feb 19, 2026 · Feb 18, 2026 · Feb 18, 2026 · Feb 18, 2026 · Feb 18, 2026
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -10,6 +10,7 @@ members = [
     "core/test",
     "core/testgen-registry",
     "core/testgen-registry-macros",
+    "core/delegate-macros",
     "core/tool-registry",
     "core/tool-registry-macros",
 
@@ -22,7 +23,6 @@ members = [
     "core/daglang/daglang-derive",
     "core/daglang/daglang-emit",
     "core/daglang/daglang-driver",
-    "core/daglang/daglang-exec-bridge",
     "core/daglang/daglang-cli",
 
     # Library crates (DAG op libraries)

diff --git a/TODO/README.md b/TODO/README.md
@@ -1,77 +1,9 @@
-# TODO — DSL Program Index
+# TODO
 
-This folder is now organized around the DSL adoption program.
-Primary roadmap reference: `docs/design/v4/dsl-roadmap.md`.
-**Consolidated execution plan**: [`docs/design/v4/consolidated-worker-plan.md`](../docs/design/v4/consolidated-worker-plan.md) — unified dependency DAG, wave decomposition, and task assignments across all tracks.
+**Task sheet**: [`tasks.md`](tasks.md) — monolithic, dependency-ordered, parallelizable.
+**Roadmap**: [`docs/design/v4/consolidated-worker-plan.md`](../docs/design/v4/consolidated-worker-plan.md)
+**Archive**: [`TODONE/`](TODONE/) — completed items with dates.
 
-Last reconciled: 2026-02-18
+Last updated: 2026-02-18
 
-## Execution Order
-
-1. Track A: DSL core compiler capabilities
-2. Track B: DSL migration targets (move existing Rust DAG graphs to `.dag`)
-3. Track C: modeling foundations needed for non-fragile DSL migration
-4. Track D: runtime/test hardening required for confident rollout
-5. Track E: domain parity and adjacent programs
-6. Track F: general debt ledger
-
-## Track Definitions
-
-| Track | Purpose |
-|------|---------|
-| A — DSL Core | Language/compiler/runtime features needed by the roadmap |
-| B — Migration Targets | Existing workflows that should be rewritten in DSL now |
-| C — Modeling Foundation | Canonical models (platform, env, transport, composition) that remove stringly/manual wiring |
-| D — Runtime/Test Hardening | Logging, testgen, codegen quality, and execution safety for DSL-generated flows |
-| E — Domain Parity | Product/domain workstreams that should become DSL consumers over time |
-| F — Debt Ledger | Generic cleanup and fallback debt not tied to one feature |
-
-## Active Docs By Track
-
-| Doc | Track | DSL Alignment | Status |
-|-----|-------|---------------|--------|
-| `TODO/TODO_URGENT_dsl_migration.md` | B | Primary migration backlog | Active |
-| `TODO/TODO_workflow_audit.md` | B | Migration inventory + sequencing input | Draft |
-| `TODO/TODO_URGENT_anemic_modeling_audit.md` | C | Cross-cutting model consolidation | Active |
-| `TODO/TODO_URGENT_browser_modeling.md` | C | Platform/environment modeling prerequisite | Active |
-| `TODO/TODO_URGENT_platform_toolchain_modeling.md` | C | Target/platform/toolchain canonicalization | Active |
-| `TODO/TODO_transport_dag_migration.md` | C | Bring transport executor behavior into DAG/testing model | Draft |
-| `TODO/TODO_URGENT_logging_consolidation.md` | D | Execution observability hardening for generated workflows | Active |
-| `TODO/TODO_testgen_seed_policy_postmortem.md` | D | Testgen semantic input correctness | Partially complete |
-| `TODO/design-codegen-quality.md` | D | Generated code idiom/IR quality | Active |
-| `TODO/TODO_credential_lifecycle.md` | E | Credential/service modeling for DSL consumers | Draft |
-| `TODO/TODO_gcp_infra_parity.md` | E | Domain parity backlog (DSL consumer target) | In Progress |
-| `TODO/llm-code-review-pipeline.md` | E | Adjacent DAG pipeline architecture | V0 complete, follow-up open |
-| `TODO/consolidation.md` | F | Generic consolidation backlog | Ongoing |
-| `TODO/TODO_hacks.md` | F | Fallback/debt register | Active |
-
-## Conventions
-
-- Every active TODO doc should include:
-  - `Status`
-  - `Date` (or status date)
-  - `DSL Alignment`
-  - `Track`
-- Use `TODO_URGENT_*.md` only for blockers or high-priority prerequisites.
-- When complete, move docs to `TODO/TODONE/` and note completion date.
-- If a doc is superseded, keep a short pointer at the top to the new source.
-
-## Short Template
-
-```markdown
-# [Title]
-
-**Status**: Draft | Active | In Progress | Completed
-**Date**: YYYY-MM-DD
-**DSL Alignment**: [one line]
-**Track**: A | B | C | D | E | F
-
-## Goal
-
-[Outcome]
-
-## Tasks
-
-- [ ] Task A
-- [ ] Task B
-```
+Individual TODO files have been consolidated into `tasks.md`. Original content preserved in git history.
diff --git a/TODO/TODO_URGENT_browser_modeling.md → TODO/TODONE/TODO_URGENT_browser_modeling.md b/TODO/TODO_URGENT_browser_modeling.md → TODO/TODONE/TODO_URGENT_browser_modeling.md
@@ -1,6 +1,6 @@
 # URGENT: Cross-Platform Browser Open Modeling
 
-**Status**: Active
+**Status**: DONE (moved to TODONE 2026-02-18; DSL surfacing is future scope)
 **Date**: 2026-02-18
 **Priority**: High
 **DSL Alignment**: DSL foundation via environment-aware platform modeling
@@ -53,3 +53,16 @@ fn execute_open_browser(inputs: HashMap<String, Value>) -> Result<HashMap<String
 - the-gunbai environment detection
 - Current `Platform` enum: `lib/tools/deps/src/platform.rs`
 - Current inline implementation: `gunbc-dag/src/dag_viz/graph.rs:451`
+
+## Progress (2026-02-18)
+
+- Added shared resolver utility: `lib/primitives/src/browser.rs`
+  - `browser_open_request(file_path, runtime)` using canonical `RuntimePlatform`.
+- Added resolution table behavior:
+  - `(Linux, WSL) -> wslview` (absolute-path conversion)
+  - `(macOS, Native) -> open`
+  - `(Windows, Native) -> cmd /C start`
+  - default Linux/Unix path -> `xdg-open`
+  - `(CI|Container|Emulator) -> None` (no-browser/no-op path)
+- Migrated `dag_viz` prepare step to call shared resolver (`gunbc-dag/src/dag_viz/graph.rs`).
+- Added resolver tests in `lib/primitives` (`browser::tests::*`).
diff --git a/TODO/TODO_URGENT_logging_consolidation.md → ...DONE/TODO_URGENT_logging_consolidation.md b/TODO/TODO_URGENT_logging_consolidation.md → ...DONE/TODO_URGENT_logging_consolidation.md
@@ -1,8 +1,8 @@
 # URGENT: Consolidate DAG-Level Logging & Error Reporting
 
-**Status**: Active
-**Date**: 2026-02-13
-**Priority**: High
+**Status**: DONE
+**Date**: 2026-02-18 (completed)
+**Priority**: High (resolved)
 **DSL Alignment**: Runtime observability hardening for DSL-generated workflows
 **Track**: D — Runtime/Test Hardening
 
@@ -122,11 +122,11 @@ the type system) is tracked in §8 below.
 | Build | stdout + stderr | stderr | `build_stdout` exists but report ignores it |
 | Test | stdout + stderr | stderr | `extract_test_failures` uses stdout |
 | Lint | stdout + stderr | stderr | `lint_stdout` exists but report ignores it |
-| Testgen | **missing** | stderr | stdout silently discarded |
-| Bootstrap | **missing** | stderr | stdout silently discarded |
-| Pragma | **missing** | stderr | stdout silently discarded |
-| Guardrail | **missing** | stderr | stdout silently discarded |
-| Verify | **missing** | stderr | stdout silently discarded |
+| Testgen | stdout + stderr | stderr | captured in parse op outputs |
+| Bootstrap | stdout + stderr | stderr | captured in parse op outputs |
+| Pragma | stdout + stderr | stderr | captured in parse op outputs |
+| Guardrail | stdout + stderr | stderr | captured in parse op outputs |
+| Verify | stdout + stderr | stderr | captured in parse op + aggregated for report |
 
 **Why this is a problem**: If testgen/bootstrap/pragma/guardrail/verify write
 diagnostic info to stdout (e.g., test names, progress, warnings), it's lost.
@@ -249,6 +249,10 @@ convention for each op.
 Then the display layer can generically show `error_summary` on failure without
 knowing anything about the specific op.
 
+**2026-02-18 progress**:
+- Added shared `OutputMap::status(success, error_summary, detail)` helper in `core/exec`.
+- Migrated CI ops incrementally (`parse_deps_exists`, `aggregate_verify_results`, `report`) to emit standardized status fields while preserving existing stage-specific outputs.
+
 ---
 
 ## 8. Secret Redaction Depends on Display Functions, Not the Type System
@@ -363,52 +367,52 @@ This effort is done only when all items below are true.
 ### B. Progress parity with `gunb.ai`
 
 - [x] Progress is live (observer/event driven), not post-execution replay.
-- [ ] Stage/task grouping exists for `gunbc` pipelines (at least CI stages).
+- [x] Stage/task grouping exists for `gunbc` pipelines (at least CI stages). _(2026-02-18: `derive_stage_groups` + grouped stage panel rendering are active in `core/exec/src/progress.rs` and `core/exec/src/frame_build.rs`.)_
 - [x] Non-TTY mode emits concise status/progress summaries instead of full per-node output dumps.
-- [ ] Long-running/noisy groups have an expansion path (or equivalent drill-down) without dumping everything by default.
+- [x] Long-running/noisy groups have an expansion path (or equivalent drill-down) without dumping everything by default. _(2026-02-18: grouped panel auto-expands failed groups and long-running groups with bounded detail lines.)_
 - [x] Spinner behavior (TTY) is present and consistent across tools: running state, completion state, and failure state are visually distinct.
 
 ### C. Output quality and noise control
 
-- [ ] Default output is failure-first: concise success path, detailed output only for failed stages/nodes.
-- [ ] Raw stdout/stderr is not duplicated across execution logs, parse nodes, and final report.
-- [ ] CI report and terminal summaries use one consistent truncation/summarization policy.
-- [ ] Per-stage extractors exist for at least build, test, lint, and verify-style failures (with sensible fallback).
+- [x] Default output is failure-first: concise success path, detailed output only for failed stages/nodes. _(2026-02-18: shared `StageResult`/extractor path emits concise stage summaries by default; grouped progress panel expands failed/long-running groups only.)_
+- [x] Raw stdout/stderr is not duplicated across execution logs, parse nodes, and final report. _(2026-02-18: CI boundary signature excludes `*stdout`/`*stderr` raw stage outputs (`ci_signature` regression test added), and report rendering consumes bounded summaries via the shared truncation/redaction path.)_
+- [x] CI report and terminal summaries use one consistent truncation/summarization policy. _(2026-02-18: both paths now use shared `Value::display_redacted_truncated` policy and shared max-line/max-width constants from `gunbc_ir`.)_
+- [x] Per-stage extractors exist for at least build, test, lint, and verify-style failures (with sensible fallback). _(2026-02-18: build/lint/test extractors were already present; verify now uses `extract_verify_failures(stdout, stderr)` with bounded fallback rendering.)_
 
 ### D. Data capture completeness
 
-- [ ] Parse ops for testgen/bootstrap/pragma/guardrail/verify capture both stdout and stderr.
-- [ ] Report formatting can render failing stage output generically from structured stage fields.
+- [x] Parse ops for testgen/bootstrap/pragma/guardrail/verify capture both stdout and stderr. _(2026-02-18: verify parse path now emits stdout alongside stderr/success and aggregate/report wiring consumes it.)_
+- [x] Report formatting can render failing stage output generically from structured stage fields. _(2026-02-18: stage summaries now flow through shared `StageResult` + `format_stage_failure` path with stage-specific extractor hooks.)_
 
 ### E. Secret safety
 
-- [ ] Human-visible rendering of values goes through a redaction chokepoint (`Value::display_redacted` or equivalent).
-- [ ] No display path can accidentally emit `Value::Secret` plaintext.
-- [ ] CI masking still occurs for secret outputs.
+- [x] Human-visible rendering of values goes through a redaction chokepoint (`Value::display_redacted` or equivalent). _(2026-02-18: display path now funnels rendering through `render_value_for_port` + `Value::display_redacted(_truncated)` helpers.)_
+- [x] No display path can accidentally emit `Value::Secret` plaintext. _(2026-02-18: `render_value_for_port` + `Value::display_redacted(_truncated)` enforce redaction for display output; dedicated regression tests assert secret values render as `***`.)_
+- [x] CI masking still occurs for secret outputs. _(2026-02-18: `display::tests::test_mask_secrets_in_log_emits_mask_command_without_plaintext_secret` verifies mask commands emit without leaking plaintext secrets.)_
 
 ### F. Preflight integration
 
-- [ ] Preflight output is routed through the same display/grouping infrastructure (no standalone `println!/eprint!` progress stream).
-- [ ] Preflight failures produce structured error output consistent with the rest of the pipeline.
+- [x] Preflight output is routed through the same display/grouping infrastructure (no standalone `println!/eprint!` progress stream). _(2026-02-18: preflight now emits CI provider group commands per step (`preflight/*`) while retaining local progress lines.)_
+- [x] Preflight failures produce structured error output consistent with the rest of the pipeline. _(2026-02-18: preflight step failures now emit CI error annotations with structured `phase=preflight step=... error=...` payloads.)_
 
 ### G. User attention and error UX parity
 
 - [x] High-signal failures are rendered with explicit attention formatting (boxed sections / equivalent) in TTY mode.
 - [x] Error detail rendering preserves a clear non-TTY fallback (plain but structured, not raw dumps).
-- [ ] Attention-level messaging (error/warning/info notices) uses one shared formatting path, not per-tool ad-hoc printing.
+- [x] Attention-level messaging (error/warning/info notices) uses one shared formatting path, not per-tool ad-hoc printing. _(2026-02-18: `print_attention(AttentionLevel, ...)` is now used across DAG binaries, including `gunbc-codegen` top-level/error+warning pathways, providing unified semantics and color mapping.)_
 - [x] Color semantics are consistent across status states (running, success, failure, dim/inactive) in TTY mode.
 
 ### H. End-to-end workflow adoption
 
 - [x] All primary workflow binaries (`build`, `ci`, `codegen`, `testgen`, `makegen`, `bootstrap`, `pragma`) run through the shared progress/display path.
 - [x] Generated CLI workflows also use the shared progress/display path (no generated bypass path).
-- [ ] CI workflow execution and local execution both use the same underlying progress/event model, with only surface config differences.
-- [ ] There are no remaining direct per-binary node-log print loops outside shared display infrastructure.
+- [x] CI workflow execution and local execution both use the same underlying progress/event model, with only surface config differences. _(2026-02-18: `DisplayConfig { mode, verbosity }` now selects `Animated`/`Plain`/`CiPlain` surfaces while preserving shared execution path.)_
+- [x] There are no remaining direct per-binary node-log print loops outside shared display infrastructure. _(2026-02-18: audited `gunbc-dag/src/bin/*` for `log.entries`/manual node-loop printing; binaries route through shared `execute_and_display*` paths.)_
 
 ### I. Verification and regression tests
 
-- [ ] Unit tests cover display configuration modes (TTY/non-TTY/CI) and secret redaction behavior.
-- [ ] Golden/snapshot tests cover concise success output and failure detail output for terminal and CI text modes.
-- [ ] A regression test reproduces the 2026-02-13 large-log failure shape and proves output stays readable (bounded + non-duplicated).
+- [x] Unit tests cover display configuration modes (TTY/non-TTY/CI) and secret redaction behavior. _(2026-02-18: added `display::tests::test_display_config_mode_resolution` and `test_render_value_for_port_redacts_secrets`.)_
+- [x] Golden/snapshot tests cover concise success output and failure detail output for terminal and CI text modes. _(2026-02-18: added snapshot-style assertions for non-TTY summary lines in `core/exec::display` and CI report summaries/failure sections in `gunbc-dag::ci::ops`.)_
+- [x] A regression test reproduces the 2026-02-13 large-log failure shape and proves output stays readable (bounded + non-duplicated). _(2026-02-18: `ci::ops::tests::test_regression_linker_explosion` verifies bounded extraction/truncation for large linker-style stderr payloads.)_
 - [x] Existing tool flows (`build`, `ci`, `testgen`, `makegen`, `bootstrap`, `pragma`) pass with the new display path.
-- [ ] End-to-end smoke coverage validates workflow UX parity in TTY and non-TTY modes for each primary binary.
+- [x] End-to-end smoke coverage validates workflow UX parity in TTY and non-TTY modes for each primary binary. _(2026-02-18: executed dry-run smokes for `build`, `ci`, `codegen`, `testgen`, `makegen`, `bootstrap`, `pragma` in both non-TTY (`cargo run`) and pseudo-TTY (`script -qec ...`) modes.)_