okstra 0.104.0 → 0.106.0

package/runtime/skills/okstra-rollup/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: okstra-rollup
+description: |
+  Use when the user wants run results from MULTIPLE okstra tasks collected and summarized at once — a task-group digest or a whole-project roll-up, not a single task. Aggregates per-task run count, elapsed time, error count, and latest report path, plus group-level totals and status/category/phase tallies, then synthesizes a cross-task prose summary from the report files. Make sure to use this skill whenever the user mentions "okstra rollup", "롤업", "task-group 요약", "그룹 단위 리포트", "여러 task 결과 모아", "전체 task 현황 요약", "cross-task summary", "그룹 종합 리포트", "모든 task 정리", "run 결과 한꺼번에", even if they don't say "rollup". For a SINGLE task's report/time/errors/recap use okstra-inspect instead; for a forward-looking work plan over non-done tasks use okstra-schedule.
+---
+
+# OKSTRA Rollup
+
+Cross-task roll-up: collect every catalog task's run results (optionally scoped to one task-group) and summarize them together. The `rollup` CLI does all deterministic aggregation — counts, time sums, error tallies, status/category/phase distributions. You resolve scope, call it, render the table, and synthesize the prose digest from the report files. **Never recompute totals or re-tally by hand** — the CLI is the SSOT for the numbers.
+
+This skill is read-only. It never mutates task artifacts.
+
+## Step 0: Verify okstra runtime + project setup
+
+Run each command as a **separate Bash tool call**, each starting with the literal token `okstra` so the `Bash(okstra:*)` permission match succeeds. Do **not** wrap any of them in `if`, `eval`, `$(...)`, `VAR=...`, `||`, `&&`, or an `npx` fallback — those defeat the permission match.
+
+1. `okstra ensure-installed --runtime claude-code`
+   Non-zero exit → tell the user: "okstra not installed — run `/okstra-setup` first." Then stop.
+
+2. `okstra check-project --json`
+   Parse `{ok, projectRoot, ...}` from stdout. `ok: false` → "this project has no okstra setup. Run `/okstra-setup` first." Then stop. `ok: true` → carry `projectRoot` as a literal string.
+
+## Step 1: Resolve scope
+
+- User named a task-group (e.g. "alpha 그룹 요약") → use it as `--task-group <group>`.
+- User asked for the whole project ("전체 task", "프로젝트 전체") or named no scope → omit `--task-group` (whole catalog).
+- If genuinely ambiguous, ask once: one task-group, or the whole project? Do not silently guess a specific group.
+
+## Step 2: Fetch the roll-up
+
+```bash
+okstra rollup --task-group <group> --project-root <projectRoot> --json
+```
+
+Omit `--task-group` for the whole project. The JSON shape (all durations are **raw milliseconds**):
+
+- `taskGroup` — the scope (`null` = whole project), `taskCount` — number of tasks.
+- `tasks[]` — per task: `taskKey, taskGroup, taskId, taskType, workCategory, workStatus, currentPhase, currentPhaseState, nextRecommendedPhase, latestRunStatus, updatedAt, reportPath, runCount, cpuSumMs, wallClockMs, errorCount`.
+- `totals` — `runs, cpuSumMs, wallClockMs, errors`, plus `byWorkStatus`, `byWorkCategory`, `byCurrentPhase`, `byTaskType` (each a `{value: count}` map).
+
+`runCount` counts every timeline run; `cpuSumMs`/`wallClockMs` only reflect runs that reached Phase 7 usage, so they can be `0` while `runCount > 0`. `reportPath` is project-relative and may be empty (task not yet reported).
+
+If `taskCount` is `0`, tell the user there are no okstra tasks in that scope and stop.
+
+## Step 3: Render the roll-up table
+
+Convert every `*Ms` to `HH:MM:SS` (zero-pad; never show raw ms). `cpuSumMs` is CPU-sum (lead + workers overlap), not wall-clock — label it "CPU"; only surface `wallClockMs` when the user asks. Sort tasks by `updatedAt` desc.
+
+```markdown
+## okstra Rollup — <task-group or "whole project"> (<taskCount> tasks)
+
+| Task | Category | workStatus | Phase | Runs | CPU | Errors | Report |
+|------|----------|------------|-------|------|-----|--------|--------|
+| DEV-1 | bugfix | done | final-verification | 2 | 00:25:00 | 2 | ✓ |
+| DEV-2 | feature | in-progress | implementation | 1 | 00:00:00 | 0 | — |
+
+**Totals:** 3 runs · CPU 00:25:00 · 2 errors
+**workStatus:** done 1 · in-progress 1   **category:** bugfix 1 · feature 1
+```
+
+Render `Report` as `✓` when `reportPath` is non-empty, else `—`. Build the status/category lines from the `totals` tally maps verbatim — do not count the `tasks[]` array yourself.
+
+## Step 4: Synthesize the digest (the summary)
+
+This is the skill's value-add over a bare table. When the user asked to "요약"/"summarize"/"digest"/"정리" (the common case), produce a short cross-task narrative:
+
+1. For each task with a non-empty `reportPath` whose file exists under `<projectRoot>/<reportPath>`, read it and write a 1–2 line summary of what it accomplished and its recommended next step.
+2. Above the per-task lines, write a 2–4 sentence group-level synthesis: what was delivered across the group, where the open work sits (use `byWorkStatus`/`byCurrentPhase`), and any error hot-spots (tasks with high `errorCount`).
+3. Cite each per-task claim with the report path as `<reportPath>` so the reader can open it.
+
+For tasks with no report, state the current phase/workStatus instead of inventing a summary — do not read non-report artifacts to fill the gap.
+
+Keep the digest to what the reports actually say; if a report is missing or empty, say so rather than guessing. For a deeper single-task drill-down (full report, per-worker time, error breakdown, run-to-run recap), point the user to `/okstra-inspect`.

package/src/cli-registry.mjs

@@ -152,6 +152,13 @@ export const COMMAND_REGISTRY = [
     category: "introspection",
     summary: ["Assemble a task's run-to-run phase recap or append a recap log entry"],
   },
+  {
+    name: "rollup",
+    module: "./commands/inspect/rollup.mjs",
+    export: "run",
+    category: "introspection",
+    summary: ["Roll up run results across a task-group's tasks (raw ms + tallies)"],
+  },
   {
     name: "container",
     module: "./commands/inspect/container.mjs",

package/src/commands/inspect/rollup.mjs

@@ -0,0 +1,27 @@
+import { runPythonModule } from "../../lib/python-helper.mjs";
+
+const USAGE = `okstra rollup — roll up run results across a task-group's tasks
+
+Usage:
+  okstra rollup [--task-group <group>] [--project-root <dir>] [--cwd <dir>]
+
+Read-only. Prints a JSON roll-up of every catalog task (optionally scoped to one
+task-group): per-task run count, elapsed time (raw ms), error count, and the
+latest report path, plus group-level totals and status/category/phase tallies.
+With no --task-group it covers the whole project catalog. Time is raw ms; the
+caller formats HH:MM:SS and synthesizes the prose digest from the report files.
+`;
+
+export async function run(args) {
+  if (args.includes("--help") || args.includes("-h")) {
+    process.stdout.write(USAGE);
+    return 0;
+  }
+
+  const result = await runPythonModule({
+    module: "okstra_ctl.rollup",
+    args,
+    stdio: "inherit-stdout",
+  });
+  return result.code;
+}

package/src/lib/skill-catalog.mjs

@@ -11,6 +11,7 @@ export const USER_SKILL_NAMES = Object.freeze([
   "okstra-manager",
   "okstra-memory",
   "okstra-inspect",
+  "okstra-rollup",
   "okstra-schedule",
   "okstra-container-build",
 ]);