develop-kilin-runtimelisted

# Develop Kilin runtime behavior Change Kilin runtime behavior without weakening its deterministic local execution model or mixing domain, infrastructure, and presentation concerns. ## Establish the change boundary 1. Confirm the physical repository root, current branch, and working-tree state. Preserve unrelated changes. 2. Read `AGENTS.md` and `packages/cli/docs/agents/system-design.md` completely. 3. Read only the V1 contracts affected by the requested behavior: - `packages/cli/docs/v1/architecture.md` for lifecycle, scheduling, locking, and persistence; - `packages/cli/docs/v1/workflow.md` and `bounded-feedback.md` for graph semantics; - `packages/cli/docs/v1/runtime.md` for process execution; - `packages/cli/docs/v1/cli.md` for command behavior; - `packages/cli/docs/v1/testing.md` for observable contracts. 4. Reproduce a non-trivial defect before fixing it. Treat the first root-cause theory as tentative. 5. Classify the change risk. Present a scoped plan before medium- or high-risk mutation unless the user has already approved implementation. If the primary change affects the workflow schema, SQLite shape, lifecycle vocabulary, public JSON or JSON Lines, exit codes, or a Viewer DTO, use `evolve-kilin-contract` instead. ## Map ownership before editing Assign each behavior to its narrowest owner: - `src/domain/`: pure workflow rules, state transitions, compilation, and value types; - `src/application/`: use cases, scheduling, lifecycle coordinat