okstra 0.232.0 → 0.234.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +19 -283
- package/dist/cli-registry.mjs +14 -1
- package/dist/cli-registry.mjs.map +1 -1
- package/dist/commands/execute/render-bundle.d.mts +6 -1
- package/dist/commands/execute/render-bundle.mjs +139 -32
- package/dist/commands/execute/render-bundle.mjs.map +1 -1
- package/dist/commands/lifecycle/config.mjs +6 -74
- package/dist/commands/lifecycle/config.mjs.map +1 -1
- package/dist/commands/trace/capacity.d.mts +12 -0
- package/dist/commands/trace/capacity.mjs +21 -0
- package/dist/commands/trace/capacity.mjs.map +1 -0
- package/dist/commands/trace/model.d.mts +89 -0
- package/dist/commands/trace/model.mjs +251 -0
- package/dist/commands/trace/model.mjs.map +1 -0
- package/dist/commands/trace/progression.d.mts +11 -0
- package/dist/commands/trace/progression.mjs +194 -0
- package/dist/commands/trace/progression.mjs.map +1 -0
- package/dist/commands/trace/review.d.mts +7 -0
- package/dist/commands/trace/review.mjs +51 -0
- package/dist/commands/trace/review.mjs.map +1 -0
- package/dist/commands/trace/task-link.d.mts +18 -0
- package/dist/commands/trace/task-link.mjs +72 -0
- package/dist/commands/trace/task-link.mjs.map +1 -0
- package/dist/commands/trace/trace.d.mts +1 -0
- package/dist/commands/trace/trace.mjs +293 -0
- package/dist/commands/trace/trace.mjs.map +1 -0
- package/dist/lib/bounded-file.d.mts +1 -0
- package/dist/lib/bounded-file.mjs +36 -0
- package/dist/lib/bounded-file.mjs.map +1 -0
- package/dist/lib/config-store.d.mts +34 -0
- package/dist/lib/config-store.mjs +70 -0
- package/dist/lib/config-store.mjs.map +1 -0
- package/dist/lib/file-lock.mjs +4 -5
- package/dist/lib/file-lock.mjs.map +1 -1
- package/dist/lib/input-limit.d.mts +4 -0
- package/dist/lib/input-limit.mjs +8 -0
- package/dist/lib/input-limit.mjs.map +1 -0
- package/dist/lib/memory-auto-register.mjs +2 -17
- package/dist/lib/memory-auto-register.mjs.map +1 -1
- package/dist/lib/report-language-tag.d.mts +1 -0
- package/dist/lib/report-language-tag.mjs +4 -0
- package/dist/lib/report-language-tag.mjs.map +1 -0
- package/dist/lib/report-language.d.mts +1 -0
- package/dist/lib/report-language.mjs +50 -0
- package/dist/lib/report-language.mjs.map +1 -0
- package/dist/lib/skill-catalog.mjs +3 -0
- package/dist/lib/skill-catalog.mjs.map +1 -1
- package/docs/architecture/storage-model.md +55 -5
- package/docs/architecture.md +10 -4
- package/docs/cli.md +320 -3
- package/docs/contributor-change-matrix.md +1 -2
- package/docs/project-structure-overview.md +34 -43
- package/package.json +1 -1
- package/runtime/BUILD.json +2 -2
- package/runtime/agents/operations/trace-interface-review.json +6 -0
- package/runtime/agents/operations/trace-scope-review.json +6 -0
- package/runtime/prompts/coding-preflight/authoring-checks.md +1 -1
- package/runtime/prompts/coding-preflight/clean-code.md +18 -20
- package/runtime/prompts/coding-preflight/overview.md +1 -1
- package/runtime/prompts/duties/code-reviewer.json +1 -1
- package/runtime/prompts/duties/interface-reviewer.json +32 -0
- package/runtime/prompts/host-orchestration/README.md +18 -9
- package/runtime/prompts/launch.template.md +3 -2
- package/runtime/prompts/lead/context-loader.md +2 -0
- package/runtime/prompts/lead/okstra-lead-contract.md +7 -7
- package/runtime/prompts/lead/report-writer.md +6 -6
- package/runtime/prompts/profiles/_coding-conventions-preflight.md +2 -2
- package/runtime/prompts/profiles/_common-contract.md +1 -1
- package/runtime/python/okstra_ctl/agent/invocation.py +1 -0
- package/runtime/python/okstra_ctl/agent/prompt_cli/cli.py +66 -26
- package/runtime/python/okstra_ctl/agent/prompt_cli/corrections.py +23 -8
- package/runtime/python/okstra_ctl/agent/prompt_cli/materialize.py +28 -10
- package/runtime/python/okstra_ctl/agent/prompt_cli/results.py +8 -11
- package/runtime/python/okstra_ctl/agent/standalone.py +12 -0
- package/runtime/python/okstra_ctl/analysis_packet.py +22 -11
- package/runtime/python/okstra_ctl/business_flow/cli.py +60 -6
- package/runtime/python/okstra_ctl/business_flow/contracts.py +12 -1
- package/runtime/python/okstra_ctl/business_flow/engine.py +17 -5
- package/runtime/python/okstra_ctl/business_flow/history.py +60 -0
- package/runtime/python/okstra_ctl/business_flow/source.py +35 -2
- package/runtime/python/okstra_ctl/business_flow/store.py +51 -14
- package/runtime/python/okstra_ctl/business_flow/sweep.py +124 -0
- package/runtime/python/okstra_ctl/code_review_census.py +93 -2
- package/runtime/python/okstra_ctl/code_review_prepare.py +381 -0
- package/runtime/python/okstra_ctl/code_review_run.py +384 -0
- package/runtime/python/okstra_ctl/code_review_scope.py +13 -0
- package/runtime/python/okstra_ctl/code_review_supervisor.py +41 -0
- package/runtime/python/okstra_ctl/code_review_target.py +140 -15
- package/runtime/python/okstra_ctl/coverage_census.py +11 -2
- package/runtime/python/okstra_ctl/design_snapshot.py +16 -9
- package/runtime/python/okstra_ctl/direct_work.py +45 -3
- package/runtime/python/okstra_ctl/dispatch_core.py +31 -15
- package/runtime/python/okstra_ctl/dispatch_state.py +9 -2
- package/runtime/python/okstra_ctl/domain/role.py +1 -0
- package/runtime/python/okstra_ctl/doyouknow/cli.py +9 -9
- package/runtime/python/okstra_ctl/doyouknow/config.py +2 -2
- package/runtime/python/okstra_ctl/doyouknow/group_view.py +152 -0
- package/runtime/python/okstra_ctl/doyouknow/source_contracts.py +4 -3
- package/runtime/python/okstra_ctl/doyouknow/source_store.py +2 -2
- package/runtime/python/okstra_ctl/doyouknow/sources/business.py +116 -0
- package/runtime/python/okstra_ctl/doyouknow/sources/manager.py +48 -9
- package/runtime/python/okstra_ctl/doyouknow/sync.py +34 -9
- package/runtime/python/okstra_ctl/final_report_schema.py +37 -34
- package/runtime/python/okstra_ctl/fixed_text.py +10 -0
- package/runtime/python/okstra_ctl/incremental_carry.py +6 -7
- package/runtime/python/okstra_ctl/initial_prompt_materialization.py +9 -2
- package/runtime/python/okstra_ctl/json_boundary.py +33 -6
- package/runtime/python/okstra_ctl/manager_cli.py +122 -1
- package/runtime/python/okstra_ctl/manager_journal.py +126 -0
- package/runtime/python/okstra_ctl/manager_launch.py +3 -3
- package/runtime/python/okstra_ctl/manager_log.py +221 -0
- package/runtime/python/okstra_ctl/manager_paths.py +8 -0
- package/runtime/python/okstra_ctl/manager_resume.py +59 -0
- package/runtime/python/okstra_ctl/manager_split.py +2 -2
- package/runtime/python/okstra_ctl/manager_store.py +116 -17
- package/runtime/python/okstra_ctl/manager_sync.py +42 -3
- package/runtime/python/okstra_ctl/manager_view.py +35 -2
- package/runtime/python/okstra_ctl/material.py +2 -0
- package/runtime/python/okstra_ctl/model_cli.py +64 -14
- package/runtime/python/okstra_ctl/model_defaults.py +22 -0
- package/runtime/python/okstra_ctl/model_io/renderers.py +3 -0
- package/runtime/python/okstra_ctl/operation_invocation.py +207 -28
- package/runtime/python/okstra_ctl/path_hints.py +14 -3
- package/runtime/python/okstra_ctl/paths.py +6 -1
- package/runtime/python/okstra_ctl/phases/catalog.py +24 -7
- package/runtime/python/okstra_ctl/phases/implementation/host-rules.md +3 -3
- package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-diff-review.md +8 -6
- package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-self-check.md +1 -1
- package/runtime/python/okstra_ctl/phases/implementation_option_selection/profile.md +1 -1
- package/runtime/python/okstra_ctl/phases/implementation_option_selection/votes.py +11 -11
- package/runtime/python/okstra_ctl/phases/implementation_planning/authoring.py +12 -9
- package/runtime/python/okstra_ctl/phases/implementation_planning/host-rules.md +3 -6
- package/runtime/python/okstra_ctl/phases/implementation_planning/instructions/plan-body-verification.md +12 -10
- package/runtime/python/okstra_ctl/phases/implementation_planning/profile.md +5 -5
- package/runtime/python/okstra_ctl/phases/improvement_discovery/lenses.py +12 -0
- package/runtime/python/okstra_ctl/phases/improvement_discovery/profile.md +7 -6
- package/runtime/python/okstra_ctl/phases/improvement_discovery/resolved_census.py +159 -0
- package/runtime/python/okstra_ctl/phases/improvement_discovery/spec.md +5 -2
- package/runtime/python/okstra_ctl/phases/improvement_discovery/validation.py +21 -7
- package/runtime/python/okstra_ctl/phases/release_handoff/boundary.json +1 -1
- package/runtime/python/okstra_ctl/phases/release_handoff/profile.md +4 -1
- package/runtime/python/okstra_ctl/plan_verify_cli.py +6 -4
- package/runtime/python/okstra_ctl/project_group.py +175 -0
- package/runtime/python/okstra_ctl/project_group_cli.py +62 -0
- package/runtime/python/okstra_ctl/render.py +28 -2
- package/runtime/python/okstra_ctl/report_assembly.py +38 -11
- package/runtime/python/okstra_ctl/report_contract.py +26 -0
- package/runtime/python/okstra_ctl/report_corrections.py +36 -20
- package/runtime/python/okstra_ctl/report_inputs.py +1 -0
- package/runtime/python/okstra_ctl/report_language.py +4 -1
- package/runtime/python/okstra_ctl/report_narrative.py +179 -7
- package/runtime/python/okstra_ctl/report_projections.py +64 -18
- package/runtime/python/okstra_ctl/report_synthesis_packet.py +86 -36
- package/runtime/python/okstra_ctl/run.py +43 -35
- package/runtime/python/okstra_ctl/run_context.py +10 -1
- package/runtime/python/okstra_ctl/set_work_status.py +4 -15
- package/runtime/python/okstra_ctl/task_list_cli.py +34 -8
- package/runtime/python/okstra_ctl/task_query.py +239 -0
- package/runtime/python/okstra_ctl/trace_review.py +264 -0
- package/runtime/python/okstra_ctl/trace_tasks.py +197 -0
- package/runtime/python/okstra_ctl/user_authorization.py +14 -0
- package/runtime/python/okstra_ctl/wizard/confirmation.py +7 -3
- package/runtime/python/okstra_ctl/wizard/launch.py +52 -0
- package/runtime/python/okstra_ctl/wizard/launch_cli.py +39 -0
- package/runtime/python/okstra_ctl/wizard/outcome.py +17 -16
- package/runtime/python/okstra_ctl/wizard/registry.py +1 -1
- package/runtime/python/okstra_ctl/wizard/render.py +8 -0
- package/runtime/python/okstra_ctl/wizard/state.py +2 -1
- package/runtime/python/okstra_project/state.py +20 -0
- package/runtime/python/okstra_token_usage/blocks.py +74 -0
- package/runtime/python/okstra_token_usage/cli.py +23 -10
- package/runtime/python/okstra_token_usage/collect.py +25 -22
- package/runtime/python/okstra_token_usage/policy.py +193 -0
- package/runtime/schemas/business-flow-v1.schema.json +3 -0
- package/runtime/schemas/doyouknow-config-v1.schema.json +1 -1
- package/runtime/schemas/report-synthesis-packet-v1.0.schema.json +1 -1
- package/runtime/skills/_fragments/wizard-confirm-step.md +1 -1
- package/runtime/skills/_fragments/wizard-preflight.md +1 -1
- package/runtime/skills/_fragments/wizard-prompt-loop.md +3 -5
- package/runtime/skills/_fragments/wizard-relay-protocol.md +1 -1
- package/runtime/skills/_fragments/wizard-render-bundle.md +15 -29
- package/runtime/skills/okstra-brief-gen/SKILL.md +7 -7
- package/runtime/skills/okstra-brief-gen/references/tracker-recursion.md +1 -1
- package/runtime/skills/okstra-code-review/SKILL.md +58 -50
- package/runtime/skills/okstra-code-review/references/census-rules.md +6 -6
- package/runtime/skills/okstra-code-review/references/review-calibration.md +8 -12
- package/runtime/skills/okstra-discussion/SKILL.md +22 -38
- package/runtime/skills/okstra-explain-flow/SKILL.md +33 -4
- package/runtime/skills/okstra-manager/SKILL.md +24 -0
- package/runtime/skills/okstra-memory/SKILL.md +1 -1
- package/runtime/skills/okstra-pr-gen/SKILL.md +1 -1
- package/runtime/skills/okstra-run/SKILL.md +55 -183
- package/runtime/skills/okstra-schedule-gen/SKILL.md +9 -13
- package/runtime/skills/okstra-setup/SKILL.md +3 -2
- package/runtime/skills/okstra-setup/references/project-config.md +2 -4
- package/runtime/skills/okstra-tdd/SKILL.md +187 -0
- package/runtime/skills/okstra-user-response/SKILL.md +4 -2
- package/runtime/templates/doyouknow/group-view.css +103 -0
- package/runtime/templates/doyouknow/group-view.js +317 -0
- package/runtime/templates/doyouknow/group-view.template.html +72 -0
- package/runtime/templates/manager/view.template.html +4 -0
- package/runtime/templates/report-writer-prompt-preamble.md +15 -3
- package/runtime/templates/trace/trace.template.md +42 -0
- package/runtime/validators/checks/fixtures-02.py +25 -33
- package/runtime/validators/validate-run.py +93 -36
|
@@ -42,9 +42,8 @@ If the call fails with `unknown command: preflight`, the `okstra` binary on PATH
|
|
|
42
42
|
|
|
43
43
|
## What the finished document looks like
|
|
44
44
|
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
Step 4, and again at Step 7.
|
|
45
|
+
This is the shape the rules below add up to — read it once before Step 4, and
|
|
46
|
+
again at Step 7.
|
|
48
47
|
|
|
49
48
|
| Section | Holds | Never holds |
|
|
50
49
|
|---|---|---|
|
|
@@ -54,8 +53,6 @@ Step 4, and again at Step 7.
|
|
|
54
53
|
| `## Gantt Chart` | one bar per selected stage, label and bar only | `days=`, per-row `! crit`/`est` |
|
|
55
54
|
| `## Task Details` | per task: Item/Detail, Problem, Solution, Work Breakdown, one block per stage (`Steps` + `Exit criteria`), Verification Commands, Rollback | `Value`, `Acceptance`, a risk section, a cross-task section, a next-actions list |
|
|
56
55
|
|
|
57
|
-
Every one of those "never holds" entries was in a shipped schedule. Four
|
|
58
|
-
restated a table that sat directly above or below them.
|
|
59
56
|
|
|
60
57
|
## Audience & authority (READ FIRST — drives everything below)
|
|
61
58
|
|
|
@@ -66,7 +63,7 @@ restated a table that sat directly above or below them.
|
|
|
66
63
|
**Assume the user and their team hold full authority and every permission required.** External approvals, access grants, sign-off, and vendor coordination are treated as already satisfied unless a report names a concrete external dependency outside the user's control. Concretely:
|
|
67
64
|
|
|
68
65
|
- **Effort sizing & day totals** count engineering work only — strip approval-waiting / coordination buffers from source sizings (note the adjustment in `## Executive Summary` if material).
|
|
69
|
-
- **Gantt bars** represent engineering duration only; no dead-time gaps for approval cycles.
|
|
66
|
+
- **Gantt bars** represent engineering duration only; no dead-time gaps for approval cycles.
|
|
70
67
|
- **Steps and Exit criteria** are concrete engineering work; items like "permission check", "approval request", "stakeholder alignment" MUST NOT be emitted.
|
|
71
68
|
|
|
72
69
|
**The schedule must be self-contained.** Opaque codes pulled from internal reports (`FC-5`, `UC-12`, `M1`, decision-item letters, …) must not appear unresolved. Choose one per identifier: **Form A** (≤3 codes) — replace the code inline with a 5–20 character one-line description of the item; **Form B** (≥4 recurring codes) — keep the codes and emit a `## Glossary` table as the last section resolving every one. Decision-item letters (`A1`, `B2`, …) are approval items and may not appear at all. TASK-IDs listed in `## At a Glance` need neither.
|
|
@@ -103,7 +100,7 @@ One computation rule the template scaffold cannot carry inline:
|
|
|
103
100
|
|
|
104
101
|
### Step 2: Filter by workStatus
|
|
105
102
|
|
|
106
|
-
|
|
103
|
+
Filter on the fixed view's `Work status`: `done` → exclude; everything else (`todo` / `in-progress` / `blocked` / `phase-done`, or a missing or empty value) → include.
|
|
107
104
|
|
|
108
105
|
If 0 tasks remain, output `All tasks in this task-group are done. There is no schedule to generate.` and stop **without creating a file**.
|
|
109
106
|
|
|
@@ -166,11 +163,11 @@ Selecting which source rows belong in a schedule is not summarising. Dropping a
|
|
|
166
163
|
|
|
167
164
|
**`## Executive Summary` opens with `**목적**` and `**달라지는 것**`; the validator requires both.** A reader who opens only that section must learn why the work happens and what is true when it ends — scope and day arithmetic alone say neither. The material is in the report's `humanSummary` (`headline`, `outcome`, `whyItMatters`), which `okstra stage-map` carries as `planning.reportSummary`. Rewrite it: that field addresses an approver ("your two questions", "the option you approved"), and that framing must not survive. `decisions`, `actions` and `blockers` are not carried at all — they ask for sign-off.
|
|
168
165
|
|
|
169
|
-
**State the limits in the outcome list.** When the work stops short of what its name suggests, the summary says so.
|
|
166
|
+
**State the limits in the outcome list.** When the work stops short of what its name suggests, the summary says so. For example, a migration that leaves some ports vendor-shaped says "디렉터리 구조 완료, 격리 미완" rather than letting the reader assume the isolation is finished. A summary that only lists wins is the kind a reader stops trusting on the first surprise.
|
|
170
167
|
|
|
171
168
|
**A stage block is `Steps` plus `Exit criteria`, and nothing else.** The `Steps` table comes from `stepwiseExecution` — one row per step with what it does (keep the leading `RED:` / `GREEN:` marker), the files it touches, and what the executor should see when it succeeds, from that step's `expected`. In the 대상 column separate entries with `<br>`, not a comma: a comma-joined path list stretches that column and squeezes the two text columns into a gutter. `Exit criteria` is one line from `exitContract` saying when the stage is finished.
|
|
172
169
|
|
|
173
|
-
Do not render `sliceValue` — it argues why the plan sliced the work this way, which is a reviewer's question, not an implementer's. Do not render `acceptance` alongside `exitContract`: they restate each other
|
|
170
|
+
Do not render `sliceValue` — it argues why the plan sliced the work this way, which is a reviewer's question, not an implementer's. Do not render `acceptance` alongside `exitContract`: they restate each other, and `exitContract` is the superset. Sort `Verification Commands` `pre` → `mid` → `post` and introduce those three values above the table — source order interleaves them, and a reader working down the table would run a precondition after the checks it gates.
|
|
174
171
|
|
|
175
172
|
**The schedule has no risk section, no cross-task section and no next-actions list.** Every row those carried restated a stage: a risk's mitigation *is* the stage that answers it, an upstream dependency *is* the step that gates on it, and the next action *is* Stage 1's first step. Carry `dependencyMigrationRisk` and `crossProjectDependencies` by making sure the stage they point at says what they demand — and put anything genuinely not a stage (a freeze agreed with another team, a coupling the stages only imply) in that task's **Solution** or **Repo** cell.
|
|
176
173
|
|
|
@@ -178,7 +175,7 @@ Do not render `sliceValue` — it argues why the plan sliced the work this way,
|
|
|
178
175
|
|
|
179
176
|
### Step 5: Gantt decision (render by default)
|
|
180
177
|
|
|
181
|
-
`## Gantt Chart` is **rendered by default** — skip ONLY when literally no day signal exists (every in-scope task lacks both effort sizing and stage decomposition). An XXL task is not a skip reason: it is sized by its stages.
|
|
178
|
+
`## Gantt Chart` is **rendered by default** — skip ONLY when literally no day signal exists (every in-scope task lacks both effort sizing and stage decomposition). An XXL task is not a skip reason: it is sized by its stages. "Range is wide", "single task" and "user decisions pending" are not skip reasons.
|
|
182
179
|
|
|
183
180
|
When the source is a Stage Map, the Gantt bars are selected stages. A row is labelled `Stage <n>` when exactly one task is scheduled, and `<TASK-ID> Stage <n>` when more than one is. Spell the stage out — `S1` costs the reader a lookup and saves five characters. A row is a label and a bar and nothing else: no `days=` annotation (the Work Breakdown owns those numbers, and the validator compares the bar against that column), and no per-row `! crit` / `est` markers, which distinguish nothing when every row carries them. One line above the fence states the column unit and what `█` and `░` mean — that is the whole legend, because those two glyphs are the only notation left. Split the task effort range proportionally by `step_count`; round every stage except the last to 0.5 day and let the last stage absorb the remainder. Cross-stage dependency annotations follow `depends_on`. Already-done and non-selected stages never get a bar. A task tagged `[NEEDS-PLANNING]` contributes no bars.
|
|
184
181
|
|
|
@@ -190,7 +187,7 @@ When the source is a Stage Map, the Gantt bars are selected stages. A row is lab
|
|
|
190
187
|
|
|
191
188
|
An unrepresentable half-day allocation is a validation error. Do not switch to a fallback allocation algorithm or publish that draft.
|
|
192
189
|
|
|
193
|
-
When you do skip, insert in the section's position exactly: `> _Gantt Chart
|
|
190
|
+
When you do skip, insert in the section's position exactly: `> _Gantt Chart omitted: <concrete reason referencing the actual data>_`
|
|
194
191
|
|
|
195
192
|
**Directive override (highest priority).** Before applying the heuristic, check for a `## Directive` section, first hit wins: (1) the `--directive-file <abs-path>` argument; (2) `<PROJECT_ROOT>/.okstra/tasks/<task-group-segment>/schedule/instruction-set/analysis-material.md`; (3) none → apply the default heuristic silently. A found directive overrides the render/skip heuristic for the affected section — note it inline as `> _Per Directive directive: <verbatim short excerpt>._` — and its pre-supplied day allocations / phase weights are used verbatim as bar lengths. A directive file without a `## Directive` heading counts as "no directive".
|
|
196
193
|
|
|
@@ -282,7 +279,7 @@ Reached only after both Step 5.5 gates return `pass`. Promote the verified same
|
|
|
282
279
|
2. Run `python3 ~/.okstra/lib/validators/validate-schedule.py <output-path>` as a final format check; use the repository validator only when the installed validator is absent.
|
|
283
280
|
3. Delete the temporary `.selection.json` only after that final check passes. Do not print the Step 8 message while the selection contract still exists or validation is failing.
|
|
284
281
|
|
|
285
|
-
**Then read the document once as its reader.** The validator settles structure, arithmetic, controlled vocabulary and run-internal leakage; it cannot judge any of the following
|
|
282
|
+
**Then read the document once as its reader.** The validator settles structure, arithmetic, controlled vocabulary and run-internal leakage; it cannot judge any of the following:
|
|
286
283
|
|
|
287
284
|
- Does the summary say **why** the work happens and what is **true when it ends** — including what stays unfinished? A list of wins that omits a known limit is the kind a reader stops trusting at the first surprise.
|
|
288
285
|
- Does every step say what to **do**, or does some row only explain why the plan chose this shape? The second is the report's voice, not the schedule's.
|
|
@@ -312,7 +309,6 @@ Reached only after both Step 5.5 gates return `pass`. Promote the verified same
|
|
|
312
309
|
| ≤2 remaining stages | Emit only as many cumulative bundles as arise (1–2); a single chain skips the picker and proceeds with all |
|
|
313
310
|
| either validation gate still fails after two revisions | Final file not written; report residual findings to the user |
|
|
314
311
|
| `task-group` matches no tasks | "That task-group could not be found." and stop |
|
|
315
|
-
| Catalog and manifest disagree on `workStatus` | Manifest wins (catalog may be stale) |
|
|
316
312
|
| task-group casing / punctuation variants | `schedule-input` matches them: it lowercases the argument and the group part of each catalog task key and drops every non-alphanumeric character (Unicode letters and digits stay); use the Step 6 segment verbatim for path output |
|
|
317
313
|
|
|
318
314
|
## Output Rules
|
|
@@ -54,8 +54,7 @@ as the literal `<host-runtime>` value instead of detecting again at each step.
|
|
|
54
54
|
Replace `<host-runtime>` with the resolved literal value before executing each
|
|
55
55
|
command. Keep the same resolved host for installation, preflight, diagnostics,
|
|
56
56
|
and retries, including retries against another project or npm cache directory.
|
|
57
|
-
The runtime registry validates host IDs
|
|
58
|
-
by the former Python suite; that regression check is now retired.
|
|
57
|
+
The runtime registry validates host IDs.
|
|
59
58
|
|
|
60
59
|
```bash
|
|
61
60
|
npx -y okstra@latest install --runtime <host-runtime>
|
|
@@ -179,6 +178,8 @@ matching section:
|
|
|
179
178
|
- **F. declared architecture style** (`architecture.style`) — `hexagonal` /
|
|
180
179
|
`layered` / `none`; hand-added, default `none`. Declaring one makes that
|
|
181
180
|
architecture's placement rules binding in planning + verification.
|
|
181
|
+
- **G. review rule packs** (`reviewRulePacks`) — absolute paths to team review
|
|
182
|
+
standards every run reads; hand-added, checked by `okstra doctor --phase <phase>`.
|
|
182
183
|
- **H. MCP servers** (`mcpServers`) — `okstra mcp add` declares a server,
|
|
183
184
|
`okstra mcp check` shows which provider CLIs reach it.
|
|
184
185
|
|
|
@@ -140,10 +140,8 @@ and `validators/validate-run.py::_validate_conformance`.
|
|
|
140
140
|
`okstra setup` (and every `okstra run` prepare that is not render-only)
|
|
141
141
|
provisions `<PROJECT_ROOT>/.claude/settings.local.json` as a symlink to
|
|
142
142
|
`~/.okstra/templates/settings.local.json`. The template contains the Bash
|
|
143
|
-
permission rules
|
|
144
|
-
|
|
145
|
-
- `Bash($HOME/.okstra/bin/okstra-codex-exec.sh:*)`
|
|
146
|
-
- `Bash($HOME/.okstra/bin/okstra-antigravity-exec.sh:*)`
|
|
143
|
+
permission rules the worker wrappers need: `Bash($HOME/.okstra/bin/:*)` covers
|
|
144
|
+
every `okstra-*-exec.sh` wrapper, alongside the provider CLI rules.
|
|
147
145
|
|
|
148
146
|
Claude Code loads `.claude/settings.local.json` inside that project after the
|
|
149
147
|
project has been trusted. When setup creates this file during an already-open
|
|
@@ -0,0 +1,187 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: okstra-tdd
|
|
3
|
+
description: Guide one agent through requirements, independently reviewed specification and interfaces, RED tests, implementation and integration GREEN in one resumable Implementation Trace. Use when the user requests okstra-tdd or a single-session test-driven implementation record; resume a task registered by okstra-run through its trace path and task key; cross-verification runs use okstra-run.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# OKSTRA TDD
|
|
7
|
+
|
|
8
|
+
Keep one feature's analysis, review decisions, approvals and test evidence in one
|
|
9
|
+
Implementation Trace. `okstra trace` owns state transitions; this session writes
|
|
10
|
+
the Markdown body. One agent writes every section without a worker roster or run
|
|
11
|
+
lifecycle; review steps are judged by separate reviewer agents.
|
|
12
|
+
|
|
13
|
+
## Open an attempt
|
|
14
|
+
|
|
15
|
+
1. Resolve the target project from the user's request. Check for
|
|
16
|
+
`<project-root>/.okstra/project.json`. If absent, direct the user to
|
|
17
|
+
`okstra-setup` and stop.
|
|
18
|
+
2. Honor a task key and trace path passed by `okstra-run` or the user. Otherwise
|
|
19
|
+
read `projectId` from project configuration and use
|
|
20
|
+
`<project-id>:implementation:<slug>` for linked creation. Keep the same key
|
|
21
|
+
for a new attempt of the same task. Ask for a feature slug if the user has not supplied one. Use lowercase letters,
|
|
22
|
+
digits and single hyphens between words. Run from the project root:
|
|
23
|
+
|
|
24
|
+
```bash
|
|
25
|
+
okstra trace status --slug <slug>
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
3. On `TRACE_NOT_FOUND`, confirm the slug with the user, then run
|
|
29
|
+
`okstra trace new --slug <slug> --task-key <full-task-key> --project-root <project-root>`. If an attempt
|
|
30
|
+
exists, offer to resume that file or create a new attempt. Resume is the
|
|
31
|
+
recommendation; creating another attempt leaves earlier files unchanged.
|
|
32
|
+
If `new` reports an error, query `status --slug <slug>` before creating again:
|
|
33
|
+
cleanup can fail after a new attempt has been saved. If an attempt exists,
|
|
34
|
+
use the same resume-or-new choice and preserve earlier files. If status
|
|
35
|
+
returns `TRACE_NOT_FOUND`, repair the creation error before retrying. If status
|
|
36
|
+
itself fails otherwise, report the blocker and stop without changing files.
|
|
37
|
+
4. Read the returned `path`, including its body and JSON frontmatter. Preserve
|
|
38
|
+
the frontmatter and CLI-rendered evidence blocks when editing the body.
|
|
39
|
+
Write prose in its `language`; keep step headings, table keys and IDs fixed.
|
|
40
|
+
|
|
41
|
+
## Task registration and recovery
|
|
42
|
+
|
|
43
|
+
The linked task shares ordinary task history without a verification run. Supply
|
|
44
|
+
`--metadata <json-file>` on creation or advance to update `title`, `summary`,
|
|
45
|
+
`tags`, `changedFiles`, `references` and explicit `relatedTasks`. Before final
|
|
46
|
+
integration, record a functional summary and the actual changed file paths;
|
|
47
|
+
the test evidence summary is separate. These fields belong to the same task;
|
|
48
|
+
an attempt's task key cannot change. A new attempt retains earlier records and
|
|
49
|
+
starts with fresh approvals.
|
|
50
|
+
|
|
51
|
+
For an older unlinked trace, use
|
|
52
|
+
`okstra trace sync --path <file> --task-key <full-task-key> --metadata <json-file>`.
|
|
53
|
+
After `TASK_SYNC_FAILED`, the trace may already be saved. Read status and retry
|
|
54
|
+
`okstra trace sync --path <file>` until `taskSync` is `synced`; do not repeat an
|
|
55
|
+
already completed transition. Status reports `pending` without repairing state.
|
|
56
|
+
Report a completed trace with pending synchronization as such, rather than
|
|
57
|
+
claiming task history is current. CLI synchronization and regression tests
|
|
58
|
+
validate projection; the agent supplies truthful metadata and evidence.
|
|
59
|
+
|
|
60
|
+
## Follow the current action
|
|
61
|
+
|
|
62
|
+
After each operation, use the returned `currentStep` and `nextAction`. On resume,
|
|
63
|
+
call `status --path <file>` rather than reconstructing state from prose.
|
|
64
|
+
|
|
65
|
+
- `write`: complete the current section below, then call
|
|
66
|
+
`advance --path <file> --step <currentStep>`.
|
|
67
|
+
- `review`: run the step's [independent reviewers](#run-independent-reviewers)
|
|
68
|
+
and advance with `--review <completion>` for each verified completion. Use
|
|
69
|
+
approval mode instead only when the user asked to approve this step: present
|
|
70
|
+
the section and its review notes, wait for a chat reply, and advance with
|
|
71
|
+
`--verdict pass --approve "<verbatim user reply>"` only after explicit approval.
|
|
72
|
+
A requested revision is a failed review; advance with `--verdict fail`.
|
|
73
|
+
- `ask-user-decision`: show the three consecutive failed reviews and remaining
|
|
74
|
+
omissions. Wait for the user's choice to continue revising, narrow scope or
|
|
75
|
+
stop. Record the choice in the review section. For an authorized retry, finish
|
|
76
|
+
the current writing step and repeat its review once, using the actions for
|
|
77
|
+
those step IDs even while status still reports the failure streak. A passing
|
|
78
|
+
review resets the streak. If narrowing scope changes approved requirements,
|
|
79
|
+
confirm a new attempt with the user and preserve the existing attempt.
|
|
80
|
+
- `run-tests`: implement the current step's work, run the commands recorded in
|
|
81
|
+
`analysis`, and supply their actual evidence as described below.
|
|
82
|
+
- `done`: report the trace path, the passing integration result and any
|
|
83
|
+
explicitly unverified limitation. End the trace workflow.
|
|
84
|
+
|
|
85
|
+
Use `okstra trace advance --path <file> --step <id> [options]` for transitions.
|
|
86
|
+
After any failed `advance`, read its JSON error and call `status --path <file>`:
|
|
87
|
+
an error can occur after the state has been saved. Repair the input and retry
|
|
88
|
+
the original step only if status still names that step as `currentStep`. If the
|
|
89
|
+
step changed, follow the persisted `nextAction` instead. If status fails, report
|
|
90
|
+
the blocker and stop without changing state. Preserve approval waits and quote
|
|
91
|
+
provenance when following the persisted action; do not infer approval from an
|
|
92
|
+
earlier failed command or edit state to bypass a rejection.
|
|
93
|
+
|
|
94
|
+
## Section outcomes
|
|
95
|
+
|
|
96
|
+
| Step | Body outcome before advancing |
|
|
97
|
+
|---|---|
|
|
98
|
+
| `analysis` | Preserve the request; map every requirement to `R-NNN` with its source sentence. Fill the `Key` / `Value` table for `language`, `unitTestCommand`, `integrationTestCommand`, `typecheckCommand`. For languages without a type checker, use a command checking that tests import. |
|
|
99
|
+
| `analysis-review` | Reviewers compare every request sentence with the requirement list. Record each reviewer's omissions and verdict. |
|
|
100
|
+
| `spec` | Put each specification item in a `Spec item` / `Requirement` table and link it to existing R-IDs. |
|
|
101
|
+
| `spec-review` | Reviewers check for missing R-IDs, specification items lacking R-IDs, unauthorized scope and overdesign. Record their findings and verdicts. |
|
|
102
|
+
| `interface-design` | Record domain boundaries and public signatures. Add a `Use case` / `Requirement` table with `UC-NNN` IDs and each use case's R-IDs. |
|
|
103
|
+
| `interface-review` | Reviewers check that every R-ID has a use case and the boundaries and signatures serve those cases. Record their findings and verdicts. |
|
|
104
|
+
| `interface-code` | Write interface code, record code paths and pass type checking, compilation or the recorded import check. |
|
|
105
|
+
| `tests-red` | Write unit and integration tests. Record `Test` / `Use case` / `Kind` / `Path` rows, using `integration` for integration rows; every UC needs an integration test. Establish both unit and integration RED caused by missing implementation. |
|
|
106
|
+
| `implementation` | Implement the interfaces and reach unit GREEN. Record the integration result even when it remains RED. |
|
|
107
|
+
| `integration` | Reach integration GREEN for every use case. Record paths and results. |
|
|
108
|
+
|
|
109
|
+
All written artifacts stay in this trace; reference code and test files by path.
|
|
110
|
+
Follow the project's language and test tools rather than adding a new framework.
|
|
111
|
+
The CLI translates template guidance for `en` and `ko`; other language tags start
|
|
112
|
+
with structural markers only. Author their prose in the frontmatter language.
|
|
113
|
+
|
|
114
|
+
## Run independent reviewers
|
|
115
|
+
|
|
116
|
+
The writing session never judges its own section. For the current review step:
|
|
117
|
+
|
|
118
|
+
<!-- BEGIN FRAGMENT: host-runtime-selection -->
|
|
119
|
+
Resolve `<host-runtime>` from the launcher's `OKSTRA_RUNTIME_HOST` when present; otherwise use the registered host ID declared by the current harness. Do not infer the host from worker models, installed executables, or `PATH`. If neither source identifies the host, report that it is unknown instead of substituting another host. Keep the same resolved host when retrying against another project directory.
|
|
120
|
+
<!-- END FRAGMENT: host-runtime-selection -->
|
|
121
|
+
|
|
122
|
+
1. Run `okstra trace reviewers --path <file> --host-runtime <host-runtime>`.
|
|
123
|
+
Keep its `dutyId`, `roleId`, `binding`, `independence` and `slots`; do not
|
|
124
|
+
choose a provider, model or duty yourself. Pass `--count <n>` only when the
|
|
125
|
+
user asks for more reviewers.
|
|
126
|
+
2. For each slot, write
|
|
127
|
+
`<projectRoot>/.okstra/agent-invocations/trace-review/<invocation-id>.instructions.md`
|
|
128
|
+
with a unique invocation ID. Include the `binding` text verbatim, the request
|
|
129
|
+
and the sections the review compares (`analysis` for `analysis-review`;
|
|
130
|
+
`analysis` and `spec` for `spec-review`; `spec` and `interface-design` for
|
|
131
|
+
`interface-review`), the trace path, and the existing source paths the design
|
|
132
|
+
touches. Do not include the writing session's reasoning or a proposed verdict.
|
|
133
|
+
Ask for findings with evidence, then exactly one final line
|
|
134
|
+
`Trace review verdict: pass` or `Trace review verdict: fail`.
|
|
135
|
+
3. Materialize and verify the prompt, then run the slot's provider wrapper:
|
|
136
|
+
|
|
137
|
+
```bash
|
|
138
|
+
okstra agent-prompt materialize --project-root <projectRoot> --invocation-id <invocation-id> --host-runtime <host-runtime> --execution-runner cli-wrapper --provider <provider> --model <modelRef> --model-role <roleId> --audience <dutyId> --purpose trace-review --instruction <instructions-path> --prompt <projectRoot>/.okstra/agent-invocations/trace-review/<invocation-id>.prompt.md --json
|
|
139
|
+
okstra agent-prompt verify --project-root <projectRoot> --metadata <metadataPath> --text
|
|
140
|
+
~/.okstra/bin/okstra-<provider>-exec.sh <projectRoot> <modelExecutionValue> <prompt-path> "" <roleId> --invocation-metadata <metadataPath>
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
`metadataPath`, `promptPath` and `modelAssignment.modelExecutionValue` come
|
|
144
|
+
from the materialize output. A slot from the host's own provider still runs
|
|
145
|
+
through this wrapper, as a fresh process.
|
|
146
|
+
4. Capture the model's returned body under
|
|
147
|
+
`<projectRoot>/.okstra/agent-invocations/trace-review/.tmp/` from the wrapper
|
|
148
|
+
output only, then run `okstra agent-prompt materialize-result`, `complete` and
|
|
149
|
+
`verify-completion` with `--purpose trace-review`. Record each reviewer's
|
|
150
|
+
findings and verdict in the review section of the trace.
|
|
151
|
+
5. Advance with `--host-runtime <host-runtime>` and one
|
|
152
|
+
`--review <completion-path>` per reviewer. `REVIEW_STALE` means the prompt
|
|
153
|
+
lacks the current binding: the reviewed section, round, step, trace or host
|
|
154
|
+
changed after dispatch, or the binding was not copied verbatim. Review the
|
|
155
|
+
current text again under a new binding rather than editing the trace back.
|
|
156
|
+
`REVIEWER_NOT_INDEPENDENT` means a registered model from another provider was
|
|
157
|
+
skipped. A failed reviewer execution is retried once with a new invocation ID;
|
|
158
|
+
report a repeated failure as a blocker instead of judging the section yourself.
|
|
159
|
+
|
|
160
|
+
## Record evidence
|
|
161
|
+
|
|
162
|
+
Write an evidence JSON file containing one object or an array of objects:
|
|
163
|
+
|
|
164
|
+
```json
|
|
165
|
+
{
|
|
166
|
+
"kind": "unit",
|
|
167
|
+
"command": "npm run test:unit",
|
|
168
|
+
"exitCode": 1,
|
|
169
|
+
"summary": "Export is not implemented",
|
|
170
|
+
"failureCause": "not-implemented"
|
|
171
|
+
}
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
Use `typecheck`, `unit` or `integration` for `kind`. Include the executed command,
|
|
175
|
+
numeric exit code and nonempty result summary. RED failure causes are
|
|
176
|
+
`not-implemented`, `assertion`, `compile-error`, `import-error` or `other`.
|
|
177
|
+
Classify the observed failure; an import or compilation problem is not evidence
|
|
178
|
+
of missing implementation. The CLI supplies `recordedAt` and renders evidence
|
|
179
|
+
into the trace.
|
|
180
|
+
|
|
181
|
+
Advance with `--evidence <json-file>`. `interface-code` requires passing
|
|
182
|
+
`typecheck`; `tests-red` requires failing `unit` and `integration` entries both
|
|
183
|
+
classified `not-implemented`; `implementation` requires passing `unit`;
|
|
184
|
+
`integration` requires passing `integration`.
|
|
185
|
+
|
|
186
|
+
When a returned `commitPoint` is true, tell the user that this is a commit point.
|
|
187
|
+
This skill records that point only: it does not commit, push or create a PR.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: okstra-user-response
|
|
3
3
|
description: >-
|
|
4
|
-
Use
|
|
4
|
+
Use to answer an okstra task's open clarification questions, record an explicit plan decision, or pick the implementation direction a finished option comparison awaits, in-session, publishing the user-responses sidecar without hand-editing reports. NOT for starting a run, inspecting a finished task, or generating a brief.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# OKSTRA User Response
|
|
@@ -29,7 +29,9 @@ Do not use the automation-oriented `list` or `show` commands. Do not open a repo
|
|
|
29
29
|
|
|
30
30
|
## Step 0: Preflight
|
|
31
31
|
|
|
32
|
-
|
|
32
|
+
<!-- BEGIN FRAGMENT: host-runtime-selection -->
|
|
33
|
+
Resolve `<host-runtime>` from the launcher's `OKSTRA_RUNTIME_HOST` when present; otherwise use the registered host ID declared by the current harness. Do not infer the host from worker models, installed executables, or `PATH`. If neither source identifies the host, report that it is unknown instead of substituting another host. Keep the same resolved host when retrying against another project directory.
|
|
34
|
+
<!-- END FRAGMENT: host-runtime-selection -->
|
|
33
35
|
|
|
34
36
|
<!-- BEGIN FRAGMENT: bash-invocation-rule -->
|
|
35
37
|
Run one shell-command tool call, starting with the literal token `okstra` (never wrapped in `if`/`eval`/`export`/`$(...)`/`VAR=...`/`||`/`&&`/`npx` — literal command tokens keep execution permissions reviewable):
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
:root {
|
|
2
|
+
--bg: #f7f7f5;
|
|
3
|
+
--panel: #ffffff;
|
|
4
|
+
--text: #1f2328;
|
|
5
|
+
--muted: #5f6670;
|
|
6
|
+
--line: #d9dbde;
|
|
7
|
+
--accent: #0969da;
|
|
8
|
+
--current: #1a7f37;
|
|
9
|
+
--historical: #9a6700;
|
|
10
|
+
--unverified: #6e7781;
|
|
11
|
+
--call: #0969da;
|
|
12
|
+
--event: #8250df;
|
|
13
|
+
--queue: #bf3989;
|
|
14
|
+
--shared-data: #1a7f37;
|
|
15
|
+
--file: #9a6700;
|
|
16
|
+
--batch: #cf222e;
|
|
17
|
+
}
|
|
18
|
+
@media (prefers-color-scheme: dark) {
|
|
19
|
+
:root {
|
|
20
|
+
--bg: #111418;
|
|
21
|
+
--panel: #1a1f25;
|
|
22
|
+
--text: #e6e8eb;
|
|
23
|
+
--muted: #9aa3ad;
|
|
24
|
+
--line: #2f363e;
|
|
25
|
+
--accent: #58a6ff;
|
|
26
|
+
--current: #3fb950;
|
|
27
|
+
--historical: #d29922;
|
|
28
|
+
--unverified: #8b949e;
|
|
29
|
+
--call: #58a6ff;
|
|
30
|
+
--event: #a371f7;
|
|
31
|
+
--queue: #db61a2;
|
|
32
|
+
--shared-data: #3fb950;
|
|
33
|
+
--file: #d29922;
|
|
34
|
+
--batch: #f85149;
|
|
35
|
+
}
|
|
36
|
+
}
|
|
37
|
+
* { box-sizing: border-box; }
|
|
38
|
+
body {
|
|
39
|
+
margin: 0;
|
|
40
|
+
background: var(--bg);
|
|
41
|
+
color: var(--text);
|
|
42
|
+
font: 14px/1.55 -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
|
|
43
|
+
}
|
|
44
|
+
main { max-width: 1200px; margin: 0 auto; padding: 24px 16px 48px; }
|
|
45
|
+
header h1 { margin: 0 0 4px; font-size: 22px; }
|
|
46
|
+
.meta { color: var(--muted); font-size: 13px; }
|
|
47
|
+
.hint { color: var(--muted); font-size: 13px; margin: 0 0 10px; }
|
|
48
|
+
.empty { color: var(--muted); }
|
|
49
|
+
section { margin-top: 28px; }
|
|
50
|
+
h2 { font-size: 17px; margin: 0 0 10px; }
|
|
51
|
+
h3 { font-size: 14px; margin: 14px 0 6px; }
|
|
52
|
+
.panel { background: var(--panel); border: 1px solid var(--line); border-radius: 8px; padding: 12px; }
|
|
53
|
+
.scroll { overflow-x: auto; }
|
|
54
|
+
table { width: 100%; border-collapse: collapse; }
|
|
55
|
+
th, td { text-align: left; padding: 7px 10px; border-bottom: 1px solid var(--line); vertical-align: top; }
|
|
56
|
+
th { color: var(--muted); font-weight: 600; font-size: 12px; white-space: nowrap; }
|
|
57
|
+
code { font: 12px/1.4 ui-monospace, SFMono-Regular, Menlo, monospace; overflow-wrap: anywhere; }
|
|
58
|
+
ul.plain { margin: 0; padding-left: 18px; }
|
|
59
|
+
|
|
60
|
+
.graph svg { width: 100%; height: auto; display: block; }
|
|
61
|
+
.graph .node circle { fill: var(--panel); stroke: var(--text); stroke-width: 1.5; cursor: pointer; }
|
|
62
|
+
.graph .node.outside circle { stroke-dasharray: 3 3; stroke: var(--muted); }
|
|
63
|
+
.graph .node.uninvestigated circle { fill: var(--bg); }
|
|
64
|
+
.graph .node.selected circle { stroke: var(--accent); stroke-width: 3; }
|
|
65
|
+
.graph .node text { fill: var(--text); font-size: 12px; text-anchor: middle; pointer-events: none; }
|
|
66
|
+
.graph .edge { fill: none; stroke-width: 1.8; cursor: pointer; }
|
|
67
|
+
.graph .edge.candidate { stroke-dasharray: 5 4; }
|
|
68
|
+
.graph .edge.dimmed { opacity: 0.15; }
|
|
69
|
+
.graph .edge.call, .legend .call { stroke: var(--call); color: var(--call); }
|
|
70
|
+
.graph .edge.event, .legend .event { stroke: var(--event); color: var(--event); }
|
|
71
|
+
.graph .edge.queue, .legend .queue { stroke: var(--queue); color: var(--queue); }
|
|
72
|
+
.graph .edge.shared-data, .legend .shared-data { stroke: var(--shared-data); color: var(--shared-data); }
|
|
73
|
+
.graph .edge.file, .legend .file { stroke: var(--file); color: var(--file); }
|
|
74
|
+
.graph .edge.batch, .legend .batch { stroke: var(--batch); color: var(--batch); }
|
|
75
|
+
.legend { list-style: none; display: flex; flex-wrap: wrap; gap: 6px 16px; margin: 10px 0 0; padding: 0; font-size: 12px; }
|
|
76
|
+
.legend li::before { content: "━ "; }
|
|
77
|
+
|
|
78
|
+
.filters { display: flex; flex-wrap: wrap; gap: 10px 16px; align-items: center; margin-bottom: 12px; }
|
|
79
|
+
.filters input, .filters select {
|
|
80
|
+
font: inherit; color: var(--text); background: var(--panel);
|
|
81
|
+
border: 1px solid var(--line); border-radius: 6px; padding: 5px 8px;
|
|
82
|
+
}
|
|
83
|
+
.filters input { min-width: 280px; }
|
|
84
|
+
|
|
85
|
+
details.flow { background: var(--panel); border: 1px solid var(--line); border-radius: 8px; margin-bottom: 10px; }
|
|
86
|
+
details.flow > summary { cursor: pointer; padding: 10px 12px; display: flex; flex-wrap: wrap; gap: 6px 10px; align-items: baseline; }
|
|
87
|
+
details.flow > summary .name { font-weight: 600; }
|
|
88
|
+
details.flow > .body { padding: 0 14px 14px; border-top: 1px solid var(--line); }
|
|
89
|
+
.chip { border: 1px solid currentColor; border-radius: 999px; padding: 0 8px; font-size: 12px; white-space: nowrap; }
|
|
90
|
+
.chip.current { color: var(--current); }
|
|
91
|
+
.chip.historical { color: var(--historical); }
|
|
92
|
+
.chip.unverified, .chip.partial { color: var(--unverified); }
|
|
93
|
+
.chip.complete { color: var(--muted); }
|
|
94
|
+
ol.steps { margin: 0; padding-left: 20px; }
|
|
95
|
+
ol.steps > li { margin-bottom: 12px; }
|
|
96
|
+
ol.steps .step-title { font-weight: 600; }
|
|
97
|
+
dl.fields { display: grid; grid-template-columns: max-content minmax(0, 1fr); gap: 2px 12px; margin: 6px 0 0; font-size: 13px; }
|
|
98
|
+
dl.fields dt { color: var(--muted); }
|
|
99
|
+
dl.fields dd { margin: 0; }
|
|
100
|
+
dl.terms dt { font-weight: 600; margin-top: 6px; }
|
|
101
|
+
dl.terms dd { margin: 0; }
|
|
102
|
+
ul.facts { margin: 0; padding-left: 18px; }
|
|
103
|
+
ul.facts li { margin-bottom: 6px; }
|