ledger-tasks-yylo

1## YYLO Ledger CLI Reference
2 
3Use `yy ledger` for all commands. Before any operation, run `yy ledger --version` and `yy ledger --help`; the installed runtime's help is authoritative. Read the current task/board state before mutation, preserve the returned mutation receipt when offered, and never edit Markdown/store files directly to bypass controller routing or lifecycle state. If the required command group is absent, stop and request a Ledger upgrade rather than guessing or invoking mutable source code. Ledger 0.3.x exposes both the compatible flat task commands and the native ID-first `record|task|wiki|workflow|artifact` groups. `yy kanban` is a labelled compatibility alias for the same controller-routed task runtime.
4 
5### Supported task contract
6 
7- Preflight installed `yy ledger --version` and `yy ledger --help`; command help is authoritative for the selected runtime.
8- Use the flat task surface for lifecycle task management. Use the dedicated native skills for wiki, workflow, and artifact Records rather than guessing their arguments.
9- New operational PDRs, contracts, plans, reports, receipts, and evidence belong in typed Artifact Records, not product documentation, task bodies/responses, or new `.juno_task/specs` files.
10- If a required native group is absent, fail closed and request a Ledger upgrade. Never invoke mutable source directly or write Ledger store files by hand.
11…