Latest stable
Kanban wrapper
Keep structured task truth available through the project-local YYLO Ledger wrapper.
When to use it
Agents and operators need statuses, blockers, responses, and commit evidence from one NDJSON source.
When not to use it
Do not use task prose as a substitute for dependency declarations or validation evidence.
Prerequisites
An initialized .juno_task directory and the Python environment installed by YYLO.
Representative command
Safety contract
Use --body-file/--response-file for shell-sensitive Markdown. Only run ready tasks and attach the validating commit when done.
Artifacts to inspect
.juno_task task NDJSON, responses, dependency metadata, and commit references.
Troubleshooting
Use get --compact for focused context and deps TASK_ID to explain why work is blocked.
Freshness source
Reviewed against YYLO README: yylo-ledger-commands and the generated installed-script inventory.