Capture immutable command declarations

This commit is contained in:
2026-10-11 01:15:13 +00:00
parent 476e98a463
commit de9bfdcc4c
16 changed files with 368 additions and 474 deletions

View File

@@ -1,6 +1,6 @@
# Implement the optional integration modules and captured registration API
Status: implementation in progress. Stage 1 is complete; subsequent work follows the ordered roadmap.
Status: implementation in progress. Stages 1 and 2 are complete; subsequent work follows the ordered roadmap.
Execute the stages in order. Each stage is sized as a separate Luna coding-agent
assignment. This document authorizes no publication or changes to sibling
repositories.
@@ -189,9 +189,13 @@ neutral diagnostic/outcome model.
values, or general app pointer. App-specific built-ins are constructed for
their app later; ordinary declarations remain reusable.
**Completion evidence:** focused capture/error checks cover source-slice edits,
copied handles, prior/wrapped causes, root-only metadata, nested no-ops, invalid
zero values, and runnable children. Do not promise arbitrary object deep copies.
**Completion evidence — complete:** declarations now use immutable captured
records; caller slices are copied at capture and child records are shared. Focused
checks cover source-slice edits, copied handles, retained/wrapped causes, root-only
metadata, nested no-ops, invalid zero values, and runnable parents with children.
Diagnostics and `Acquired[T]` are core-owned, and ConfigKit/PromptKit requirements
were removed from the root module. Root tests pass. This does not promise arbitrary
object deep copies.
## Stage 3: Unify typed flag and argument conversion