chore(repo): checkpoint current capakraken implementation state

docs/estimating-extension-design.md

@@ -2,7 +2,7 @@
 
 **Date:** 2026-03-13
 **Related workbook:** `samples/CGIBreakdown_Template/Template_CGI-Breakdown+Calc_25Dez_V0.976_251212_beta_LCR-Update.xlsx`
-**Purpose:** Canonical design, field mapping, and implementation plan for a browser-based estimating system in Planarchy.
+**Purpose:** Canonical design, field mapping, and implementation plan for a browser-based estimating system in CapaKraken.
 
 ## Executive Summary
 
@@ -15,12 +15,12 @@ The workbook is not a simple calculator. It is a full estimating and pricing sys
 - management summaries
 - downstream export sheets
 
-Planarchy can support this, but not by copying Excel cell logic into the browser. The right implementation is a dedicated estimating bounded context with:
+CapaKraken can support this, but not by copying Excel cell logic into the browser. The right implementation is a dedicated estimating bounded context with:
 
 - a wizard for first-pass estimate creation
 - a workspace for iterative revisions
 - a typed calculation pipeline
-- live linkage to Planarchy resources and roles
+- live linkage to CapaKraken resources and roles
 - immutable snapshots for auditability
 
 ## Design Principles
@@ -39,7 +39,7 @@ The replacement should be:
 
 ### 2. Reuse the current platform where it already fits
 
-Useful existing Planarchy primitives:
+Useful existing CapaKraken primitives:
 
 - `Resource` for roster, rates, skills, availability, and dynamic metadata
 - `Project` for schedule, budget, and project linkage
@@ -134,7 +134,7 @@ That mix is exactly why the app needs separated models for assumptions, scope, d
 
 ### Mapping legend
 
-- `Direct`: already maps to an existing first-class Planarchy field
+- `Direct`: already maps to an existing first-class CapaKraken field
 - `Bridge`: can be bridged short-term, but should move to estimating models
 - `Derived`: calculate it, do not persist it as manual source data
 - `New Model`: requires estimating schema
@@ -236,7 +236,7 @@ That prevents old approved estimates from changing when roster rates or metadata
 ### Phase 4. Resource linkage and planning handoff
 
 - connect demand lines to resources, roles, and availability
-- add staffing suggestions from current Planarchy data
+- add staffing suggestions from current CapaKraken data
 - support conversion from approved estimate demand into downstream planning entities
 
 ### Phase 5. Exports and approvals
@@ -261,7 +261,7 @@ Implemented baseline in the current codebase:
 - version submit, approve, and locked revision-cloning actions
 - export artifact scaffolding with stored serializer metadata records
 - format-specific export generation with stored payloads for JSON, CSV, XLSX, SAP, and MMP
-- live resource-linked staffing rows that can sync current Planarchy rates and persist estimate-version snapshots
+- live resource-linked staffing rows that can sync current CapaKraken rates and persist estimate-version snapshots
 - explicit live-vs-manual rate mode metadata on demand lines, with server-side recalculation before metrics are persisted
 - read-only and draft workspace visibility for manual overrides versus live resource snapshots
 - project snapshot persistence on estimate versions