chore(repo): checkpoint current capakraken implementation state

2026-03-29 12:47:12 +02:00
parent beae1a5d6e
commit 47e4d701ff
94 changed files with 4283 additions and 1710 deletions
@@ -35,7 +35,7 @@ Define the contracts that remove field and widget drift before implementation st
 ## Agent Prompt

 ```text
-You are A1, the architect for the Planarchy widget + field refactor sprint.
+You are A1, the architect for the CapaKraken widget + field refactor sprint.

 Your job is to define stable contracts before implementation starts. Focus on the field-definition model and the widget-config/layout versioning model.

@@ -33,7 +33,7 @@ Centralize dynamic-field validation and filter construction so project and resou
 ## Agent Prompt

 ```text
-You are C1, the field domain coder for the Planarchy refactor sprint.
+You are C1, the field domain coder for the CapaKraken refactor sprint.

 Implement the shared dynamic-field validation and filter-building path defined by A1. Your target is parity between project and resource handling with duplicated logic removed from routers.

@@ -33,7 +33,7 @@ Align blueprint and dynamic-field UI to the canonical field contract so UI behav
 ## Agent Prompt

 ```text
-You are C2, the blueprint UI coder for the Planarchy refactor sprint.
+You are C2, the blueprint UI coder for the CapaKraken refactor sprint.

 Update the blueprint field editor and dynamic-field UI to use the canonical field-definition contract. Remove UI-only assumptions and align rendering and filtering behavior with the shared schema.

@@ -34,7 +34,7 @@ Make dashboard widget persistence typed and versioned, then move rendering towar
 ## Agent Prompt

 ```text
-You are C3, the widget platform coder for the Planarchy refactor sprint.
+You are C3, the widget platform coder for the CapaKraken refactor sprint.

 Implement the widget-config and layout-versioning contract from A1, then move dashboard rendering toward a registry-driven model.

@@ -30,7 +30,7 @@ Thin the dashboard router and prepare the path to SQL-first performance work.
 ## Agent Prompt

 ```text
-You are C4, the dashboard data coder for the Planarchy refactor sprint.
+You are C4, the dashboard data coder for the CapaKraken refactor sprint.

 Extract dashboard data assembly out of the router, reduce JS-side aggregation complexity where feasible, and document the next sprint's SQL-first rewrite path.

@@ -24,7 +24,7 @@ Claude Flow does not expose an `orchestrator` agent type in the CLI. The sprint

 - `O1` orchestrator role -> CLI `coordinator` type

-The role behavior still comes from [O1-orchestrator.md](/home/hartmut/Documents/Copilot/planarchy/.agents/sprints/widget-field-refactor/O1-orchestrator.md), which explicitly forbids implementation work.
+The role behavior still comes from [O1-orchestrator.md](/home/hartmut/Documents/Copilot/capakraken/.agents/sprints/widget-field-refactor/O1-orchestrator.md), which explicitly forbids implementation work.

 ## Azure Requirement

@@ -35,7 +35,7 @@ This launcher is intended to run against Azure OpenAI-backed Codex. It will fail
 - the config references `AZURE_OPENAI_API_KEY`
 - `AZURE_OPENAI_API_KEY` is present in the shell environment

-See [docs/azure_codex_setup.md](/home/hartmut/Documents/Copilot/planarchy/docs/azure_codex_setup.md).
+See [docs/azure_codex_setup.md](/home/hartmut/Documents/Copilot/capakraken/docs/azure_codex_setup.md).

 ## Start

@@ -111,7 +111,7 @@ Do not accept a story unless all are true:
 ## Orchestrator Prompt

 ```text
-You are O1, the sprint orchestrator for the Planarchy widget + field refactor.
+You are O1, the sprint orchestrator for the CapaKraken widget + field refactor.

 You never implement. You do not patch files, write tests, fix lint errors, or edit migrations. Your job is to sequence work, issue precise tickets, review handoffs against acceptance criteria, control merge order, and escalate blockers.

@@ -33,7 +33,7 @@ Review every merge candidate for regressions, contract drift, and unsafe persist
 ## Agent Prompt

 ```text
-You are R1, the reviewer for the Planarchy refactor sprint.
+You are R1, the reviewer for the CapaKraken refactor sprint.

 Review every merge candidate with a regression-first mindset. Prioritize correctness, contract discipline, persistence safety, and behavior parity across project/resource flows.

@@ -35,7 +35,7 @@ Add the regression and integration tests that make this refactor safe to land.
 ## Agent Prompt

 ```text
-You are T1, the test agent for the Planarchy refactor sprint.
+You are T1, the test agent for the CapaKraken refactor sprint.

 Your role is to add the minimum set of high-value tests that make the refactor safe. Prioritize contracts, parity, persistence, and migration behavior over broad test volume.