roadmap: P1 — Agent tool wiring for orchestrator-agent (blocks or.1 design goal)
This commit is contained in:
@@ -41,6 +41,22 @@ context. Pick the next milestone from P1.)_
|
||||
|
||||
## P1 — Next
|
||||
|
||||
- [ ] **\[todo\]** `Agent` tool wiring for the dispatched
|
||||
orchestrator-agent — `skills/implement/agents/ailang-implement-orchestrator.md`
|
||||
declares `tools: Read, Edit, Write, Bash, Glob, Grep, Agent`, but
|
||||
the first real dispatch (pr.1) reported `Agent` was not in its
|
||||
actual tool set, forcing degraded-mode execution (per-task
|
||||
sub-loop did not run; all tasks executed inline in the
|
||||
orchestrator's own context). Diagnosis needed before fix-scope
|
||||
can be set: Claude Code restriction on nested-subagent dispatch?
|
||||
Frontmatter parsing detail? Deferred-tool issue at the harness
|
||||
layer? This blocks the or.1 design goal (Boss-context offload via
|
||||
fresh-subagent-per-task isolation); Boss-context offload itself
|
||||
still works because per-task detail collapses into one
|
||||
end-report regardless.
|
||||
- context: `docs/journals/2026-05-11-iter-pr.1.md` Boss-side
|
||||
addendum + Audit close section.
|
||||
|
||||
- [ ] **\[milestone\]** Post-22 Prelude — ship `Show` / `Eq` / `Ord`
|
||||
with the three total-orderable primitive instances (Int, Bool, Str);
|
||||
rewire `print` through `Show.show`. Float gets `Show` but **not**
|
||||
|
||||
Reference in New Issue
Block a user