What
Implement Finish Today (Wrap-up Guidance) V1 consumption in headsdown-pi so Pi can automatically steer toward the smallest safe shippable outcome when wrap-up is active, while preserving an explicit per-task full-depth override.
Why
headsdown-pi is a primary behavior surface for HeadsDown-guided agent execution. Once the shared API/SDK contract lands, Pi should consume the same structured guidance so behavior is consistent with VS Code and Claude surfaces.
Acceptance Criteria
headsdown_status output includes wrapUpGuidance when present, and keeps current output shape backward compatible.
before_agent_start context injection includes a concise, explicit Finish Today summary when active (state, remaining time/deadline, and intent).
headsdown_propose supports a per-task delivery override (auto, wrap_up, full_depth) and passes it through to SDK proposal input when provided.
- HeadsDown skill guidance is updated so Pi behavior changes when wrap-up is active: completion-first execution, defer non-critical decisions, concise handoff.
- Opt-out behavior is explicit and local to the task/session by default (no silent global disable).
- Tests cover active/inactive guidance parsing, context formatting, and override pass-through behavior.
- Existing non-wrap-up behavior remains unchanged for users on older APIs or with inactive guidance.
Developer Notes
Dependency: https://github.com/headsdownapp/heads_down/issues/812
Approach: Keep server guidance semantic and client behavior deterministic. Do not implement provider-specific model switching in this ticket.
Likely files:
extensions/headsdown/index.ts
extensions/headsdown/policy.ts (formatting only if needed)
skills/headsdown/SKILL.md
test/extension.test.ts
test/availability-compat.test.ts
Testing:
- Unit tests for wrap-up fields in status/context payloads.
- Unit tests for
deliveryMode (or equivalent) proposal input wiring.
- Compatibility tests for missing guidance fields.
What
Implement Finish Today (Wrap-up Guidance) V1 consumption in
headsdown-piso Pi can automatically steer toward the smallest safe shippable outcome when wrap-up is active, while preserving an explicit per-task full-depth override.Why
headsdown-piis a primary behavior surface for HeadsDown-guided agent execution. Once the shared API/SDK contract lands, Pi should consume the same structured guidance so behavior is consistent with VS Code and Claude surfaces.Acceptance Criteria
headsdown_statusoutput includeswrapUpGuidancewhen present, and keeps current output shape backward compatible.before_agent_startcontext injection includes a concise, explicit Finish Today summary when active (state, remaining time/deadline, and intent).headsdown_proposesupports a per-task delivery override (auto,wrap_up,full_depth) and passes it through to SDK proposal input when provided.Developer Notes
Dependency: https://github.com/headsdownapp/heads_down/issues/812
Approach: Keep server guidance semantic and client behavior deterministic. Do not implement provider-specific model switching in this ticket.
Likely files:
extensions/headsdown/index.tsextensions/headsdown/policy.ts(formatting only if needed)skills/headsdown/SKILL.mdtest/extension.test.tstest/availability-compat.test.tsTesting:
deliveryMode(or equivalent) proposal input wiring.