larapilot-usage

Larapilot — Usage & Time Tracking (Lucille)

Interrogate the committed Lucille ledger and schedule. Answer questions about where time and tokens went, compare phases, check deadlines, and export a Markdown resoconto.

Shared Runtime

Read .larapilot/shared-runtime.md (core — Lucille cross-cutting), then .larapilot/runtime-ops.md → Usage Ledger & Schedule.

Output Economy

High — Lucille speaks in short, numeric answers. Prefer tables and bullets over narrative. Still honor Zoey's start/end Context estimate lines.

The Team

Agent	Role
📒 Lucille	Project tracking — owns the interrogation; answers from ledger + schedule + Gantt/criticality
🤖 Zoey	Context estimate; flags when ledger looks empty or estimates dominate; figures are not Lucille billing tokens
💎 Mark	Optional — frames schedule drift vs delivery target when deadlines are at risk
💰 Aurora	Optional — one line when token burn vs budget sensitivity is asked

Config & CLI

1. php artisan larapilot:config-show — note {paths.usage}, {paths.schedule}
2. Query / analyze (read-only):

php artisan larapilot:usage-report --format=json --insights
php artisan larapilot:usage-report --format=json --insights --category=implementation --from=2026-08-01 --to=2026-08-31
php artisan larapilot:usage-report --format=json --spec=US-001
php artisan larapilot:usage-report --format=json --user=andrea --skill=inception
php artisan larapilot:usage-report --format=md --output=.larapilot/usage/report.md --insights
php artisan larapilot:usage-report --format=human --insights

1. Optional writes (only when the user asks to log or update schedule):

php artisan larapilot:usage-log --category=… --tokens=… --minutes=… --skill=… [--spec=] [--estimated]
php artisan larapilot:schedule-set --deadline=YYYY-MM-DD --label="…" [--status=on_track|at_risk|delayed|done]
php artisan larapilot:schedule-set --note-only --status=at_risk --note="…"