@pi-unipi/milestone 0.1.8 → 2.0.0

package/README.md

@@ -1,17 +1,47 @@
 # @pi-unipi/milestone
 
-Lifecycle layer for project-level goals. Track progress across multiple workflow cycles via a `MILESTONES.md` file with automatic context injection and sync.
+Track project goals across workflow cycles. A `MILESTONES.md` file with phases and checkbox items that stays in sync with your specs, plans, and completed work.
 
-## Why
+Workflow operates at the task level — brainstorm, plan, work, review. Project goals scatter across those documents. Milestone gives you a single view of what's done and what's left, and keeps the agent aligned with your goals across sessions.
 
-Workflow operates at the task level — brainstorm, plan, work, review. But project goals are scattered across specs, plans, and quick-work docs. Milestone provides a unified view of "what's left to do" and keeps the agent aligned with project goals across sessions.
+## Commands
 
-## How It Works
+| Command | Description |
+|---------|-------------|
+| `/unipi:milestone-onboard` | Create MILESTONES.md from existing workflow docs |
+| `/unipi:milestone-update` | Sync MILESTONES.md with completed work |
 
-1. **MILESTONES.md** — A markdown file with phases and checkbox items that tracks your project goals
-2. **Session start hook** — Reads milestones and injects progress summary into the system prompt
-3. **Session end hook** — Scans modified workflow docs, detects completed items, auto-updates milestones
-4. **Coexist triggers** — Hooks into brainstorm/plan/consolidate to suggest milestone updates
+## Special Triggers
+
+### Session Start
+
+On `before_agent_start`, milestone reads `.unipi/docs/MILESTONES.md` and appends a progress summary to the system prompt:
+
+```
+## Project Milestones
+Overall progress: 5/10 items (50%)
+  Phase 1: Foundation: 3/5 done
+  Phase 2: Features: 2/5 done
+Current focus: Phase 1: Foundation
+```
+
+If MILESTONES.md doesn't exist, no context is injected.
+
+### Session End
+
+On `session_shutdown`, milestone scans workflow docs modified during the session. Detects items that changed from `- [ ]` to `- [x]` and auto-updates MILESTONES.md using exact text matching.
+
+### Coexist Triggers
+
+| Trigger | Behavior |
+|---------|----------|
+| After brainstorm | Checks if new spec items map to milestones, logs suggestions |
+| After plan | Maps plan tasks to milestone items, logs coverage |
+| After consolidate | References auto-sync from session shutdown |
+
+All triggers are non-blocking and skip gracefully if MILESTONES.md doesn't exist.
+
+Milestone registers with the info-screen dashboard, showing progress, current phase, and remaining items.
 
 ## MILESTONES.md Format
 
@@ -40,26 +70,12 @@ updated: 2026-04-28
 - [ ] Notification service
 ```
 
-## Skills
-
-### `/unipi:milestone-onboard`
-
-Create MILESTONES.md from existing workflow docs. Scans specs, plans, quick-work, debug, fix, and chore docs to group scattered tasks into coherent milestone phases.
-
-**Phases:** Explore → Propose → Refine → Write → Report
-
-### `/unipi:milestone-update`
-
-Sync MILESTONES.md with completed work. Detects checkbox changes in workflow docs and updates milestone items.
-
-**Phases:** Scan → Diff → Resolve → Write → Report
-
 ## API Exports
 
 ```typescript
 import {
-  parseMilestones,      // Parse MILESTONES.md → MilestoneDoc
-  writeMilestones,      // Write MilestoneDoc → MILESTONES.md
+  parseMilestones,      // Parse MILESTONES.md to MilestoneDoc
+  writeMilestones,      // Write MilestoneDoc to MILESTONES.md
   updateItemStatus,     // Toggle a checkbox item
   getProgressSummary,   // Get progress stats
 } from "@pi-unipi/milestone";
@@ -73,51 +89,10 @@ import type {
 } from "@pi-unipi/milestone";
 ```
 
-## Lifecycle Hooks
-
-### Session Start
-
-On `before_agent_start`, reads `.unipi/docs/MILESTONES.md` and appends a progress summary to the system prompt:
-
-```
-## Project Milestones
-Overall progress: 5/10 items (50%)
-  Phase 1: Foundation: 3/5 done
-  Phase 2: Features: 2/5 done
-Current focus: Phase 1: Foundation
-```
-
-If MILESTONES.md doesn't exist, no context is injected.
-
-### Session End
-
-On `session_shutdown`, scans workflow docs modified during the session. Detects items that changed from `- [ ]` to `- [x]` and auto-updates MILESTONES.md using exact text matching.
-
-Unmatched items are logged as warnings — resolve manually with `/unipi:milestone-update`.
-
-## Coexist Triggers
-
-| Trigger | Behavior |
-|---------|----------|
-| After brainstorm | Checks if new spec items map to milestones, logs suggestions |
-| After plan | Maps plan tasks to milestone items, logs coverage |
-| After consolidate | References auto-sync from session shutdown |
-
-All triggers are non-blocking and skip gracefully if MILESTONES.md doesn't exist.
-
-## Info Screen
-
-Registers a "Milestones" group in the info-screen dashboard showing:
-- **Progress** — completed/total items with percentage
-- **Current Phase** — phase name with per-phase breakdown
-- **Remaining** — items left to complete
-
-## Configuration
+## Configurables
 
 No configuration needed. Place MILESTONES.md at `.unipi/docs/MILESTONES.md` and the extension handles the rest.
 
-## Dependencies
+## License
 
-- `@pi-unipi/core` — shared constants and utilities
-- `@mariozechner/pi-coding-agent` — extension API
-- `@mariozechner/pi-tui` — TUI types
+MIT

package/commands.ts

@@ -6,7 +6,7 @@
  * loads SKILL.md content and sends it as a user message.
  */
 
-import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";
+import type { ExtensionAPI, ExtensionCommandContext } from "@mariozechner/pi-coding-agent";
 import { UNIPI_PREFIX, MILESTONE_COMMANDS, MILESTONE_DIRS } from "@pi-unipi/core";
 import { parseMilestones } from "./milestone.js";
 import { readFileSync } from "node:fs";
@@ -33,7 +33,7 @@ export function registerCommands(pi: ExtensionAPI): void {
   // milestone-onboard — create milestones from existing work
   pi.registerCommand(`${UNIPI_PREFIX}${MILESTONE_COMMANDS.ONBOARD}`, {
     description: "Create MILESTONES.md from existing workflow docs — scan, propose, refine, write",
-    handler: async (args: string, ctx: any) => {
+    handler: async (args: string, ctx: ExtensionCommandContext) => {
       const skillContent = loadSkill("milestone-onboard");
 
       let message = "Execute the milestone-onboard workflow.";
@@ -55,7 +55,7 @@ export function registerCommands(pi: ExtensionAPI): void {
   // milestone-update — sync milestones with completed work
   pi.registerCommand(`${UNIPI_PREFIX}${MILESTONE_COMMANDS.UPDATE}`, {
     description: "Sync MILESTONES.md with completed work — scan docs, diff checkboxes, auto-update",
-    handler: async (args: string, ctx: any) => {
+    handler: async (args: string, ctx: ExtensionCommandContext) => {
       const skillContent = loadSkill("milestone-update");
 
       let message = "Execute the milestone-update workflow.";

package/index.ts

@@ -21,8 +21,7 @@ export default function milestoneExtension(pi: ExtensionAPI): void {
   registerCommands(pi);
 
   // Register info-screen group
-  const globalObj = globalThis as any;
-  const registry = globalObj.__unipi_info_registry;
+  const registry = globalThis.__unipi_info_registry;
   if (registry) {
     registry.registerGroup({
       id: "milestone",
@@ -63,7 +62,7 @@ export default function milestoneExtension(pi: ExtensionAPI): void {
   }
 
   // Emit module ready event
-  emitEvent(pi as any, UNIPI_EVENTS.MODULE_READY, {
+  emitEvent(pi, UNIPI_EVENTS.MODULE_READY, {
     name: MODULES.MILESTONE,
     version: "0.1.0",
     commands: Object.values(MILESTONE_COMMANDS),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-unipi/milestone",
-  "version": "0.1.8",
+  "version": "2.0.0",
   "description": "Lifecycle layer for project-level goals — MILESTONES.md tracking, session hooks, auto-sync",
   "type": "module",
   "license": "MIT",