feat: complete critical spec refinements and backlog hygiene

Author: rand

.beads/issues.jsonl

@@ -4,6 +4,8 @@ This package turns the evaluation findings into an execution-ready program for `
 
 Safe mode is the default operating profile on this machine due prior memory exhaustion.
 
+Last reconciled: 2026-02-20 (live state source: `docs/execution-plan/STATUS.md` + Beads).
+
 ## Execution Principles
 
 - Contract-first: lock cross-repo behavior before changing implementation.
@@ -13,14 +15,16 @@ Safe mode is the default operating profile on this machine due prior memory exha
 - Small-batch: execute one task card at a time, not one milestone at a time.
 - Reproducibility: every gate has a deterministic command and pass criteria.
 
-## Current Reality (2026-02-19 Post-M6 + M7 Planning)
+## Current Reality (Historical Snapshot: 2026-02-19 Post-M6 + M7 Planning)
+
+Use `docs/execution-plan/STATUS.md` for live status before acting on any item below.
 
 - M0-M6 remediation/governance milestones are complete with evidence.
 - SPEC-20..27 still contain implementation gaps or partial integrations requiring runtime closure.
 - Open gap IDs from traceability artifact: `G-001` (`LLM_BATCH` end-to-end runtime integration) and `G-002` (orchestrator fallback wiring).
 - `loop-agent` and `io-rflx` remain active integration targets; compatibility claims must follow D-017 clean-clone committed-tuple policy.
 - Safe mode remains mandatory due prior OOM history; heavy command concurrency stays at 1.
-- M7 is the active completion tranche, with task-level gate definitions in `VALIDATION-MATRIX.md`.
+- M7 is complete; post-M7 critical refinements are tracked in `loop-azq` and child tasks.
 
 ## File Map
 

docs/execution-plan/README.md

@@ -2,16 +2,19 @@
 
 > Current state assessment and path to completion
 
+> Reconciled on 2026-02-20 against Beads and `docs/execution-plan/STATUS.md`.
+> This file is historical wave-planning context, not the live execution tracker.
+
 ## Executive Summary
 
-**Implementation is substantially complete.** Both major epics have all their component tasks closed:
+**Wave 3-5 scope is complete.** Both major epics and migration tasks referenced by this plan are closed:
 
 - **rlm-core Epic (loop-uci)**: 12/12 implementation phases closed
 - **Lean FV Epic (loop-vce)**: 4/4 implementation phases closed
 
-**Remaining Work**:
-- 2 migration tasks (open)
-- Testing, validation, and publishing
+**Current Follow-on Work**:
+- Post-M7 critical refinements are tracked in `loop-azq` and child tasks.
+- Live state is maintained in `docs/execution-plan/STATUS.md`, `docs/execution-plan/TASK-REGISTRY.md`, and `bd status`.
 
 ---
 
@@ -42,11 +45,12 @@
 
 ### 1.2 Beads Issue Status
 
-| Status | Count | Issues |
-|--------|-------|--------|
-| **Closed** | 20 | All implementation phases |
-| **In Progress** | 2 | `loop-uci` (epic), `loop-vce` (epic) |
-| **Open** | 2 | `loop-cyl` (migration), `loop-m0c` (migration) |
+| Issue | Scope | Status |
+|-------|-------|--------|
+| `loop-uci` | Unified RLM epic | Closed |
+| `loop-vce` | Lean FV epic | Closed |
+| `loop-cyl` | `rlm-claude-code` migration | Closed |
+| `loop-m0c` | `recurse` migration | Closed |
 
 ### 1.3 Code Statistics
 
@@ -56,14 +60,14 @@
 
 ---
 
-## 2. Remaining Work
+## 2. Remaining Work (Historical Wave Scope)
 
 ### 2.1 Migration Tasks (Wave 5)
 
 | Issue | Title | Status | Description |
 |-------|-------|--------|-------------|
-| `loop-cyl` | Migration: rlm-claude-code to rlm-core | Open | Replace Python implementation with rlm-core bindings |
-| `loop-m0c` | Migration: recurse to rlm-core | Open | Replace Go implementation with rlm-core CGO bindings |
+| `loop-cyl` | Migration: rlm-claude-code to rlm-core | Closed | Replaced legacy Python implementation with rlm-core delegation/runtime |
+| `loop-m0c` | Migration: recurse to rlm-core | Closed | Replaced legacy Go implementation with rlm-core CGO bridges |
 
 **Migration Strategy (from specs):**
 
@@ -83,19 +87,17 @@
 
 ### 2.2 Epic Closure
 
-Once migrations are complete, the epics can be closed:
-
 | Epic | Issue | Acceptance Criteria Status |
 |------|-------|---------------------------|
-| Unified RLM Library | `loop-uci` | All criteria met except migrations |
-| Lean Formal Verification | `loop-vce` | All implementation phases complete |
+| Unified RLM Library | `loop-uci` | Closed |
+| Lean Formal Verification | `loop-vce` | Closed |
 
 **loop-uci Acceptance Criteria:**
 - [x] rlm-core Rust crate compiles
 - [x] Python bindings (PyO3) available
 - [x] Go bindings working with CGO
-- [ ] **recurse migrated to use rlm-core** ← `loop-m0c`
-- [ ] **rlm-claude-code migrated to use rlm-core** ← `loop-cyl`
+- [x] recurse migrated to use rlm-core (`loop-m0c`)
+- [x] rlm-claude-code migrated to use rlm-core (`loop-cyl`)
 - [x] >80% test coverage on core crate
 - [x] All public APIs documented
 
@@ -107,7 +109,7 @@ Once migrations are complete, the epics can be closed:
 - [x] Progressive proof automation implemented
 - [x] DP integration tracks formal spec coverage
 
-### 2.3 Publishing Tasks (Post-Migration)
+### 2.3 Publishing Tasks (Still Program-Level Backlog)
 
 | Task | Description | Status |
 |------|-------------|--------|
@@ -118,50 +120,22 @@ Once migrations are complete, the epics can be closed:
 
 ---
 
-## 3. Execution Plan
-
-### Phase 1: Migrations (Current Focus)
+## 3. Historical Execution Plan
 
-Both migrations can proceed in parallel:
+This wave execution plan has already been completed.  
+For current execution sequencing, use:
 
-```bash
-# Track A: rlm-claude-code migration
-bd update loop-cyl --status in_progress --assignee claude
-
-# Track B: recurse migration
-bd update loop-m0c --status in_progress --assignee claude
-```
-
-**Duration**: 1-2 weeks per migration
-
-### Phase 2: Validation
-
-After migrations:
-- Run full test suite (incrementally, not all at once)
-- Verify no regressions in existing functionality
-- Performance benchmarks
-
-### Phase 3: Epic Closure
-
-```bash
-# Close epics
-bd close loop-uci --reason "All acceptance criteria met"
-bd close loop-vce --reason "All implementation phases complete"
-```
-
-### Phase 4: Publishing
-
-- Tag release
-- Publish packages
-- Update documentation
+- `docs/execution-plan/STATUS.md`
+- `docs/execution-plan/TASK-REGISTRY.md`
+- `bd ready` / `bd status`
 
 ---
 
 ## 4. Dependency Summary
 
 ```
-                          COMPLETE                                    REMAINING
-                          ════════                                    ═════════
+                          COMPLETE                                 CURRENT TRACK
+                          ════════                                 ═════════════
 
     ┌─────────────────────────────────────────────────────────┐
     │              All Implementation Phases                   │
@@ -174,16 +148,24 @@ bd close loop-vce --reason "All implementation phases complete"
               ┌──────────────────────────────────────┐
               │         Migration Tasks              │
               │                                      │
-              │  loop-cyl: rlm-claude-code  ❌ OPEN │
-              │  loop-m0c: recurse          ❌ OPEN │
+              │  loop-cyl: rlm-claude-code  ✅ CLOSED |
+              │  loop-m0c: recurse          ✅ CLOSED |
               └─────────────────┬────────────────────┘
                                 │
                                 ▼
               ┌──────────────────────────────────────┐
               │         Epic Closure                 │
               │                                      │
-              │  loop-uci: Unified RLM    ◐ IN_PROG │
-              │  loop-vce: Lean FV        ◐ IN_PROG │
+              │  loop-uci: Unified RLM     ✅ CLOSED |
+              │  loop-vce: Lean FV         ✅ CLOSED |
+              └─────────────────┬────────────────────┘
+                                │
+                                ▼
+              ┌──────────────────────────────────────┐
+              │      Active Follow-on Backlog        │
+              │                                      │
+              │  loop-azq child tasks (SPEC gaps)   │
+              │  tracked in execution-plan docs      │
               └──────────────────────────────────────┘
 ```
 
@@ -200,27 +182,22 @@ bd close loop-vce --reason "All implementation phases complete"
 - [ADR-002: Lean Formal Verification](./adr/ADR-002-lean-formal-verification.md)
 
 ### Implementation Roadmap
-- [Implementation Roadmap](./implementation-roadmap.md) (historical, superseded by this doc)
+- [Implementation Roadmap](./implementation-roadmap.md) (historical)
+- `docs/execution-plan/STATUS.md` (authoritative live tracker)
 
 ---
 
 ## 6. Commands Reference
 
 ```bash
-# View current status
+# View live status
 bd ready                    # Show ready-to-work issues
 bd list --status open       # Show open issues
 bd stats                    # Project statistics
 
-# Work on migrations
-bd update loop-cyl --status in_progress
-bd update loop-m0c --status in_progress
-
-# Close when complete
-bd close loop-cyl --reason "Migration complete"
-bd close loop-m0c --reason "Migration complete"
-bd close loop-uci --reason "All acceptance criteria met"
-bd close loop-vce --reason "All phases complete"
+# Inspect current post-M7 backlog
+bd show loop-azq
+bd children loop-azq
 
 # Sync at session end
 bd sync --from-main

docs/implementation-plan-wave3-5.md

@@ -2,6 +2,9 @@
 
 > Intelligent sequencing for maximum efficacy and performance
 
+> Historical planning artifact. Last reconciled against Beads/`STATUS.md` on 2026-02-20.
+> Live issue state is tracked in `bd` and `docs/execution-plan/STATUS.md`; tables below are archival sequencing context.
+
 ## Executive Summary
 
 This roadmap sequences work across two major initiatives:
@@ -10,9 +13,18 @@ This roadmap sequences work across two major initiatives:
 
 The plan maximizes parallelization while respecting dependencies, targeting efficient resource utilization.
 
+## Current Authoritative State (2026-02-20)
+
+- Runtime/spec closure is tracked under `loop-azq` children in Beads.
+- M7 milestone cards are complete and archived under `docs/execution-plan/evidence/2026-02-20/milestone-M7/`.
+- For current execution order and status, use:
+  - `docs/execution-plan/STATUS.md`
+  - `docs/execution-plan/TASK-REGISTRY.md`
+  - `bd status` / `bd ready`
+
 ---
 
-## 1. Current State Analysis
+## 1. Historical State Analysis (Archived)
 
 ### 1.1 rlm-core Status
 
@@ -296,35 +308,15 @@ For maximum throughput, use **3 parallel agent sessions**:
 
 ---
 
-## 6. Recommended Immediate Actions
-
-### Today
-
-1. **Unblock Lean FV work**: Remove epic blocker from src-726 and src-4sz
-2. **Verify rlm-core**: Run `cargo build` and `cargo test` to ensure code compiles
-3. **Start Wave 1**: Begin work on src-8ox (Go bindings) and src-726 (Lean REPL)
+## 6. Recommended Immediate Actions (Historical)
 
-### This Week
+The action list below was valid for the original roadmap horizon and is retained only for archival context.
 
-4. **Set up Lean environment**: Install Lean 4, elan, mathlib
-5. **Clone and test Topos**: Verify topos MCP server works
-6. **Complete observability track**: src-tzy, src-dt2, src-y7b (lower priority but parallelizable)
+For current work intake and execution:
 
-### Command to Start
-
-```bash
-# Approve epic and remove blockers
-bd update src-vce --status in_progress
-
-# Start Lean REPL task
-bd update src-726 --status in_progress --assignee claude
-
-# Start Go Bindings task
-bd update src-8ox --status in_progress --assignee claude
-
-# Start Topos Integration task
-bd update src-4sz --status in_progress --assignee claude
-```
+1. Start with `bd ready` and `bd show loop-azq`.
+2. Follow `docs/execution-plan/STATUS.md` and `docs/execution-plan/TASK-REGISTRY.md`.
+3. Treat this roadmap's legacy issue IDs (`src-*`) as historical references, not active queue items.
 
 ---
 

docs/implementation-roadmap.md

@@ -2,7 +2,7 @@
 
 > DSPy-inspired typed signatures for rlm-core
 
-**Status**: Partially implemented (typed runtime protocol and validation parity implemented through M7-T03; remaining composition/runtime-governance refinements are up-next critical scope tracked in `loop-azq`)
+**Status**: Implemented in `rlm-core` runtime (typed runtime protocol + deterministic composition validation + derive type-inference refinements)
 **Created**: 2026-01-20
 **Epic**: loop-zcx (DSPy-Inspired RLM Improvements)
 **Tasks**: loop-d75, loop-jqo, loop-9l6, loop-bzz
@@ -21,11 +21,11 @@ Implement DSPy-style typed signatures that enable composable modules, automatic
 | SPEC-20.02 Field specification model | Implemented | `rlm-core/src/signature/types.rs` |
 | SPEC-20.03 Runtime validation | Implemented (input pre-validation + output validation path) | `validate_fields` in `rlm-core/src/signature/validation.rs`, `Predict::forward` in `rlm-core/src/module/predict.rs` |
 | SPEC-20.04 Derive macro attributes | Implemented (including explicit enum values) | `rlm-core-derive/src/lib.rs` |
-| SPEC-20.05 Type inference | Partially implemented | Primitive/List/Option inference in `rlm-core-derive/src/lib.rs`; explicit enum via `#[field(enum_values = \"...\")]` |
+| SPEC-20.05 Type inference | Implemented | Primitive/List/Option plus reference/slice/array inference in `rlm-core-derive/src/lib.rs`; explicit enum via `#[field(enum_values = \"...\")]` |
 | SPEC-20.07..20.10 SUBMIT + REPL protocol | Implemented | `rlm-core/python/rlm_repl/sandbox.py`, `rlm-core/python/rlm_repl/main.py`, `rlm-core/src/repl.rs` |
 | SPEC-20.11 Module trait | Implemented | `rlm-core/src/module/mod.rs` |
 | SPEC-20.12 Predict wrapper | Implemented (with deterministic pre-exec input validation) | `rlm-core/src/module/predict.rs` |
-| SPEC-20.13 Composition validation | Partially implemented | `rlm-core/src/module/compose.rs` |
+| SPEC-20.13 Composition validation | Implemented | Deterministic direct-field compatibility checks (`validate_direct_field_mapping`) + validation-backed decode path in `rlm-core/src/module/compose.rs` |
 
 ## Requirements
 
@@ -177,14 +177,16 @@ Automatic FieldType inference from Rust types.
 | `bool` | `FieldType::Boolean` |
 | `Vec<T>` | `FieldType::List(T)` |
 | `Option<T>` | Same as T, but `required = false` |
+| `&T` | Same as `T` |
+| `[T]`, `[T; N]` | `FieldType::List(T)` |
 | `String` + `#[field(enum_values = "...")]` | `FieldType::Enum(values)` |
 | Rust enum type without `enum_values` annotation | `FieldType::Custom(type_name)` (current behavior) |
 | Other | `FieldType::Custom(type_name)` |
 
 **Acceptance Criteria**:
-- [ ] All primitive types inferred correctly
-- [ ] Generic types (Vec, Option) handled
-- [ ] Custom types fall back to Custom variant
+- [x] All primitive types inferred correctly
+- [x] Generic types (Vec, Option, references/slices/arrays) handled
+- [x] Custom types fall back to Custom variant
 
 ### SPEC-20.06: Compile-Time Validation
 
@@ -454,9 +456,9 @@ where
 - Propagate LM to all sub-modules
 
 **Acceptance Criteria**:
-- [ ] Type-safe composition at compile time
-- [ ] Runtime validation for dynamic cases
-- [ ] LM propagation through composition
+- [x] Type-safe composition at compile time
+- [x] Runtime validation for dynamic cases
+- [x] LM propagation through composition
 
 ---
 
@@ -482,12 +484,12 @@ where
 
 | Test | Description | Spec |
 |------|-------------|------|
-| `signature::tests::derive_tests::*` | Derive macro and signature behavior | SPEC-20.04, SPEC-20.05 |
+| `signature::tests::derive_tests::*` | Derive macro and signature behavior (including optional-list/array type-inference coverage) | SPEC-20.04, SPEC-20.05 |
 | `signature::validation::tests::*` | Validation behavior and error paths | SPEC-20.03, SPEC-20.09 |
 | `signature::submit::tests::*` | SubmitResult/SubmitError serialization and semantics | SPEC-20.08, SPEC-20.09 |
 | `tests/test_repl.py::TestReplServer::test_submit_*` | Python SUBMIT scenarios (success + validation failures) | SPEC-20.07, SPEC-20.09, SPEC-20.10 |
 | `repl::tests::test_submit_result_roundtrip_*` (ignored) | Rust/Python end-to-end submit_result roundtrip scenarios | SPEC-20.08, SPEC-20.10 |
-| `module::compose::tests::*` | Module composition/name generation scaffolding | SPEC-20.13 |
+| `module::compose::tests::*` | Module composition runtime mapping validation + deterministic error behavior | SPEC-20.13 |
 | `module::predict::tests::*` | Predict wrapper behavior and prompt/input formatting | SPEC-20.12 |
 
 ---