From b0231fdef7a1ee2e4b402861a3a9f21bdc8da611 Mon Sep 17 00:00:00 2001 From: Kjell Tore Guttormsen Date: Tue, 5 May 2026 11:17:00 +0200 Subject: [PATCH] =?UTF-8?q?docs(ultraplan-local):=20D5=20close-out=20?= =?UTF-8?q?=E2=80=94=20repo=20cleanup=20pre-voyage-rebrand=20[skip-docs]?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit D5 — final session of post-v3.4.1 stabilisering. Repo prepared for the upcoming voyage-rebrand (v4.0.0 hard cut: ultraplan-local → voyage, /ultra*-local → /trek*). Tracked changes: - README.md: cut #9 jargon — '### Self-verifying plan chain' → '### Manifest-verified steps' with body rewritten to drop the 'objective completion predicate' jargon. - package.json: removed 'simulate' script that pointed to tests/simulator/run-pipeline.mjs (file never existed; D3 was dropped before that work shipped). - .claude-plugin/marketplace.json: ultraplan-local description updated from 'Four-command pipeline' to the current six-command shape with Handover 6 + multi-session resumption (matches plugin.json). - docs/_archive-ultra-suite-brief_2.md: deleted (tracked planning-doc unrelated to ultraplan-local; 117 lines, no inbound references). Untracked cleanup (not in commit, gitignored): - 4 stale plugin-root .local.md (NEXT-SESSION-PROMPT.archived, PLAN-v2.1-phase3, V3.0-MULTI-SESSION-PLAN, etc.) - 3 docs/ planning .local.md (ultracontinue-brief, ultracontinue-design-notes, ultraexecute-v2-observations) - examples/01-add-verbose-flag/perf-baseline.local.md - .claude/plans/ultraplan-2026-04-17-logger.md - 9 closed sub-projects under .claude/projects/ (skill-factory, ultracontinue, ultrareview-local, ultra-pipeline-speedup, examples-02-real-cli, post-v3.4.0-roadmap, spor-c-q3-cache, v3.3.1-ultracontinue-fixes) Cuts #7 (template-duplisering) + #10 (Two kinds of briefs) reviewed and judged not needed: README has 38 code-fences vs CLAUDE.md 2 (no overlap), and 'Two kinds of briefs' is already a direct task-vs- research-brief explanation, not jargon. D3 + D4 droppet 2026-05-05 — voyage-rebrand renames all ultra* references; new test infrastructure built against the old names would need to be renamed in the same pass. Memory pin: feedback_cleanup_vs_new_code.md. Tests: 361 / 0 (unchanged — no test changes). Stabilisering close-out: complete. Repo is ready for voyage-rebrand. --- .claude-plugin/marketplace.json | 2 +- plugins/ultraplan-local/README.md | 4 +- .../docs/_archive-ultra-suite-brief_2.md | 118 ------------------ plugins/ultraplan-local/package.json | 3 +- 4 files changed, 4 insertions(+), 123 deletions(-) delete mode 100644 plugins/ultraplan-local/docs/_archive-ultra-suite-brief_2.md diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index ae9680d..e141648 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -23,7 +23,7 @@ { "name": "ultraplan-local", "source": "./plugins/ultraplan-local", - "description": "Four-command context-engineering pipeline (brief → research → plan → execute) with specialized agent swarms, external research triangulation, adversarial review, session decomposition, and headless execution" + "description": "Six-command context-engineering pipeline (brief → research → plan → execute → review → continue) with specialized agent swarms, external research triangulation, adversarial review, post-hoc independent review with Handover 6 feedback loop, multi-session resumption, session decomposition, and headless execution" }, { "name": "linkedin-thought-leadership", diff --git a/plugins/ultraplan-local/README.md b/plugins/ultraplan-local/README.md index ebdfb04..31707c9 100644 --- a/plugins/ultraplan-local/README.md +++ b/plugins/ultraplan-local/README.md @@ -41,9 +41,9 @@ Terminology matters: A project typically has one task brief and zero-to-N research briefs. -### Self-verifying plan chain +### Manifest-verified steps -Every step in the plan ends with a YAML `manifest:` block declaring `expected_paths`, `commit_message_pattern`, `bash_syntax_check`, `forbidden_paths`, `must_contain`. This makes the plan the **objective completion predicate**: a step may not be marked passed if its manifest does not verify, regardless of the Verify command's exit code (Hard Rule 17). +Every step in the plan ends with a YAML `manifest:` block declaring `expected_paths`, `commit_message_pattern`, `bash_syntax_check`, `forbidden_paths`, `must_contain`. The executor checks the manifest against the resulting commit — a step may not be marked passed if its manifest does not verify, regardless of the Verify command's exit code (Hard Rule 17). After all steps complete, `/ultraexecute-local` runs **Phase 7.5 — Manifest audit (independent)**: re-verifies every expected path from git log + filesystem, ignoring the agent's own bookkeeping. Drift → status `partial`, **Phase 7.6** auto-dispatches a bounded recovery session with only the missing steps (`recovery_depth ≤ 2`). Step 0 pre-flight (`git push --dry-run`) runs inside every session sandbox before any real work — exit 77 sentinel catches sandbox push-denial before the agent wastes the whole budget. diff --git a/plugins/ultraplan-local/docs/_archive-ultra-suite-brief_2.md b/plugins/ultraplan-local/docs/_archive-ultra-suite-brief_2.md deleted file mode 100644 index 8445bc2..0000000 --- a/plugins/ultraplan-local/docs/_archive-ultra-suite-brief_2.md +++ /dev/null @@ -1,118 +0,0 @@ -Kontekst: Harness-plugin (../harness/) er nettopp oppgradert til v13.0.0 (commit - 8a444f5 på main). Kiur (v5.4.0) er søster-plugin — harness orkestrerer hvilke - features som bygges, Kiur håndhever kvalitet via TDD + multi-agent review. Kiur - dispatches fra harness for L1/L2 features (kiur:tdd + kiur:done), så konvensjonene - må holdes i sync. - - Oppgave: Moderniser Kiur til å matche: - 1. Harness v13.0.0 konvensjoner - 2. Opus 4.7 (ny modell — claude-opus-4-7, extended reasoning) - 3. Nyere Claude Code features (2.1.x+) - - Viktig: IKKE implementer ennå. Les kontekst, foreslå en plan med prioritert - oppgaveliste + begrunnelse, vent på min godkjenning. - - ### Fase 1 — Les kontekst (obligatorisk før planlegging) - - Les disse filene i sin helhet: - - ../harness/CLAUDE.md (v13.0 konvensjoner, spesielt model.strategy, review gates, 3 - nye hooks) - - ../harness/README.md (seksjonene "Review Gates", "Review Triad (v13.0)", "Version - History v13.0.0") - - ../harness/lib/config.mjs (se model.strategy og enforce-mønsteret) - - ../harness/agents/plan-critic-agent.md (adversarial review-pattern) - - ../harness/agents/scope-guardian-agent.md (coverage matrix-pattern) - - ../harness/hooks/scripts/subagent-stop-validate.mjs (verification_manifest gate) - - ../harness/hooks/scripts/pre-compact-snapshot.mjs (state preservation) - - ../harness/hooks/hooks.json (SessionEnd/SubagentStop/PreCompact wiring) - - Fra Kiur selv: - - CLAUDE.md, README.md, CHANGELOG.md - - .claude-plugin/plugin.json (nåværende versjon, manglende - compatibleClaudeCodeVersions) - - Alle 6 agent-filer (agents/*.md) — noter modeller i frontmatter - - Alle 8 commands (commands/*.md) — spesielt tdd.md, review.md, done.md - - Alle 4 hook-scripter (hooks/scripts/*.mjs) - - ### Fase 2 — Dimensjoner å vurdere - - A) **Opus 4.7-tilpasning** - - Hvilke agenter ville ha nytte av ny extended reasoning? (Default: dype - planleggings-/review-agenter → opus, implementerings-/formatterings-agenter → - sonnet) - - Konkret: red-team-agent, security-auditor-agent, accessibility-auditor-agent, - spec-reviewer-agent er plausible opus-kandidater. implementer-agent, - tdd-test-first-agent er plausible sonnet-kandidater. Vurder per agent. - - Sjekk om frontmatter bruker korrekt modellidentifikator (sonnet/opus som alias, - ikke hardkodet "claude-3.5-sonnet" eller lignende utdaterte navn). - - B) **Harness v13 paritet** - - **Centralized model strategy:** Innfør `model.strategy` i Kiur-config med - per-role defaults (tdd_implementer, tdd_test_first, reviewer_default, red_team, - security, accessibility, spec_reviewer). Dette lar harness override Kiur-dispatch - uten å redigere agent-filer. - - **Compatibility declaration:** Legg til `compatibleClaudeCodeVersions: { - minimum: "2.1.0" }` i plugin.json. - - **SubagentStop validation:** Kiur dispatcher mange subagenter (Agent Teams for - L2). Vurder en analog subagent-stop-validate.mjs som sjekker at review-agenter - produserte strukturert output (f.eks. JSON-verdict) før Stop-event propageres. - - **PreCompact snapshot:** Kiurs WORKFLOW_STATE.json kan tape progresjon ved - context compaction midt i RED/GREEN/REFACTOR. Vurder en pre-compact-snapshot.mjs som - lagrer TDD-fase + failing test count. - - **SessionEnd archive:** Kiur skriver ikke event-log på samme måte som harness, - men vurder om review-db (hvis den finnes) eller andre JSONL-stater trenger - gzip-arkivering. - - C) **Claude Code 2.1.x changelog-relevante features** - - **Agent isolation: "worktree"** — Agent-tool støtter nå worktree-isolering. - Relevant for red-team-agent som gjør eksperimentelle endringer. - - **Dynamic /loop og ScheduleWakeup** — Ikke direkte relevant for Kiur (harness - eier loop), men Kiur kan eksponere hooks/events som /loop-integrasjoner kan lytte - på. - - **TaskCreate/TaskUpdate med blocks/blockedBy** — Mulig bruk i kiur:done for å - eksponere Definition of Done-sjekkpunkter som tracked tasks. - - **Monitor tool** — For å streame output fra langvarige test-kjøringer uten å - blokkere. Vurder i tdd-pipelinen ved store test-suites. - - **SendMessage mellom agenter** — Kan forenkle feedback-loop mellom - tdd-test-first-agent og implementer-agent i Agent Teams-mode. - - **PreCompact / SessionEnd / SubagentStop hook-events** — Allerede dekket i del - B. - - **Skill tool vs direct invocation** — Hvis Kiur har skills, sjekk at de følger - progressive disclosure-mønsteret (kompakt SKILL.md + references/). - - D) **Kiur-spesifikke forbedringer inspirert av harness** - - **Adversarial pattern:** Harness' plan-critic-agent er en NO-PLACEHOLDER-streng - adversarial reviewer. Vurder analog for Kiur: en "test-critic-agent" som motbeviser - at tester faktisk tester noe meningsfullt (f.eks. sjekker for tautologiske asserts, - mocks som ikke verifiserer noe, manglende edge cases). Dette forsterker Iron Law. - - **Enforce-gating:** Innfør `red_team.enforce`, `security.enforce`, - `accessibility.enforce` i config — default warn, kan settes til block for kritiske - prosjekter. - - ### Fase 3 — Leveranse - - Gi meg tilbake: - 1. **Oppgaveliste** — nummerert, prioritert (P0/P1/P2), med konkret acceptance - criteria per oppgave. - 2. **Scope-fence** — hva som IKKE gjøres i denne omgangen (f.eks. full rewrite av - Agent Teams-orkestrering). - 3. **Versjonsforslag** — v5.5.0 (minor) vs v6.0.0 (major). Begrunn basert på - breaking changes. - 4. **Risikovurdering** — hva kan gå galt når harness v13 dispatcher til Kiur vN - etter disse endringene? - 5. **Testforslag** — hvilke nye unit/integration-tester trengs for å verifisere - paritet med harness-konvensjoner? - 6. **Rekkefølge** — hvilken av A/B/C/D bør gjøres først? (Min intuisjon: B før A før - D før C, men overbevis meg.) - - ### Constraints - - - Arbeid KUN i ../kiur/. Ikke rør harness, andre plugins, eller marketplace.json. - - Alle hooks skal være .mjs (cross-platform, ingen bash-avhengigheter utover det som - allerede finnes). - - Følg plugin-konvensjonen i ../CLAUDE.md (plugins/ktg-privat CLAUDE.md). - - Bash 3.2-kompatibilitet for eventuelle shell-templates. - - Aldri bruk `claude-3.5-sonnet` eller `claude-3-opus` i frontmatter — bruk alias - `sonnet` / `opus` / `haiku` som plugin-arkitekturen forstår. - - Start med Fase 1 (les kontekst). Rapporter når klar for Fase 3. \ No newline at end of file diff --git a/plugins/ultraplan-local/package.json b/plugins/ultraplan-local/package.json index bdce4e6..e62794d 100644 --- a/plugins/ultraplan-local/package.json +++ b/plugins/ultraplan-local/package.json @@ -7,8 +7,7 @@ "node": ">=18" }, "scripts": { - "test": "node --test 'tests/**/*.test.mjs'", - "simulate": "node tests/simulator/run-pipeline.mjs" + "test": "node --test 'tests/**/*.test.mjs'" }, "keywords": [ "claude-code",