ariadna 1.2.0 → 1.2.2

data/data/ariadna/references/decimal-phase-calculation.md

@@ -58,8 +58,8 @@ Decimal phase directories use the full decimal number:
 
 ```bash
 SLUG=$(ariadna-tools generate-slug "$DESCRIPTION" --raw)
-PHASE_DIR=".planning/phases/${DECIMAL_PHASE}-${SLUG}"
+PHASE_DIR=".ariadna_planning/phases/${DECIMAL_PHASE}-${SLUG}"
 mkdir -p "$PHASE_DIR"
 ```
 
-Example: `.planning/phases/06.1-fix-critical-auth-bug/`
+Example: `.ariadna_planning/phases/06.1-fix-critical-auth-bug/`

data/data/ariadna/references/git-integration.md

@@ -51,7 +51,7 @@ Phases:
 What to commit:
 
 ```bash
-ariadna-tools commit "docs: initialize [project-name] ([N] phases)" --files .planning/
+ariadna-tools commit "docs: initialize [project-name] ([N] phases)" --files .ariadna_planning/
 ```
 
 </format>
@@ -123,13 +123,13 @@ Tasks completed: [N]/[N]
 - [Task 2 name]
 - [Task 3 name]
 
-SUMMARY: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
+SUMMARY: .ariadna_planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
 ```
 
 What to commit:
 
 ```bash
-ariadna-tools commit "docs({phase}-{plan}): complete [plan-name] plan" --files .planning/phases/XX-name/{phase}-{plan}-PLAN.md .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md .planning/STATE.md .planning/ROADMAP.md
+ariadna-tools commit "docs({phase}-{plan}): complete [plan-name] plan" --files .ariadna_planning/phases/XX-name/{phase}-{plan}-PLAN.md .ariadna_planning/phases/XX-name/{phase}-{plan}-SUMMARY.md .ariadna_planning/STATE.md .ariadna_planning/ROADMAP.md
 ```
 
 **Note:** Code files NOT included - already committed per-task.
@@ -149,7 +149,7 @@ Current: [task name]
 What to commit:
 
 ```bash
-ariadna-tools commit "wip: [phase-name] paused at task [X]/[Y]" --files .planning/
+ariadna-tools commit "wip: [phase-name] paused at task [X]/[Y]" --files .ariadna_planning/
 ```
 
 </format>

data/data/ariadna/references/git-planning-commit.md

@@ -4,20 +4,20 @@ Commit planning artifacts using the ariadna-tools CLI, which automatically check
 
 ## Commit via CLI
 
-Always use `ariadna-tools commit` for `.planning/` files — it handles `commit_docs` and gitignore checks automatically:
+Always use `ariadna-tools commit` for `.ariadna_planning/` files — it handles `commit_docs` and gitignore checks automatically:
 
 ```bash
-ariadna-tools commit "docs({scope}): {description}" --files .planning/STATE.md .planning/ROADMAP.md
+ariadna-tools commit "docs({scope}): {description}" --files .ariadna_planning/STATE.md .ariadna_planning/ROADMAP.md
 ```
 
-The CLI will return `skipped` (with reason) if `commit_docs` is `false` or `.planning/` is gitignored. No manual conditional checks needed.
+The CLI will return `skipped` (with reason) if `commit_docs` is `false` or `.ariadna_planning/` is gitignored. No manual conditional checks needed.
 
 ## Amend previous commit
 
-To fold `.planning/` file changes into the previous commit:
+To fold `.ariadna_planning/` file changes into the previous commit:
 
 ```bash
-ariadna-tools commit "" --files .planning/codebase/*.md --amend
+ariadna-tools commit "" --files .ariadna_planning/codebase/*.md --amend
 ```
 
 ## Commit Message Patterns
@@ -34,5 +34,5 @@ ariadna-tools commit "" --files .planning/codebase/*.md --amend
 ## When to Skip
 
 - `commit_docs: false` in config
-- `.planning/` is gitignored
-- No changes to commit (check with `git status --porcelain .planning/`)
+- `.ariadna_planning/` is gitignored
+- No changes to commit (check with `git status --porcelain .ariadna_planning/`)

data/data/ariadna/references/model-profile-resolution.md

@@ -5,7 +5,7 @@ Resolve model profile once at the start of orchestration, then use it for all Ta
 ## Resolution Pattern
 
 ```bash
-MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")
+MODEL_PROFILE=$(cat .ariadna_planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")
 ```
 
 Default: `balanced` if not set or config missing.

data/data/ariadna/references/model-profiles.md

@@ -41,7 +41,7 @@ Model profiles control which Claude model each Ariadna agent uses. This allows b
 Orchestrators resolve model before spawning:
 
 ```
-1. Read .planning/config.json
+1. Read .ariadna_planning/config.json
 2. Get model_profile (default: "balanced")
 3. Look up agent in table above
 4. Pass model parameter to Task call
@@ -51,7 +51,7 @@ Orchestrators resolve model before spawning:
 
 Runtime: `/ariadna:set-profile <profile>`
 
-Per-project default: Set in `.planning/config.json`:
+Per-project default: Set in `.ariadna_planning/config.json`:
 ```json
 {
   "model_profile": "balanced"

data/data/ariadna/references/planning-config.md

@@ -1,6 +1,6 @@
 <planning_config>
 
-Configuration options for `.planning/` directory behavior.
+Configuration options for `.ariadna_planning/` directory behavior.
 
 <config_schema>
 ```json
@@ -32,15 +32,15 @@ Configuration options for `.planning/` directory behavior.
 - Full history of planning decisions preserved
 
 **When `commit_docs: false`:**
-- Skip all `git add`/`git commit` for `.planning/` files
-- User must add `.planning/` to `.gitignore`
+- Skip all `git add`/`git commit` for `.ariadna_planning/` files
+- User must add `.ariadna_planning/` to `.gitignore`
 - Useful for: OSS contributions, client projects, keeping planning private
 
 **Using ariadna-tools (preferred):**
 
 ```bash
 # Commit with automatic commit_docs + gitignore checks:
-ariadna-tools commit "docs: update state" --files .planning/STATE.md
+ariadna-tools commit "docs: update state" --files .ariadna_planning/STATE.md
 
 # Load config via state load (returns JSON):
 INIT=$(ariadna-tools state load)
@@ -51,12 +51,12 @@ INIT=$(ariadna-tools init execute-phase "1")
 # commit_docs is included in all init command outputs
 ```
 
-**Auto-detection:** If `.planning/` is gitignored, `commit_docs` is automatically `false` regardless of config.json. This prevents git errors when users have `.planning/` in `.gitignore`.
+**Auto-detection:** If `.ariadna_planning/` is gitignored, `commit_docs` is automatically `false` regardless of config.json. This prevents git errors when users have `.ariadna_planning/` in `.gitignore`.
 
 **Commit via CLI (handles checks automatically):**
 
 ```bash
-ariadna-tools commit "docs: update state" --files .planning/STATE.md
+ariadna-tools commit "docs: update state" --files .ariadna_planning/STATE.md
 ```
 
 The CLI checks `commit_docs` config and gitignore status internally — no manual conditionals needed.
@@ -67,12 +67,12 @@ The CLI checks `commit_docs` config and gitignore status internally — no manua
 
 **When `search_gitignored: false` (default):**
 - Standard rg behavior (respects .gitignore)
-- Direct path searches work: `rg "pattern" .planning/` finds files
-- Broad searches skip gitignored: `rg "pattern"` skips `.planning/`
+- Direct path searches work: `rg "pattern" .ariadna_planning/` finds files
+- Broad searches skip gitignored: `rg "pattern"` skips `.ariadna_planning/`
 
 **When `search_gitignored: true`:**
-- Add `--no-ignore` to broad rg searches that should include `.planning/`
-- Only needed when searching entire repo and expecting `.planning/` matches
+- Add `--no-ignore` to broad rg searches that should include `.ariadna_planning/`
+- Only needed when searching entire repo and expecting `.ariadna_planning/` matches
 
 **Note:** Most Ariadna operations use direct file reads or explicit paths, which work regardless of gitignore status.
 
@@ -92,12 +92,12 @@ To use uncommitted mode:
 
 2. **Add to .gitignore:**
    ```
-   .planning/
+   .ariadna_planning/
    ```
 
-3. **Existing tracked files:** If `.planning/` was previously tracked:
+3. **Existing tracked files:** If `.ariadna_planning/` was previously tracked:
    ```bash
-   git rm -r --cached .planning/
+   git rm -r --cached .ariadna_planning/
    git commit -m "chore: stop tracking planning docs"
    ```
 

data/data/ariadna/references/rails-conventions.md

@@ -216,6 +216,7 @@ class UserTest < ActiveSupport::TestCase
 
   test "validates email presence" do
     user = User.new(name: "Test")
+
     assert_not user.valid?
     assert_includes user.errors[:email], "can't be blank"
   end
@@ -238,6 +239,7 @@ class PostsControllerTest < ActionDispatch::IntegrationTest
 
   test "index returns posts" do
     get posts_url
+
     assert_response :success
     assert_select "h2", posts(:first).title
   end
@@ -341,11 +343,16 @@ Tasks:
 ### Add Turbo/Hotwire Feature
 ```
 Tasks:
-1. Add Turbo Frame wrapping + controller turbo_stream response
+1. Add Turbo Frame wrapping to target views + controller turbo_stream responses
    Files: app/views/[model]/*.html.erb, app/controllers/[model]_controller.rb
+   Conventions: 422 for validation errors, 303 for redirects, dom_id for frame IDs
 2. Add Stimulus controller (if interactive behavior needed)
    Files: app/javascript/controllers/[name]_controller.js
-3. Add system test for real-time behavior
+   Conventions: static values/targets/outlets first, connect/disconnect symmetry
+3. Add Turbo Stream broadcasts (if real-time updates needed)
+   Files: app/models/[model].rb (after_create_commit callbacks)
+   Conventions: prefer default stream actions, broadcast_append_to/replace_to
+4. Add system test for Turbo/Stimulus behavior
    Files: test/system/[feature]_test.rb
 ```
 

data/data/ariadna/references/tdd.md

@@ -50,8 +50,8 @@ Output: [Working, tested feature]
 </objective>
 
 <context>
-@.planning/PROJECT.md
-@.planning/ROADMAP.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/ROADMAP.md
 @relevant/source/files.rb
 </context>
 

data/data/ariadna/templates/DEBUG.md

@@ -1,6 +1,6 @@
 # Debug Template
 
-Template for `.planning/debug/[slug].md` — active debug session tracking.
+Template for `.ariadna_planning/debug/[slug].md` — active debug session tracking.
 
 ---
 
@@ -129,7 +129,7 @@ files_changed: []
 
 **On resolution:**
 - status → "resolved"
-- Move file to .planning/debug/resolved/
+- Move file to .ariadna_planning/debug/resolved/
 
 </lifecycle>
 

data/data/ariadna/templates/UAT.md

@@ -1,6 +1,6 @@
 # UAT Template
 
-Template for `.planning/phases/XX-name/{phase}-UAT.md` — persistent UAT session tracking.
+Template for `.ariadna_planning/phases/XX-name/{phase}-UAT.md` — persistent UAT session tracking.
 
 ---
 
@@ -129,7 +129,7 @@ skipped: [N]
       issue: "after_commit not invalidating counter cache"
   missing:
     - "Add counter cache invalidation to after_commit callback"
-  debug_session: ".planning/debug/comment-not-refreshing.md"
+  debug_session: ".ariadna_planning/debug/comment-not-refreshing.md"
 ```
 
 </diagnosis_lifecycle>
@@ -242,6 +242,6 @@ skipped: 0
       issue: "after_commit not invalidating counter cache"
   missing:
     - "Add counter cache invalidation to after_commit callback"
-  debug_session: ".planning/debug/comment-not-refreshing.md"
+  debug_session: ".ariadna_planning/debug/comment-not-refreshing.md"
 ```
 </good_example>

data/data/ariadna/templates/codebase/architecture.md

@@ -1,6 +1,6 @@
 # Architecture Template
 
-Template for `.planning/codebase/ARCHITECTURE.md` - captures conceptual code organization.
+Template for `.ariadna_planning/codebase/ARCHITECTURE.md` - captures conceptual code organization.
 
 **Purpose:** Document how the code is organized at a conceptual level. Complements STRUCTURE.md (which shows physical file locations).
 

data/data/ariadna/templates/codebase/concerns.md

@@ -1,6 +1,6 @@
 # Codebase Concerns Template
 
-Template for `.planning/codebase/CONCERNS.md` - captures known issues and areas requiring care.
+Template for `.ariadna_planning/codebase/CONCERNS.md` - captures known issues and areas requiring care.
 
 **Purpose:** Surface actionable warnings about the codebase. Focused on "what to watch out for when making changes."
 

data/data/ariadna/templates/codebase/conventions.md

@@ -1,6 +1,6 @@
 # Coding Conventions Template
 
-Template for `.planning/codebase/CONVENTIONS.md` - captures coding style and patterns.
+Template for `.ariadna_planning/codebase/CONVENTIONS.md` - captures coding style and patterns.
 
 **Purpose:** Document how code is written in this codebase. Prescriptive guide for Claude to match existing style.
 

data/data/ariadna/templates/codebase/integrations.md

@@ -1,6 +1,6 @@
 # External Integrations Template
 
-Template for `.planning/codebase/INTEGRATIONS.md` - captures external service dependencies.
+Template for `.ariadna_planning/codebase/INTEGRATIONS.md` - captures external service dependencies.
 
 **Purpose:** Document what external systems this codebase communicates with. Focused on "what lives outside our code that we depend on."
 

data/data/ariadna/templates/codebase/stack.md

@@ -1,6 +1,6 @@
 # Technology Stack Template
 
-Template for `.planning/codebase/STACK.md` - captures the technology foundation.
+Template for `.ariadna_planning/codebase/STACK.md` - captures the technology foundation.
 
 **Purpose:** Document what technologies run this codebase. Focused on "what executes when you run the code."
 

data/data/ariadna/templates/codebase/structure.md

@@ -1,6 +1,6 @@
 # Structure Template
 
-Template for `.planning/codebase/STRUCTURE.md` - captures physical file organization.
+Template for `.ariadna_planning/codebase/STRUCTURE.md` - captures physical file organization.
 
 **Purpose:** Document where things physically live in the codebase. Answers "where do I put X?"
 

data/data/ariadna/templates/codebase/testing.md

@@ -1,6 +1,6 @@
 # Testing Patterns Template
 
-Template for `.planning/codebase/TESTING.md` - captures test framework and patterns.
+Template for `.ariadna_planning/codebase/TESTING.md` - captures test framework and patterns.
 
 **Purpose:** Document how tests are written and run. Guide for adding tests that match existing patterns.
 

data/data/ariadna/templates/context.md

@@ -1,6 +1,6 @@
 # Phase Context Template
 
-Template for `.planning/phases/XX-name/{phase}-CONTEXT.md` - captures implementation decisions for a phase.
+Template for `.ariadna_planning/phases/XX-name/{phase}-CONTEXT.md` - captures implementation decisions for a phase.
 
 **Purpose:** Document decisions that downstream agents need. Researcher uses this to know WHAT to investigate. Planner uses this to know WHAT choices are locked vs flexible.
 
@@ -276,7 +276,7 @@ The output should answer: "What does the researcher need to investigate? What ch
 - "Easy to use"
 
 **After creation:**
-- File lives in phase directory: `.planning/phases/XX-name/{phase}-CONTEXT.md`
+- File lives in phase directory: `.ariadna_planning/phases/XX-name/{phase}-CONTEXT.md`
 - `ariadna-phase-researcher` uses decisions to focus investigation
 - `ariadna-planner` uses decisions + research to create executable tasks
 - Downstream agents should NOT need to ask the user again about captured decisions

data/data/ariadna/templates/continue-here.md

@@ -1,6 +1,6 @@
 # Continue-Here Template
 
-Copy and fill this structure for `.planning/phases/XX-name/.continue-here.md`:
+Copy and fill this structure for `.ariadna_planning/phases/XX-name/.continue-here.md`:
 
 ```yaml
 ---

data/data/ariadna/templates/debug-subagent-prompt.md

@@ -27,7 +27,7 @@ goal: {find_root_cause_only | find_and_fix}
 </mode>
 
 <debug_file>
-Create: .planning/debug/{slug}.md
+Create: .ariadna_planning/debug/{slug}.md
 </debug_file>
 ```
 
@@ -77,7 +77,7 @@ Continue debugging {slug}. Evidence is in the debug file.
 </objective>
 
 <prior_state>
-Debug file: @.planning/debug/{slug}.md
+Debug file: @.ariadna_planning/debug/{slug}.md
 </prior_state>
 
 <checkpoint_response>

data/data/ariadna/templates/discovery.md

@@ -1,6 +1,6 @@
 # Discovery Template
 
-Template for `.planning/phases/XX-name/DISCOVERY.md` - shallow research for library/option decisions.
+Template for `.ariadna_planning/phases/XX-name/DISCOVERY.md` - shallow research for library/option decisions.
 
 **Purpose:** Answer "which library/option should we use" questions during mandatory discovery in plan-phase.
 
@@ -71,7 +71,7 @@ Before completing discovery, verify:
 
 
 <output_structure>
-Create `.planning/phases/XX-name/DISCOVERY.md`:
+Create `.ariadna_planning/phases/XX-name/DISCOVERY.md`:
 
 ```markdown
 # [Topic] Discovery

data/data/ariadna/templates/milestone-archive.md

@@ -1,6 +1,6 @@
 # Milestone Archive Template
 
-This template is used by the complete-milestone workflow to create archive files in `.planning/milestones/`.
+This template is used by the complete-milestone workflow to create archive files in `.ariadna_planning/milestones/`.
 
 ---
 
@@ -89,7 +89,7 @@ Plans:
 
 ---
 
-_For current project status, see .planning/ROADMAP.md_
+_For current project status, see .ariadna_planning/ROADMAP.md_
 
 ---
 
@@ -112,8 +112,8 @@ _For current project status, see .planning/ROADMAP.md_
 
 **Archive location:**
 
-- Save to `.planning/milestones/v{VERSION}-{NAME}.md`
-- Example: `.planning/milestones/v1.0-mvp.md`
+- Save to `.ariadna_planning/milestones/v{VERSION}-{NAME}.md`
+- Example: `.ariadna_planning/milestones/v1.0-mvp.md`
 
 **After archiving:**
 

data/data/ariadna/templates/milestone.md

@@ -1,6 +1,6 @@
 # Milestone Entry Template
 
-Add this entry to `.planning/MILESTONES.md` when completing a milestone:
+Add this entry to `.ariadna_planning/MILESTONES.md` when completing a milestone:
 
 ```markdown
 ## v[X.Y] [Name] (Shipped: YYYY-MM-DD)

data/data/ariadna/templates/phase-prompt.md

@@ -3,7 +3,7 @@
 > **Note:** Planning methodology is in `agents/ariadna-planner.md`.
 > This template defines the PLAN.md output format that the agent produces.
 
-Template for `.planning/phases/XX-name/{phase}-{plan}-PLAN.md` - executable phase plans optimized for parallel execution.
+Template for `.ariadna_planning/phases/XX-name/{phase}-{plan}-PLAN.md` - executable phase plans optimized for parallel execution.
 
 **Naming:** Use `{phase}-{plan}-PLAN.md` format (e.g., `01-02-PLAN.md` for Phase 1, Plan 2)
 
@@ -46,9 +46,9 @@ Output: [What artifacts will be created]
 </execution_context>
 
 <context>
-@.planning/PROJECT.md
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/STATE.md
 
 # Only reference prior plan SUMMARYs if genuinely needed:
 # - This plan uses types/exports from prior plan
@@ -114,7 +114,7 @@ Before declaring plan complete:
   </success_criteria>
 
 <output>
-After completion, create `.planning/phases/XX-name/{phase}-{plan}-SUMMARY.md`
+After completion, create `.ariadna_planning/phases/XX-name/{phase}-{plan}-SUMMARY.md`
 </output>
 ```
 
@@ -248,9 +248,9 @@ Backend plans run in Wave 1. Frontend and testing plans run in Wave 2 (parallel,
 
 ```markdown
 <context>
-@.planning/PROJECT.md
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/STATE.md
 
 # Only include SUMMARY refs if genuinely needed:
 # - This plan imports types from prior plan
@@ -267,8 +267,8 @@ Backend plans run in Wave 1. Frontend and testing plans run in Wave 2 (parallel,
 **Bad pattern (creates false dependencies):**
 ```markdown
 <context>
-@.planning/phases/03-features/03-01-SUMMARY.md  # Just because it's earlier
-@.planning/phases/03-features/03-02-SUMMARY.md  # Reflexive chaining
+@.ariadna_planning/phases/03-features/03-01-SUMMARY.md  # Just because it's earlier
+@.ariadna_planning/phases/03-features/03-02-SUMMARY.md  # Reflexive chaining
 </context>
 ```
 
@@ -355,9 +355,9 @@ Output: User model, controller, and view templates.
 </objective>
 
 <context>
-@.planning/PROJECT.md
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/STATE.md
 </context>
 
 <tasks>
@@ -389,7 +389,7 @@ Output: User model, controller, and view templates.
 </success_criteria>
 
 <output>
-After completion, create `.planning/phases/03-features/03-01-SUMMARY.md`
+After completion, create `.ariadna_planning/phases/03-features/03-01-SUMMARY.md`
 </output>
 ```
 
@@ -420,10 +420,10 @@ Output: Working dashboard controller and view.
 </execution_context>
 
 <context>
-@.planning/PROJECT.md
-@.planning/ROADMAP.md
-@.planning/phases/03-features/03-01-SUMMARY.md
-@.planning/phases/03-features/03-02-SUMMARY.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/phases/03-features/03-01-SUMMARY.md
+@.ariadna_planning/phases/03-features/03-02-SUMMARY.md
 </context>
 
 <tasks>
@@ -460,7 +460,7 @@ Output: Working dashboard controller and view.
 </success_criteria>
 
 <output>
-After completion, create `.planning/phases/03-features/03-03-SUMMARY.md`
+After completion, create `.ariadna_planning/phases/03-features/03-03-SUMMARY.md`
 </output>
 ```
 

data/data/ariadna/templates/planner-subagent-prompt.md

@@ -13,23 +13,23 @@ Template for spawning ariadna-planner agent. The agent contains all planning exp
 **Mode:** {standard | gap_closure}
 
 **Project State:**
-@.planning/STATE.md
+@.ariadna_planning/STATE.md
 
 **Roadmap:**
-@.planning/ROADMAP.md
+@.ariadna_planning/ROADMAP.md
 
 **Requirements (if exists):**
-@.planning/REQUIREMENTS.md
+@.ariadna_planning/REQUIREMENTS.md
 
 **Phase Context (if exists):**
-@.planning/phases/{phase_dir}/{phase}-CONTEXT.md
+@.ariadna_planning/phases/{phase_dir}/{phase}-CONTEXT.md
 
 **Research (if exists):**
-@.planning/phases/{phase_dir}/{phase}-RESEARCH.md
+@.ariadna_planning/phases/{phase_dir}/{phase}-RESEARCH.md
 
 **Gap Closure (if --gaps mode):**
-@.planning/phases/{phase_dir}/{phase}-VERIFICATION.md
-@.planning/phases/{phase_dir}/{phase}-UAT.md
+@.ariadna_planning/phases/{phase_dir}/{phase}-VERIFICATION.md
+@.ariadna_planning/phases/{phase_dir}/{phase}-UAT.md
 
 </planning_context>
 
@@ -98,8 +98,8 @@ Continue planning for Phase {phase_number}: {phase_name}
 </objective>
 
 <prior_state>
-Phase directory: @.planning/phases/{phase_dir}/
-Existing plans: @.planning/phases/{phase_dir}/*-PLAN.md
+Phase directory: @.ariadna_planning/phases/{phase_dir}/
+Existing plans: @.ariadna_planning/phases/{phase_dir}/*-PLAN.md
 </prior_state>
 
 <checkpoint_response>

data/data/ariadna/templates/project.md

@@ -1,6 +1,6 @@
 # PROJECT.md Template
 
-Template for `.planning/PROJECT.md` — the living project context document.
+Template for `.ariadna_planning/PROJECT.md` — the living project context document.
 
 <template>
 
@@ -173,7 +173,7 @@ STATE.md references PROJECT.md:
 ```markdown
 ## Project Reference
 
-See: .planning/PROJECT.md (updated [date])
+See: .ariadna_planning/PROJECT.md (updated [date])
 
 **Core value:** [One-liner from Core Value section]
 **Current focus:** [Current phase name]

data/data/ariadna/templates/requirements.md

@@ -1,6 +1,6 @@
 # Requirements Template
 
-Template for `.planning/REQUIREMENTS.md` — checkable requirements that define "done."
+Template for `.ariadna_planning/REQUIREMENTS.md` — checkable requirements that define "done."
 
 <template>
 

data/data/ariadna/templates/research-project/ARCHITECTURE.md

@@ -1,6 +1,6 @@
 # Architecture Research Template
 
-Template for `.planning/research/ARCHITECTURE.md` — Rails application architecture discovery for the project.
+Template for `.ariadna_planning/research/ARCHITECTURE.md` — Rails application architecture discovery for the project.
 
 <template>
 

data/data/ariadna/templates/research-project/FEATURES.md

@@ -1,6 +1,6 @@
 # Features Research Template
 
-Template for `.planning/research/FEATURES.md` — feature landscape for the project domain.
+Template for `.ariadna_planning/research/FEATURES.md` — feature landscape for the project domain.
 
 <template>
 

data/data/ariadna/templates/research-project/PITFALLS.md

@@ -1,6 +1,6 @@
 # Pitfalls Research Template
 
-Template for `.planning/research/PITFALLS.md` — common mistakes to avoid in Ruby on Rails applications.
+Template for `.ariadna_planning/research/PITFALLS.md` — common mistakes to avoid in Ruby on Rails applications.
 
 <template>
 

data/data/ariadna/templates/research-project/STACK.md

@@ -1,6 +1,6 @@
 # Stack Research Template
 
-Template for `.planning/research/STACK.md` — discovered technology stack for the Rails project.
+Template for `.ariadna_planning/research/STACK.md` — discovered technology stack for the Rails project.
 
 <template>