agentplane 0.6.11 → 0.6.13

package/README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="https://raw.githubusercontent.com/basilisk-labs/agentplane/main/docs/assets/readme-headers/agentplane-cli.svg" alt="AgentPlane CLI package header" style="width:100%;max-width:100%;"/>
+  <img src="https://raw.githubusercontent.com/basilisk-labs/agentplane/main/docs/assets/readme-headers/agentplane-cli.svg" alt="Agentplane CLI package header" style="width:100%;max-width:100%;"/>
 </p>
 
 # AgentPlane CLI

package/assets/AGENTS.md

@@ -20,7 +20,7 @@ Detailed procedures live in canonical modules from `## CANONICAL DOCS`.
 
 - Repository type: user project initialized with `agentplane`.
 - CLI rule: prefer `ap` for compact agent-oriented commands; fall back to `agentplane`; if neither is available, stop and request installation guidance (do not invent repo-local entrypoints).
-- Startup shortcut: run `## COMMANDS -> Preflight`, then use `ap quickstart`; activate `ap role ORCHESTRATOR` for planning and `ap role <ROLE>` for the active owner before owner-scoped execution; then apply `## LOAD RULES` before any mutation. The guarded route is determined by `workflow.mode` in `.agentplane/WORKFLOW.md`; use `ap task brief <task-id>` and the emitted next command before manually assembling route commands. In `branch_pr`, start from the emitted `work start` route command or `ap work start ... --worktree`; in `direct`, stay in the current checkout and use the task lifecycle route.
+- Startup shortcut: run `## COMMANDS -> Preflight`; use `ap quickstart`; activate `ap role ORCHESTRATOR` for planning and `ap role <ROLE>` for execution; then apply `## LOAD RULES` before mutation. The guarded route is determined by `workflow.mode` in `.agentplane/WORKFLOW.md`; treat `ap task brief <task-id>` and `ap task next-action <task-id> --explain` as the route oracle: follow the emitted checkout, blocker, and next command instead of reconstructing workflow state.
 
 <!-- /ap:fragment -->
 <!-- ap:fragment id="gateway.agents.source_of_truth.sources.of.truth" slot="source_of_truth" mutability="replaceable" -->
@@ -62,10 +62,18 @@ ap quickstart
 ap task list
 ap task active
 git status --short --untracked-files=no
-git status --short
+git status --short --untracked-files=all
 git rev-parse --abbrev-ref HEAD
 ```
 
+### Route commands
+
+```bash
+ap task brief <task-id>
+ap task next-action <task-id> --explain
+ap work resume <task-id>
+```
+
 ### Task lifecycle
 
 ```bash
@@ -117,8 +125,10 @@ node .agentplane/policy/check-routing.mjs
 
 ## SHARED PROMPT CONTRACT
 
-- Outcome-first, concise, evidence-first: state goal, success criteria, constraints, stop rules, and output; use procedure only for command contracts, state machines, or irreversible gates; ask one narrow question only when missing information changes scope, task graph, security, or irreversible action.
-- Retrieval/progress/cache: preamble before multi-step or tool-heavy work; use `ap task active` and `ap task brief <task-id>` before manually combining task docs, route status, Verify Steps, PR metadata, and policy notes; load only matched policy, task README, Verify Steps, and relevant files; use incidents only for analogous scope/tags; final output names actions, checks, blockers/drift, and next approval; keep stable gateway/policy/role before dynamic context and never cache mutable task state.
+- Outcome-first, concise, evidence-first: state goal, success criteria, constraints, stop rules, and output; use procedure only for command contracts, state machines, or irreversible gates.
+- Ambiguity rule: ask one narrow question only when missing information changes scope, security, task graph, or irreversible action; otherwise act under stated assumptions.
+- Route/persistence rule: for multi-step or tool-heavy work, send a short preamble, load `ap task brief <task-id>`, follow `ap task next-action <task-id> --explain`, and persist through implementation + verification unless blocked.
+- Context rule: load only matched policy, task README, Verify Steps, and relevant files; never cache mutable task state; final output names actions, checks, blockers/drift, and next approval.
 
 <!-- /ap:fragment -->
 <!-- ap:fragment id="gateway.user.instructions" slot="body" mutability="append_only" -->
@@ -182,18 +192,7 @@ Role boundaries: ORCHESTRATOR = preflight + plan + approvals; PLANNER = executab
 
 ## CORE DOD
 
-A task is done only when all are true:
-
-1. Approved scope is satisfied; no unresolved drift.
-2. Required checks from loaded policy modules passed.
-3. Security and approval gates were respected.
-4. Traceability exists (task ID + updated task docs).
-5. Verification evidence is recorded.
-6. No unintended tracked changes remain.
-
-Detailed DoD rules are in `.agentplane/policy/dod.core.md`, `.agentplane/policy/dod.code.md`, and `.agentplane/policy/dod.docs.md`.
-
----
+A task is done only when approved scope, loaded DoD modules, security gates, task traceability, recorded verification, and clean final tracked state all pass. Detailed DoD rules live in `.agentplane/policy/dod.core.md`, `.agentplane/policy/dod.code.md`, and `.agentplane/policy/dod.docs.md`.
 
 <!-- /ap:fragment -->
 <!-- ap:fragment id="gateway.agents.hard_constraint.size.budget" slot="hard_constraint" mutability="append_only" -->
@@ -205,8 +204,6 @@ Detailed DoD rules are in `.agentplane/policy/dod.core.md`, `.agentplane/policy/
 - Worst-case loaded policy graph (always imports + all conditional imports) MUST stay <= 600 lines.
 - Enforced by `node .agentplane/policy/check-routing.mjs`.
 
----
-
 <!-- /ap:fragment -->
 <!-- ap:fragment id="gateway.agents.body.canonical.docs" slot="body" mutability="replaceable" -->
 

package/assets/policy/dod.core.md

@@ -10,7 +10,7 @@ The task is complete only if all core checks are true:
 4. Required task documentation sections are populated.
 5. Verification steps are executed and results recorded.
 6. Drift was either absent or explicitly re-approved.
-7. Final repo state contains no unintended tracked changes.
+7. Final repo state contains no unintended tracked changes or unreviewed untracked artifacts; final evidence includes `git status --short --untracked-files=all`.
 
 <!-- /ap:fragment -->
 <!-- ap:fragment id="policy.dod.core.body.required.task.readme.contract" slot="body" mutability="replaceable" -->

package/assets/policy/workflow.branch_pr.md

@@ -69,12 +69,12 @@ Before manually filling `<slug>` or `<branch>`, use `agentplane task brief <task
 - Task documentation updates MAY be batched within one turn before approval.
 - MUST run `task plan approve` then `task start-ready` as `Step 1 -> wait -> Step 2` (never parallel).
 - In `branch_pr`, `task start-ready`, `pr open`, `pr update`, and verification commands SHOULD be run from the task worktree created by `work start`.
-- A related task batch MAY reuse one primary task worktree when all included tasks are approved,
-  listed, verified independently, and merged through the primary task PR.
+- A related task batch MAY reuse one primary task worktree when all included tasks are approved, listed, verified independently, and merged through the primary task PR.
 - `pr open` without `--sync-only` SHOULD complete in one pass: sync local artifacts, auto-publish the task branch to `origin` when it has no upstream yet, then create/link the remote GitHub PR.
 - In `branch_pr`, the task GitHub PR is the primary integration mechanism. Local `integrate`
   serializes the lane and drives the provider merge route; it MUST NOT treat GitHub PR merge as an
   exceptional shortcut around local base mutation.
+- Before release recovery mutation, classify the route as implementation, metadata closure, included-task closure, stale branch cleanup, or provider merge; use GitHub truth for PR/merge state and pass Markdown bodies via files or structured APIs, not inline shell text.
 - If protected `main` requires GitHub PR merges, the agent MUST create/update the GitHub PR,
   wait until all hosted checks are complete and stable (including late agent checks that appear
   after the first green rollup), then merge it through GitHub. If auto-merge remains blocked
@@ -95,5 +95,5 @@ Before manually filling `<slug>` or `<branch>`, use `agentplane task brief <task
 - MUST stop and request re-approval on material drift.
 - Planning and closure happen on base checkout.
 - Do not export task snapshots from task branches.
-- After merged closure, remove stale task branches/worktrees via the cleanup route instead of leaving orphaned local state behind.
+- After merged closure, remove stale task branches/worktrees via the cleanup route; preserve/report dirty worktree state instead of leaving orphaned local state behind or deleting it silently.
 <!-- /ap:fragment -->

package/dist/.build-manifest.json

@@ -2,7 +2,7 @@
   "schema_version": 1,
   "manifest_kind": "package",
   "package_name": "agentplane",
-  "package_version": "0.6.11",
-  "git_head": "f64842db3ede31bdac865dbc7b501351e4c922a3",
-  "watched_runtime_snapshot_hash": "e8fee1bd81eec3cef2943f5f26575301e7fa43e72baac1023fa47da35b543c0b"
+  "package_version": "0.6.13",
+  "git_head": "7f3cf5e7af318abfb625e5e4b31aa658e8e3f1b6",
+  "watched_runtime_snapshot_hash": "2228cc9e8068ec48b39bf69d308012fa6bf2987a515126852e1f4918358163ce"
 }