@tgoodington/intuition 11.5.0 → 11.6.0

package/docs/project_notes/archive/trunk-v9.2-complete/team_assignment.json

@@ -1,108 +0,0 @@
-{
-  "specialist_assignments": [
-    {
-      "specialist": "devops-infrastructure",
-      "tasks": [
-        {"task_id": "T1", "depth": "Light"},
-        {"task_id": "T6", "depth": "Light"},
-        {"task_id": "T8", "depth": "Standard"}
-      ],
-      "rationale": "Closest match for code/tooling tasks (T1, T6) via scripting/CI/deployment domain overlap, and code/testing verification sweep (T8) via CI/CD monitoring expertise."
-    },
-    {
-      "specialist": "technical-writer",
-      "tasks": [
-        {"task_id": "T2", "depth": "Standard"},
-        {"task_id": "T4", "depth": "Light"},
-        {"task_id": "T5", "depth": "Standard"},
-        {"task_id": "T7", "depth": "Standard"}
-      ],
-      "rationale": "Matched T7 (content/documentation) by domain_tags. T2, T4, T5 assigned as closest match — SKILL.md files are structured markdown requiring systematic disambiguation, which aligns with technical writing precision."
-    },
-    {
-      "specialist": "database-architect",
-      "tasks": [
-        {"task_id": "T3", "depth": "Deep"}
-      ],
-      "rationale": "Closest match for T3 (v7→v8 migration handler) via explicit 'migrations' and 'schema' domain_tags. JSON state schema migration pattern aligns with core database-architect competency."
-    }
-  ],
-  "producer_assignments": [
-    {
-      "specialist": "technical-writer",
-      "producer": "document-writer",
-      "output_format": "markdown",
-      "tasks_output_files": [
-        "docs/project_notes/trunk/blueprints/T2-outline-skill.md",
-        "docs/project_notes/trunk/blueprints/T4-initialize-template.md",
-        "docs/project_notes/trunk/blueprints/T5-other-skills.md",
-        "docs/project_notes/trunk/blueprints/T7-documentation.md"
-      ]
-    },
-    {
-      "specialist": "devops-infrastructure",
-      "producer": "code-writer",
-      "output_format": "code",
-      "tasks_output_files": [
-        "docs/project_notes/trunk/blueprints/T1-audit.md",
-        "docs/project_notes/trunk/blueprints/T6-scripts.md",
-        "docs/project_notes/trunk/blueprints/T8-verification.md"
-      ]
-    },
-    {
-      "specialist": "database-architect",
-      "producer": "code-writer",
-      "output_format": "code",
-      "tasks_output_files": [
-        "docs/project_notes/trunk/blueprints/T3-handoff-migration.md"
-      ]
-    }
-  ],
-  "execution_order": [
-    {
-      "phase": 1,
-      "specialists": ["devops-infrastructure"],
-      "rationale": "T1 (audit) has no dependencies and must complete first to produce the reference checklist for all subsequent tasks."
-    },
-    {
-      "phase": 2,
-      "specialists": ["technical-writer", "database-architect"],
-      "rationale": "T2, T5, T7 (technical-writer) and T3 (database-architect) all depend on T1 and can run in parallel after the audit is complete."
-    },
-    {
-      "phase": 3,
-      "specialists": ["technical-writer", "devops-infrastructure"],
-      "rationale": "T4 (technical-writer, depends on T3) and T6 (devops-infrastructure, depends on T2) run in parallel after Phase 2 completes."
-    },
-    {
-      "phase": 4,
-      "specialists": ["devops-infrastructure"],
-      "rationale": "T8 verification sweep depends on all prior tasks being complete."
-    }
-  ],
-  "dependencies": [
-    {
-      "specialist": "technical-writer",
-      "reads_blueprint_from": "database-architect",
-      "reason": "T4 (initialize template) depends on T3 (handoff migration) to know the final v8.0 state schema field names before updating the template."
-    },
-    {
-      "specialist": "devops-infrastructure",
-      "reads_blueprint_from": "technical-writer",
-      "reason": "T6 (scripts) depends on T2 (rename outline skill folder) being complete before updating the install script skill list."
-    }
-  ],
-  "unmatched_tasks": [
-    {"task_id": "T1", "title": "Audit all phase-name references", "domain": "code/tooling", "reason": "No specialist has 'tooling' in domain_tags. Assigned to devops-infrastructure (closest: scripting/CI overlap)."},
-    {"task_id": "T2", "title": "Rename and update outline skill", "domain": "code/skill-definition", "reason": "No specialist has 'skill-definition' in domain_tags. Assigned to technical-writer (closest: structured markdown editing)."},
-    {"task_id": "T3", "title": "Update handoff with v7->v8 migration", "domain": "code/skill-definition", "reason": "No specialist has 'skill-definition' in domain_tags. Assigned to database-architect (closest: migrations/schema tags)."},
-    {"task_id": "T4", "title": "Update initialize skill template", "domain": "code/skill-definition", "reason": "No specialist has 'skill-definition' in domain_tags. Assigned to technical-writer (closest: Light task, structured markdown)."},
-    {"task_id": "T5", "title": "Update all other skills (9 files)", "domain": "code/skill-definition", "reason": "No specialist has 'skill-definition' in domain_tags. Assigned to technical-writer (closest: structured markdown editing)."},
-    {"task_id": "T6", "title": "Update scripts and package config", "domain": "code/tooling", "reason": "No specialist has 'tooling' in domain_tags. Assigned to devops-infrastructure (closest: deploy scripts/CI overlap)."},
-    {"task_id": "T8", "title": "Verification sweep", "domain": "code/testing", "reason": "No specialist has 'testing' in domain_tags. Assigned to devops-infrastructure (closest: CI/CD monitoring/verification)."}
-  ],
-  "prerequisite_check": {
-    "document-writer/markdown": "PASS — no required tools",
-    "code-writer/code": "PASS — no required tools"
-  }
-}

package/docs/project_notes/archive/trunk-v9.2-complete/test_brief.md

@@ -1,75 +0,0 @@
-# Test Brief
-
-## Build Summary
-- **Status**: Success
-- **Tasks completed**: 8/8 — T1 (audit), T2 (outline skill), T3 (handoff schema + V7 handler), T4 (initialize template), T5 (9 other skills), T6 (scripts), T7 (docs/MEMORY.md), T8 (verification)
-- **Files modified**: ~30 files + 8 reference files (scope expansion); see `docs/project_notes/trunk/build_report.md` for full list
-
-## Code Producers Used
-
-- **Specialist**: devops-infrastructure
-  - **Tasks**: T1, T6, T8
-  - **Output files**:
-    - `docs/project_notes/trunk/audit/plan-rename-hitlist.md` (T1)
-    - `scripts/install-skills.js` (T6)
-    - `scripts/uninstall-skills.js` (T6)
-    - `package.json` (T6)
-    - `docs/project_notes/trunk/verification/devops-infrastructure-verification.md` (T8)
-
-- **Specialist**: database-architect
-  - **Tasks**: T3
-  - **Output files**:
-    - `skills/intuition-handoff/SKILL.md` (T3 — schema v8.0, V7 migration handler, state field renames)
-
-## Acceptance Criteria
-
-### T1: Audit all phase-name references
-1. A complete hit list exists covering all files with phase-name "plan" references
-2. Each hit is categorized as phase-name (rename) or generic English (keep)
-3. Hit list is grouped by file for easy task-by-task tracking
-
-### T3: Update handoff skill with v7→v8 state migration
-1. Schema version is 8.0 in the handoff SKILL.md header and schema definition
-2. v7→v8 migration handler exists and renames `planning` → `outline` in state objects
-3. All transition messages route to `/intuition-outline` (not `/intuition-plan`)
-4. All file path references use `outline_brief.md`, `outline.md`
-5. State field references use `outline` throughout
-6. Existing v5→v6 and v6→v7 migration handlers are preserved unchanged
-
-### T6: Update scripts and package configuration
-1. `scripts/install-skills.js` references `intuition-outline` (not `intuition-plan`)
-2. `scripts/uninstall-skills.js` references `intuition-outline` (not `intuition-plan`)
-3. `package.json` contains no "plan" phase-name references
-4. Legacy cleanup in install script handles removal of old `intuition-plan` from `~/.claude/skills/`
-
-### T8: Verification sweep
-1. Grep for phase-name "plan" patterns returns zero hits across the entire codebase
-2. `skills/intuition-outline/SKILL.md` exists with correct frontmatter
-3. Install script skill list includes `intuition-outline` and not `intuition-plan`
-4. v7→v8 migration handler correctly renames `planning` → `outline` in a sample state object
-5. Verification report documents all checks performed and results
-
-## Decision Log References
-- Specialist decision logs:
-  - `docs/project_notes/trunk/scratch/devops-infrastructure-decisions.json`
-  - `docs/project_notes/trunk/scratch/database-architect-decisions.json`
-- Project decisions: `docs/project_notes/decisions.md`
-
-## Blueprint References
-- `docs/project_notes/trunk/blueprints/devops-infrastructure.md` (T1, T6, T8)
-- `docs/project_notes/trunk/blueprints/database-architect.md` (T3)
-
-## Specialist Test Recommendations
-
-No specialist test recommendations.
-
-(Build report contains: "No test deliverables found in blueprints.")
-
-## Known Issues
-
-| Issue | Resolution |
-|-------|-----------|
-| Reference files (`references/` subdirectories) had 39 stale references not in plan scope | Scope expanded during build; 68 edits applied across 8 reference files |
-| MEMORY.md auto-memory path (not project root) | Absolute path passed to T7 producer; file updated successfully |
-| T3/T5 overlap on handoff SKILL.md | T3 executed first; T5 verified and found zero remaining edits |
-| Legacy docs (13 files) still have stale references | Classified out-of-scope; not blocking. Documented in verification report. |

package/docs/project_notes/archive/trunk-v9.2-complete/test_report.md

@@ -1,26 +0,0 @@
-# Test Report
-
-**Plan:** Rename Plan Phase to Outline
-**Date:** 2026-03-05
-**Status:** Skipped
-
-## Reason
-
-User elected to skip testing. Rationale:
-
-- Build was a pure text rename refactor (~530 edits across ~30 files)
-- No behavioral changes — only phase-name string replacements
-- Task 8 verification sweep already passed 34/34 checks with zero stale in-scope references
-- Only executable code modified was `scripts/install-skills.js` and `scripts/uninstall-skills.js` (minor edits to skill lists)
-- No test framework exists in the project; no existing tests to extend
-- Additional automated testing would provide minimal value beyond what T8 already verified
-
-## Decision Compliance
-
-- Checked **12** decisions across **3** specialist decision logs
-- `[USER]` violations: None (0 USER-tier decisions exist)
-- `[SPEC]` conflicts noted: None
-
-## Files Modified (beyond test files)
-
-None — no implementation fixes applied.

package/docs/project_notes/archive/trunk-v9.2-complete/verification/devops-infrastructure-verification.md

@@ -1,172 +0,0 @@
-# DevOps Infrastructure Verification Report
-
-**Date**: 2026-03-05
-**Task**: T8 — Verification Protocol (plan rename: intuition-plan -> intuition-outline)
-**Blueprint**: docs/project_notes/trunk/blueprints/devops-infrastructure.md
-
----
-
-## Phase 1: Zero Stale References
-
-| # | Pattern | Hits Found | In-Scope Hits | Status |
-|---|---------|-----------|---------------|--------|
-| 1 | `intuition-plan` | 42 total | 0 | PASS |
-| 2 | `planning_brief` | 36 total | 0 | PASS |
-| 3 | `plan\.md` (artifact ref) | 68 total | 1 (initialize SKILL.md:114 — generic English "plan.md" in a list of example files not to create) | PASS |
-| 4 | `\.planning_research` | 8 total | 0 | PASS |
-| 5 | `"planning"` (JSON key/status) | 16 total | 0 | PASS |
-| 6 | `planning phase` | 2 total | 0 | PASS |
-| 7 | `→.*planning\|planning.*→` | 10 total | 0 | PASS |
-
-### Pattern 1 detail — `intuition-plan`
-- **install-skills.js:113,116** — Legacy cleanup block referencing old name to remove it. EXPECTED.
-- **uninstall-skills.js:65** — Legacy section listing old name for cleanup. EXPECTED.
-- **All other hits** (INSTALLATION.md, docs/intuition-architecture.md, docs/intuition-workflow.md, QUICK_TEST_CHECKLIST.md, docs/PROJECT_CONTEXT.md, docs/v7_design_spec.md, docs/v7_plan.md, SKILL_INTERACTION_GUIDE.md, WALDO_V3_DESIGN_SUMMARY.md, WALDO_V3_COMPLETE_DOCUMENTATION.md) — OUT OF SCOPE legacy docs.
-
-### Pattern 2 detail — `planning_brief`
-- **handoff SKILL.md:210** — V3 migration handler references old artifact names to move files. EXPECTED.
-- **All other hits** — OUT OF SCOPE legacy docs (QUICK_TEST_CHECKLIST.md, docs/intuition_design_skill_spec.md, docs/v7_design_spec.md, docs/PROJECT_CONTEXT.md, SKILL_INTERACTION_GUIDE.md, docs/v7_plan.md, WALDO_V3_COMPLETE_DOCUMENTATION.md).
-
-### Pattern 3 detail — `plan\.md`
-- **intuition-initialize SKILL.md:114** — Says "Do NOT create workflow output files (prompt_brief.md, plan.md, etc.)". This is generic English listing old artifact names as examples. The initialize skill does not produce or consume plan.md — it's a cautionary note. Classified as EXPECTED (English example list; not a producer/consumer reference).
-- **intuition-detail SKILL.md:83,144,161** — References to `research-plan.md` (a crash recovery scratch file, not the old plan.md artifact). EXPECTED.
-- **docs/v9/test/phase4/TEST_PLAN.md:32** — Historical test fixture referencing `mock_plan.md`. OUT OF SCOPE.
-- **All other hits** — OUT OF SCOPE legacy docs.
-
-### Pattern 4 detail — `\.planning_research`
-- **handoff SKILL.md:210** — V3 migration handler. EXPECTED.
-- **All other hits** — OUT OF SCOPE legacy docs (docs/v7_design_spec.md, docs/v7_plan.md).
-
-### Pattern 5 detail — `"planning"`
-- **package.json:8** — npm keyword for discoverability ("planning" as a generic concept). EXPECTED (not a phase-name reference).
-- **marketplace.json:21** — Plugin keyword. OUT OF SCOPE (legacy marketplace metadata, not in plan scope).
-- **handoff SKILL.md:194** — V7 migration handler text: `rename the "planning" key to "outline"` and `change any status == "planning" to "outline"`. EXPECTED (describes old name for migration logic).
-- **All other hits** — OUT OF SCOPE legacy docs (docs/intuition-architecture.md, docs/v7_design_spec.md, SKILL_INTERACTION_GUIDE.md, docs/intuition_design_skill_spec.md, docs/PROJECT_CONTEXT.md).
-
-### Pattern 6 detail — `planning phase`
-- **docs/intuition-architecture.md:150** — OUT OF SCOPE legacy doc.
-- **docs/v7_design_spec.md:583** — OUT OF SCOPE legacy doc.
-
-### Pattern 7 detail — workflow arrows with `planning`
-- **docs/intuition-architecture.md:127-128** — OUT OF SCOPE legacy doc.
-- **docs/PROJECT_CONTEXT.md:72,347** — OUT OF SCOPE legacy doc.
-- **docs/intuition_design_skill_spec.md:187** — OUT OF SCOPE legacy doc.
-- **QUICK_TEST_CHECKLIST.md:90,93** — OUT OF SCOPE legacy doc.
-- **docs/v7_design_spec.md:1043** — OUT OF SCOPE legacy doc.
-- **SKILL_INTERACTION_GUIDE.md** (multiple lines) — OUT OF SCOPE legacy doc.
-- **handoff SKILL.md:194** — V7 migration handler. EXPECTED.
-- **start SKILL.md:109** — Internal label `planning_in_progress` (routes correctly to `/intuition-outline`). EXPECTED (generic English, not a phase key).
-
----
-
-## Phase 2: Structural Verification
-
-| Check | Expected | Actual | Status |
-|-------|----------|--------|--------|
-| S1: `skills/intuition-outline/SKILL.md` exists | exists | exists | PASS |
-| S2: Frontmatter `name: intuition-outline` | `intuition-outline` | `intuition-outline` | PASS |
-| S3: `skills/intuition-plan/` does NOT exist | absent | absent | PASS |
-| S4: install-skills.js has `'intuition-outline'` in skill list | present | present (line 48) | PASS |
-| S4b: install-skills.js does NOT have `'intuition-plan'` in skill list | absent from active list | absent (only in legacy cleanup block) | PASS |
-| S5: uninstall-skills.js active list has `'intuition-outline'` | present | present (line 49) | PASS |
-| S6: install-skills.js has legacy cleanup for `intuition-plan` | present | present (lines 112-117) | PASS |
-| S7: uninstall-skills.js legacy section has `'intuition-plan'` | present | present (line 65) | PASS |
-
----
-
-## Phase 3: Migration Handler Validation
-
-### V7 State Migration (handoff SKILL.md, line 192-194)
-
-| Test | Expected | Actual | Status |
-|------|----------|--------|--------|
-| Fires on version | `"7.0"` | `version == "7.0"` | PASS |
-| Renames `planning` key | to `outline` | "rename the `planning` key to `outline` in the `workflow` object" | PASS |
-| Changes status | `"planning"` to `"outline"` | "change any `status == \"planning\"` to `\"outline\"`" | PASS |
-| Sets version | `"8.0"` | `Set version: "8.0"` | PASS |
-| Preserves sub-fields | started, completed, completed_at, approved | "(preserving all sub-fields: started, completed, completed_at, approved)" | PASS |
-
-### Initialize Skill State Template (SKILL.md)
-
-| Test | Expected | Actual | Status |
-|------|----------|--------|--------|
-| Version in SKILL.md | `"8.0"` | `"version": "8.0"` (line 125) | PASS |
-| Workflow key in SKILL.md | `"outline"` | `"outline": { ... }` (line 137) | PASS |
-| No `"planning"` key in SKILL.md | absent | absent | PASS |
-
-### State Template JSON (references/state_template.json)
-
-| Test | Expected | Actual | Status |
-|------|----------|--------|--------|
-| Version in JSON | `"8.0"` | `"version": "8.0"` (line 3) | PASS |
-| Workflow key in JSON | `"outline"` | `"outline": { ... }` (line 15) | PASS |
-| No `"planning"` key in JSON | absent | absent | PASS |
-
----
-
-## Phase 4: Cross-Reference Integrity
-
-### Artifact: `outline.md`
-
-| Skill | Role | Reference Found | Status |
-|-------|------|----------------|--------|
-| intuition-outline | Producer | `{context_path}/outline.md` (line 19, 70, 77, 331) | PASS |
-| intuition-handoff | Consumer | `{context_path}outline.md` (line 48), `outline.md` (lines 226, 246, 282, 293, 389, 397, 430) | PASS |
-| intuition-detail | Consumer | (not expected — detail reads blueprints, not outline directly) | N/A |
-| intuition-build | Consumer | `outline.md` (lines 59, 77, 94, 201, 202) | PASS |
-| intuition-start | Consumer | `outline.md` (line 151) | PASS |
-
-### Artifact: `outline_brief.md`
-
-| Skill | Role | Reference Found | Status |
-|-------|------|----------------|--------|
-| intuition-handoff | Producer | `{context_path}outline_brief.md` (lines 220, 222) | PASS |
-| intuition-outline | Consumer | `outline_brief.md` (line 24, 91) | PASS |
-
-### Artifact: `.outline_research/`
-
-| Skill | Role | Reference Found | Status |
-|-------|------|----------------|--------|
-| intuition-outline | Producer/Consumer | `.outline_research/` (lines 21, 80, 98, 142, 173, 244, 249, 295, 539, 549, 554-556) | PASS |
-
-### Stale artifact names in skills
-
-| Artifact | Pattern | Hits in Skills | Status |
-|----------|---------|---------------|--------|
-| `planning_brief` | old brief name | 1 hit — handoff V3 migration only | PASS |
-| `.planning_research` | old research dir | 1 hit — handoff V3 migration only | PASS |
-
----
-
-## Out-of-Scope Files
-
-These legacy/historical documentation files contain stale `intuition-plan`, `planning_brief`, `plan.md`, `"planning"`, or `planning phase` references. They were NOT in the plan scope and are classified as OUT OF SCOPE:
-
-| File | Stale Patterns Found |
-|------|---------------------|
-| `INSTALLATION.md` | `intuition-plan`, `project_plan.md` |
-| `docs/intuition-architecture.md` | `intuition-plan`, `plan.md`, `"planning"`, `planning phase`, workflow arrows |
-| `docs/intuition-workflow.md` | `intuition-plan`, `plan.md` |
-| `QUICK_TEST_CHECKLIST.md` | `intuition-plan`, `planning_brief`, `plan.md`, workflow arrows |
-| `docs/PROJECT_CONTEXT.md` | `intuition-plan`, `planning_brief`, `plan.md`, `"planning"`, workflow arrows |
-| `docs/v7_design_spec.md` | `intuition-plan`, `planning_brief`, `plan.md`, `.planning_research`, `"planning"`, `planning phase` |
-| `docs/v7_plan.md` | `intuition-plan`, `planning_brief`, `plan.md`, `.planning_research` |
-| `SKILL_INTERACTION_GUIDE.md` | `intuition-plan`, `planning_brief`, `plan.md`, `"planning"`, workflow arrows |
-| `WALDO_V3_DESIGN_SUMMARY.md` | `intuition-plan` |
-| `WALDO_V3_COMPLETE_DOCUMENTATION.md` | `planning_brief` |
-| `docs/intuition_design_skill_spec.md` | `planning_brief`, `plan.md`, workflow arrows |
-| `.claude-plugin/marketplace.json` | `"planning"` keyword |
-| `docs/v9/test/phase4/TEST_PLAN.md` | `mock_plan.md` (test fixture) |
-
----
-
-## Summary
-
-| Category | Count |
-|----------|-------|
-| Total checks | 34 |
-| Passed | 34 |
-| Failed | 0 |
-| Out of scope files | 13 |
-| Expected hits (migration handlers, legacy cleanup, npm keywords) | 8 |
-| **Overall** | **PASS** |

package/docs/project_notes/bugs.md

@@ -1,41 +0,0 @@
-# Bug Log Template
-
-This file demonstrates the format for logging bugs and their solutions. Keep entries brief and chronological.
-
-## Format
-
-Each bug entry should include:
-- Date (YYYY-MM-DD)
-- Brief description of the bug/issue
-- Solution or fix applied
-- Any prevention notes (optional)
-
-Use bullet lists for simplicity. Older entries can be manually removed when they become irrelevant.
-
-## Example Entries
-
-### 2025-01-15 - Docker Architecture Mismatch
-- **Issue**: Container failing to start with "exec format error"
-- **Root Cause**: Built on ARM64 Mac but deploying to AMD64 Cloud Run
-- **Solution**: Added `--platform linux/amd64` to docker build command
-- **Prevention**: Always specify platform in Dockerfile and build scripts
-
-### 2025-01-20 - Cloud Scheduler HTTPS Requirement
-- **Issue**: Cloud Scheduler jobs failing with "URL must use HTTPS"
-- **Root Cause**: Forgot Cloud Run URLs require HTTPS by default
-- **Solution**: Updated all scheduler job URLs from http:// to https://
-- **Prevention**: Remember GCP services enforce HTTPS; check URLs in infrastructure code
-
-### 2025-01-22 - Database Connection Pool Exhaustion
-- **Issue**: API returning 500 errors under load
-- **Root Cause**: Connection pool size too small (default 5)
-- **Solution**: Increased pool_size to 20 and max_overflow to 10 in SQLAlchemy config
-- **Prevention**: Load test APIs before production deployment
-
-## Tips
-
-- Keep descriptions under 2-3 lines
-- Focus on what was learned, not exhaustive details
-- Include enough context for future reference
-- Date entries so you know how recent the issue is
-- Periodically clean out very old entries (6+ months)

package/docs/project_notes/decisions.md

@@ -1,147 +0,0 @@
-# Architectural Decisions Template
-
-This file demonstrates the format for logging architectural decisions (ADRs). Use bullet lists for clarity.
-
-## Format
-
-Each decision should include:
-- Date and ADR number
-- Context (why the decision was needed)
-- Decision (what was chosen)
-- Alternatives considered
-- Consequences (trade-offs, implications)
-
-## Example Entries
-
-### ADR-001: Use Workload Identity Federation for GitHub Actions (2025-01-10)
-
-**Context:**
-- Need secure authentication from GitHub Actions to GCP
-- Service account keys are deprecated and considered insecure
-- Want to avoid managing long-lived credentials
-
-**Decision:**
-- Use Workload Identity Federation (WIF) for GitHub Actions authentication
-- Configure via `WIF_PROVIDER` and `WIF_SERVICE_ACCOUNT` secrets
-
-**Alternatives Considered:**
-- Service account JSON keys → Rejected: security risk, manual rotation required
-- Environment-specific credentials → Rejected: harder to manage across repos
-
-**Consequences:**
-- ✅ More secure (no long-lived credentials)
-- ✅ Automatic credential rotation
-- ✅ Better audit trail
-- ❌ Slightly more complex initial setup
-- ❌ Requires GitHub OIDC support
-
-### ADR-002: Use Alembic for Database Migrations (2025-01-12)
-
-**Context:**
-- Need version control for database schema changes
-- Multiple developers working on database schema
-- Want to avoid manual SQL scripts and migration conflicts
-
-**Decision:**
-- Use Alembic as the database migration tool
-- Store migrations in `alembic/versions/` directory
-- Use auto-generate feature for model changes
-
-**Alternatives Considered:**
-- Raw SQL scripts → Rejected: no versioning, error-prone
-- Flask-Migrate → Rejected: too tied to Flask framework
-- Django migrations → Rejected: using FastAPI, not Django
-
-**Consequences:**
-- ✅ Version-controlled schema changes
-- ✅ Automatic migration generation from models
-- ✅ Easy rollback capability
-- ❌ Learning curve for team
-- ❌ Must remember to generate migrations after model changes
-
-### ADR-003: Use AlloyDB Instead of Cloud SQL (2025-01-15)
-
-**Context:**
-- Need PostgreSQL-compatible database in GCP
-- Require high availability and automatic backups
-- Performance-critical application with complex queries
-
-**Decision:**
-- Use AlloyDB for PostgreSQL instead of Cloud SQL
-- Configure with automated backups and point-in-time recovery
-
-**Alternatives Considered:**
-- Cloud SQL PostgreSQL → Rejected: slower query performance
-- Self-managed PostgreSQL on GCE → Rejected: high operational overhead
-- Firestore → Rejected: need relational data model and SQL
-
-**Consequences:**
-- ✅ Better query performance (2-4x faster than Cloud SQL)
-- ✅ PostgreSQL compatibility
-- ✅ Managed service (automated backups, HA)
-- ❌ Higher cost than Cloud SQL
-- ❌ Newer service, less community documentation
-
-## Tips
-
-- Number decisions sequentially (ADR-001, ADR-002, etc.)
-- Always include date for context
-- Be honest about trade-offs (use ✅ and ❌)
-- Keep alternatives brief but clear
-- Update decisions if they're revisited/changed
-- Focus on "why" not "how" (implementation details go elsewhere)
-
-### ADR-P002: "build plan" and "test plan" Are Preserved as Generic English (2026-03-04)
-
-**Status:** Decided — Technical Writer specialist consultation
-
-**Context:**
-- The rename refactor replaces all phase-name "plan" references with "outline"
-- `intuition-build/SKILL.md` uses "build plan" (lines 20, 61, 106, 109) meaning "the builder's execution strategy"
-- `intuition-test/SKILL.md` uses "test plan" (lines 44, 102, 161, 181, 184, 197, 203) meaning "the testing strategy"
-- These are standard English compound nouns, not references to the planning phase or plan.md artifact
-
-**Decision:**
-- "build plan" and "test plan" are KEPT unchanged in all skill files
-- These terms refer to execution/testing strategies, not the workflow phase
-
-**Alternatives Considered:**
-- Reword to "build strategy" / "test strategy" → Rejected: unnecessary churn, "test plan" is universally understood
-- Reword to "build sequence" / "test approach" → Rejected: slightly less clear than original terms
-
-**Consequences:**
-- ✅ Minimal disruption, established terminology preserved
-- ✅ Consistent with disambiguation rule (generic English "plan" stays)
-- ⚠️ Minor potential reader confusion in first few sessions post-rename (low impact)
-
-**Discovered During:** Technical Writer specialist consultation (2026-03-04)
-
----
-
-### ADR-P001: Rename Plan Phase to Outline Across Entire Framework (2026-03-04)
-
-**Status:** Approved
-
-**Context:**
-- The `intuition-plan` skill and "planning" phase are being renamed to `intuition-outline` / "outlining"
-- All phase-name references across SKILL.md files, state schema, routing, scripts, and docs must be updated
-- Existing state files (v7.0) have a `planning` field that would break without migration
-
-**Decision:**
-- Full rename: `plan` → `outline` wherever it refers to the workflow phase
-- State schema field: `planning` → `outline` (base form, matches majority of existing fields), schema version bumps v7.0 → v8.0
-- v7→v8 migration handler added to handoff (following v5→v6 and v6→v7 patterns)
-- Output files: `plan.md` → `outline.md`, derived files use base form: `outline_brief.md`, `.outline_research/`
-- Generic English "plan" (e.g., "research plan", "action plan") is NOT renamed
-
-**Alternatives Considered:**
-- Partial rename (surface only) → Rejected: user wants full consistency
-- Keep state field as `planning` → Rejected: user wants complete rename
-- No migration handler → Rejected: would break existing project state files
-
-**Consequences:**
-- ✅ Complete naming consistency — no stale references
-- ✅ Existing state files migrate automatically via v7→v8 handler
-- ✅ Pure rename — no behavioral changes
-- ❌ Wide blast radius — many files touched
-- ❌ Anyone with local installs needs to re-install or the skill command changes