agileflow 3.4.3 → 4.0.0-alpha.2

package/src/core/commands/session/history.md

@@ -1,293 +0,0 @@
----
-description: View past session history and metrics
-argument-hint: "[DAYS=7|30|90|all]"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:session:history - Show sessions filtered by age"
-    - "Accepts DAYS argument: 7, 30, 90, or all (default: 30)"
-    - "Filters sessions by created timestamp"
-    - "Shows table with creation date, branch, story, status"
-    - "Read-only display (no prompts)"
-    - "Shows summary: total sessions, active count, inactive count"
-  state_fields:
-    - timeframe_days
-    - filtered_sessions
-    - active_count
-    - inactive_count
----
-
-# /agileflow:session:history
-
-View historical session data and metrics.
-
----
-
-## Purpose
-
-Show all sessions (active and inactive) with creation dates, last activity, and work done.
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js session:history
-```
-
----
-
-## Arguments
-
-| Argument | Default | Description |
-|----------|---------|-------------|
-| DAYS | 30 | Filter sessions by age (7, 30, 90, or "all") |
-
-## IMMEDIATE ACTIONS
-
-### Step 1: Get All Sessions
-
-```bash
-node .agileflow/scripts/session-manager.js list --json
-```
-
-### Step 2: Filter by Timeframe
-
-Parse the DAYS argument and filter sessions by their `created` timestamp.
-
-### Step 3: Display History
-
-```
-📜 Session History (Last 30 days)
-
-┌─────┬────────────┬──────────────────┬─────────────┬────────────┐
-│  #  │ Created    │ Name/Branch      │ Story       │ Status     │
-├─────┼────────────┼──────────────────┼─────────────┼────────────┤
-│  1  │ Dec 20     │ main             │ -           │ ● Active   │
-│  2  │ Dec 22     │ "auth"           │ US-0042     │ ● Active   │
-│  3  │ Dec 23     │ feature/payments │ US-0051     │ ○ Inactive │
-│  4  │ Dec 25     │ "bugfix"         │ US-0038     │ ○ Inactive │
-└─────┴────────────┴──────────────────┴─────────────┴────────────┘
-
-Summary: 4 sessions │ 2 active │ 2 inactive
-```
-
-### Step 4: Show Tips
-
-```
-💡 Tips:
-   • /agileflow:session:new to create a new session
-   • /agileflow:session:delete {id} to remove old sessions
-   • Inactive sessions can be resumed with /agileflow:session:resume
-```
-
-## No History Case
-
-```
-📜 Session History
-
-No sessions found in the last {DAYS} days.
-
-Try /agileflow:session:history DAYS=all to see all sessions.
-```
-
-## Related Commands
-
-- `/agileflow:session:status` - Current status
-- `/agileflow:session:resume` - Switch sessions
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## ⚠️ COMPACT SUMMARY - /agileflow:session:history IS ACTIVE
-
-**CRITICAL**: This command shows historical session data. It NEVER prompts for action - read-only display only.
-
----
-
-### 🚨 RULE #1: PARSE DAYS ARGUMENT
-
-Valid values: `7`, `30`, `90`, `all`
-
-```
-/agileflow:session:history DAYS=7    → Last 7 days
-/agileflow:session:history DAYS=30   → Last 30 days (default)
-/agileflow:session:history DAYS=90   → Last 90 days
-/agileflow:session:history DAYS=all  → All sessions
-/agileflow:session:history           → Default to 30 days
-```
-
----
-
-### 🚨 RULE #2: FILTER BY CREATED TIMESTAMP
-
-After getting all sessions, filter by their `created` timestamp:
-```javascript
-const cutoffDate = new Date(Date.now() - days * 24 * 60 * 60 * 1000);
-filtered = sessions.filter(s => new Date(s.created) >= cutoffDate);
-```
-
-For `DAYS=all`, include all sessions.
-
----
-
-### 🚨 RULE #3: DISPLAY FORMAT
-
-**Structure:**
-1. Header with emoji: `📜 Session History (Last {DAYS} days)`
-2. Table with columns: #, Created, Name/Branch, Story, Status
-3. Summary: `Summary: X sessions │ Y active │ Z inactive`
-4. Tips (optional)
-
-**Example:**
-```
-📜 Session History (Last 30 days)
-
-┌─────┬────────────┬──────────────────┬─────────────┬────────────┐
-│  #  │ Created    │ Name/Branch      │ Story       │ Status     │
-├─────┼────────────┼──────────────────┼─────────────┼────────────┤
-│  1  │ Dec 20     │ main             │ -           │ ● Active   │
-│  2  │ Dec 22     │ "auth"           │ US-0042     │ ● Active   │
-│  3  │ Dec 23     │ feature/payments │ US-0051     │ ○ Inactive │
-│  4  │ Dec 25     │ "bugfix"         │ US-0038     │ ○ Inactive │
-└─────┴────────────┴──────────────────┴─────────────┴────────────┘
-
-Summary: 4 sessions │ 2 active │ 2 inactive
-```
-
----
-
-### 🚨 RULE #4: DATE FORMATTING
-
-Show dates in compact form:
-- Format: `Dec 20` (month + day)
-- No year needed (assumed current year or implied by context)
-- Makes table compact
-
----
-
-### 🚨 RULE #5: READ-ONLY DISPLAY (NO PROMPTS)
-
-**NEVER use AskUserQuestion.** This command is informational only.
-
-For user actions, show tips:
-```
-💡 Tips:
-   • /agileflow:session:new to create a new session
-   • /agileflow:session:delete {id} to remove old sessions
-   • Inactive sessions can be resumed with /agileflow:session:resume
-```
-
----
-
-### 🚨 RULE #6: HANDLE EMPTY RESULTS
-
-If no sessions in timeframe:
-```
-📜 Session History
-
-No sessions found in the last {DAYS} days.
-
-Try /agileflow:session:history DAYS=all to see all sessions.
-```
-
----
-
-### FORMATTING RULES
-
-| Element | Format | Example |
-|---------|--------|---------|
-| Date | Month + day | `Dec 20` |
-| Session name | Nickname or branch | `"auth"` or `feature/payments` |
-| Story | US-#### or dash | `US-0042` or `-` |
-| Status | ● Active or ○ Inactive | `● Active` |
-| Summary | Count format | `4 sessions │ 2 active │ 2 inactive` |
-
----
-
-### KEY FILES TO REMEMBER
-
-| File | Purpose |
-|------|---------|
-| `.agileflow/sessions/registry.json` | All sessions with created timestamps |
-| `.agileflow/scripts/session-manager.js` | Data source via list --json |
-
----
-
-### WORKFLOW
-
-1. **Parse DAYS argument** → Default to 30 if not provided
-2. **Get all sessions** → `session-manager.js list --json`
-3. **Filter by date** → Compare created timestamp to cutoff
-4. **Count active/inactive** → Check status field
-5. **Build table** → Format with proper columns
-6. **Show summary** → Total and active counts
-7. **Optionally show** → Tips for actions
-
----
-
-### SESSION DATA STRUCTURE
-
-From `session-manager.js list --json`:
-```json
-{
-  "id": 1,
-  "branch": "main",
-  "nickname": null,
-  "status": "active",
-  "created": "2025-12-20T10:00:00Z",
-  "last_active": "2025-12-20T10:30:00Z"
-}
-```
-
-Use `created` for filtering.
-
----
-
-### ARGUMENT VALIDATION
-
-```
-DAYS=7    ✅ Valid
-DAYS=30   ✅ Valid
-DAYS=90   ✅ Valid
-DAYS=all  ✅ Valid
-DAYS=14   ❌ Invalid (suggest 7, 30, 90, or all)
-DAYS=xyz  ❌ Invalid (suggest 7, 30, 90, or all)
-(no arg)  ✅ Valid (default to 30)
-```
-
----
-
-### ANTI-PATTERNS (DON'T DO THESE)
-
-❌ Use AskUserQuestion to prompt for action
-❌ Show "Delete old sessions?" or similar prompts
-❌ Accept arbitrary DAYS values (only 7, 30, 90, all)
-❌ Show full ISO timestamp (use compact date)
-❌ Show absolute paths (too much info)
-❌ Forget summary line with counts
-
-### DO THESE INSTEAD
-
-✅ Display as read-only information
-✅ Use ● and ○ bullets for status
-✅ Accept only: 7, 30, 90, all
-✅ Format dates compactly: Dec 20
-✅ Show summary with active/inactive counts
-✅ Optionally show tips for related commands
-
----
-
-### REMEMBER AFTER COMPACTION
-
-- `/agileflow:session:history` IS ACTIVE
-- Accepts DAYS: 7, 30, 90, all (default: 30)
-- Filter by created timestamp
-- Format: header + table + summary
-- Use ● for active, ○ for inactive
-- NEVER prompt for action (read-only)
-- Show date as "Dec 20" (compact format)
-- Optionally show tips
-
-<!-- COMPACT_SUMMARY_END -->

package/src/core/commands/session/init.md

@@ -1,210 +0,0 @@
----
-description: Initialize session harness with test verification
-argument-hint: "(no arguments)"
-compact_context:
-  priority: high
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:session:init - Initialize session tracking"
-    - "Creates `.agileflow/sessions/` directory and `registry.json` if missing"
-    - "Registers current directory as active session with lock file"
-    - "Runs automatically via SessionStart hook on session begin"
-    - "Safe to run multiple times (idempotent operation)"
-    - "If registry.json exists, validates schema before use"
-  state_fields:
-    - session_id
-    - registry_status
-    - active_session_count
----
-
-# /agileflow:session:init
-
-Initialize or verify the session management system.
-
----
-
-## Purpose
-
-Sets up session tracking infrastructure:
-- Creates `.agileflow/sessions/` directory
-- Initializes `registry.json` if missing
-- Registers the current session
-- Displays session status
-
-This command is typically called automatically by the SessionStart hook.
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js session:init
-```
-
----
-
-## IMMEDIATE ACTIONS
-
-### Step 1: Ensure Session Infrastructure
-
-```bash
-node .agileflow/scripts/session-manager.js register
-```
-
-This will:
-- Create `.agileflow/sessions/` if missing
-- Create `registry.json` with schema if missing
-- Register current directory as a session
-- Create lock file with current PID
-
-### Step 2: Check for Other Active Sessions
-
-```bash
-node .agileflow/scripts/session-manager.js count
-```
-
-If `count > 0`, there are other active sessions.
-
-### Step 3: Display Status
-
-**If no other sessions:**
-```
-✓ Session initialized
-
-  Session ID: 1
-  Path: /home/user/project
-  Branch: main
-
-No other active sessions detected.
-```
-
-**If other sessions active:**
-```
-✓ Session initialized
-
-  Session ID: 1 (current)
-  Path: /home/user/project
-  Branch: main
-
-⚠️ {count} other session(s) active in this repo.
-   Run /agileflow:session:status to see all sessions.
-   Run /agileflow:session:new to create isolated workspace.
-```
-
-## Already Initialized Case
-
-If session is already registered:
-```
-✓ Session already active
-
-  Session ID: 1
-  Path: /home/user/project
-  Branch: main
-```
-
-## Related Commands
-
-- `/agileflow:session:status` - View all sessions
-- `/agileflow:session:new` - Create parallel session
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## ⚠️ COMPACT SUMMARY - /agileflow:session:init IS ACTIVE
-
-**CRITICAL**: This command sets up session tracking infrastructure. It MUST run before any session management features work.
-
----
-
-### 🚨 RULE #1: IDEMPOTENT OPERATION
-
-This command is **safe to run multiple times**. It:
-- Creates `.agileflow/sessions/` if missing
-- Creates `registry.json` with schema if missing
-- Registers current directory if not already registered
-- Updates lock file if already registered
-
-**No data is lost, no conflicts occur on repeated runs.**
-
----
-
-### 🚨 RULE #2: AUTOMATIC INVOCATION
-
-This command runs automatically via **SessionStart hook**. You typically don't call it manually unless:
-- Debugging session tracking
-- Setting up manually without hook
-- Recovering from corrupted session state
-
----
-
-### 🚨 RULE #3: REGISTRY SCHEMA
-
-The generated `registry.json` has this structure:
-```json
-{
-  "version": "1.0",
-  "sessions": [
-    {
-      "id": 1,
-      "path": "/home/user/project",
-      "branch": "main",
-      "created": "2025-12-20T10:00:00Z",
-      "last_active": "2025-12-20T10:30:00Z",
-      "is_main": true,
-      "nickname": null,
-      "status": "active"
-    }
-  ]
-}
-```
-
----
-
-### 🚨 RULE #4: LOCK FILE MANAGEMENT
-
-Session tracking uses lock files at `.agileflow/sessions/{id}.lock`:
-- Lock file = session is **active** (has running Claude process)
-- No lock file = session is **inactive** (can be resumed)
-- Lock files are created on init, removed on `/agileflow:session:end`
-
----
-
-### KEY FILES TO REMEMBER
-
-| File | Purpose |
-|------|---------|
-| `.agileflow/sessions/` | Session directory (created by init) |
-| `.agileflow/sessions/registry.json` | Master registry of all sessions |
-| `.agileflow/sessions/{id}.lock` | Lock file marking session active |
-| `.agileflow/scripts/session-manager.js` | Script that does the work |
-
----
-
-### TYPICAL WORKFLOW
-
-1. **First time in project**:
-   - SessionStart hook runs → `/agileflow:session:init` called automatically
-   - Creates infrastructure, registers main session
-   - You never see this happening
-
-2. **Debugging session state**:
-   - Run `/agileflow:session:init` manually
-   - Check `.agileflow/sessions/registry.json` for current state
-   - Use `/agileflow:session:status` to view readable output
-
-3. **Manual setup**:
-   - If hook is disabled, run this to initialize
-   - Then use other session commands
-
----
-
-### REMEMBER AFTER COMPACTION
-
-- `/agileflow:session:init` IS ACTIVE
-- Creates `.agileflow/sessions/` directory and registry
-- Runs automatically via SessionStart hook
-- Safe to run multiple times (idempotent)
-- Lock files track active vs inactive sessions
-- Check `registry.json` for current session state
-
-<!-- COMPACT_SUMMARY_END -->