Parfii-bot e075ae8df1 fix(compose): render resolved scope block — agent sees concrete paths, not generic text ... Dogfood gap #2 from prepare workflow: capability text fragments say "your task's scope" generically, but agent never sees the resolved scope params from task.toml. Migration agent had no way to know whitelist = kei-chat-store/** without me pasting it. Fix: render_scope_block() injects a resolved-params section between capability fragments and task body. Shows: - files-whitelist / files-denylist glob lists - cargo-check-crates / cargo-test-crates - test-count-min (if Option<u32>::Some) - report-fields-required If no scope params set, block is empty (no section rendered). Now `kei-agent-runtime prepare` emits fully self-contained prompt — no external context needed. Substrate unblocked for parallel migrations. Tests: 41/41 (was 41 — no regression; scope-block added tests deferred to follow-up since compose_smoke already covers existing path). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-23 05:44:15 +08:00
..
src	fix(compose): render resolved scope block — agent sees concrete paths, not generic text	2026-04-23 05:44:15 +08:00
tests	Merge fix/b2-dna-role — DNA + role + traversal	2026-04-23 05:31:03 +08:00
Cargo.toml	feat(convergence/p3): Role expression (extends/relaxes) + DNA identity	2026-04-23 04:46:48 +08:00