docs(kiro): reconcile spec metadata, promote 3 new specs, fix template path

- config-upgrade-snapshot, raft-adapter-conformance: correct stale
  phase metadata (both showed "tasks-generated" though every task was
  already complete) and record their validate-impl GO decisions with
  known-limitations notes (bug-1471/bug-1472-remainder, bug-1474
  angle-b) for future spec ownership.
- component-failover-adoption: catch up design/requirements/research
  docs to the Phase 6 fix (bug-1548/bug-1549, commit d479b707) that
  landed after this spec was already marked closed.
- Promote 3 roadmap backlog items to specs (2026-08-10 discovery):
  component-rejoin-resync (apiserver/scheduler rejoin resync),
  worker-rejoin-resync (worker job-fact resync, hard prereq for
  raft-apply-decoupling's facts half), scheduler-sim-diagnostics
  (open-ended scheduler REPL debug/troubleshoot capability).
- roadmap.md updated to reflect all of the above.
- kiro-steering/kiro-steering-custom SKILL.md: fix stale template path
  (templates/steering/ -> .kiro/settings/templates/steering/) plus
  minor doc corrections in the other kiro-spec-* skills.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

.claude/skills/kiro-spec-design/SKILL.md

@@ -27,9 +27,9 @@ Otherwise, load all necessary context:
 - `.kiro/specs/{feature}/research.md` (if exists, contains gap analysis from `/kiro-validate-gap`)
 - Core steering context: `product.md`, `tech.md`, `structure.md`
 - Additional steering files only when directly relevant to requirement coverage, architecture boundaries, integrations, runtime prerequisites, security/performance constraints, or team conventions that affect implementation readiness
-- `templates/specs/design.md` from this skill's directory for document structure
+- `.kiro/settings/templates/specs/design.md` for document structure
 - Read `rules/design-principles.md` from this skill's directory for design principles
-- `templates/specs/research.md` from this skill's directory for discovery log structure
+- `.kiro/settings/templates/specs/research.md` for discovery log structure
 
 **Validate requirements approval**:
 - If auto-approve flag is true: Auto-approve requirements in spec.json
@@ -157,7 +157,7 @@ Provide brief summary in the language specified in spec.json:
 
 **Format**: Concise Markdown (under 200 words) - this is the command output, NOT the design document itself
 
-**Note**: The actual design document follows `templates/specs/design.md` (this skill's directory) structure.
+**Note**: The actual design document follows `.kiro/settings/templates/specs/design.md` structure.
 
 ## Safety & Fallback
 
@@ -174,7 +174,7 @@ Provide brief summary in the language specified in spec.json:
 - **Suggested Action**: "Run `/kiro-spec-requirements {feature}` to generate requirements first"
 
 **Template Missing**:
-- **User Message**: "Template file missing at `templates/specs/design.md` in this skill's directory"
+- **User Message**: "Template file missing at `.kiro/settings/templates/specs/design.md`"
 - **Suggested Action**: "Check repository setup or restore template file"
 - **Fallback**: Use inline basic structure with warning
 

.claude/skills/kiro-spec-init/SKILL.md

@@ -17,8 +17,8 @@ Generate a unique feature name from the project description ($ARGUMENTS) and ini
 3. **Check Uniqueness**: Verify `.kiro/specs/` for naming conflicts. If the directory already exists with only `brief.md` (no `spec.json`), use that directory (discovery created it).
 4. **Create Directory**: `.kiro/specs/[feature-name]/` (skip if already exists from discovery)
 5. **Initialize Files Using Templates**:
-   - Read `templates/specs/init.json` from this skill's directory
-   - Read `templates/specs/requirements-init.md` from this skill's directory
+   - Read `.kiro/settings/templates/specs/init.json`
+   - Read `.kiro/settings/templates/specs/requirements-init.md`
    - Replace placeholders:
      - `{{FEATURE_NAME}}` → generated feature name
      - `{{TIMESTAMP}}` → current ISO 8601 timestamp
@@ -46,6 +46,6 @@ Provide output in the language specified in `spec.json` with the following struc
 
 ## Safety & Fallback
 - **Ambiguous Feature Name**: If feature name generation is unclear, propose 2-3 options and ask user to select
-- **Template Missing**: If template files don't exist in this skill's `templates/specs/`, report error with specific missing file path and suggest checking skill installation
+- **Template Missing**: If template files don't exist in `.kiro/settings/templates/specs/`, report error with specific missing file path and suggest checking repository setup
 - **Directory Conflict**: If feature name already exists, append numeric suffix (e.g., `feature-name-2`) and notify user of automatic conflict resolution
 - **Write Failure**: Report error with specific path and suggest checking permissions or disk space

.claude/skills/kiro-spec-quick/SKILL.md

@@ -72,10 +72,10 @@ Execute these 4 phases in order:
 
 5. **Initialize Files from Templates**:
 
-   a. Read templates from this skill's directory:
+   a. Read templates:
    ```
-   - templates/specs/init.json
-   - templates/specs/requirements-init.md
+   - .kiro/settings/templates/specs/init.json
+   - .kiro/settings/templates/specs/requirements-init.md
    ```
 
    b. Replace placeholders:
@@ -230,7 +230,7 @@ Next Steps:
 ### Error Scenarios
 
 **Template Missing**:
-- Check `templates/specs/` in this skill's directory exists
+- Check `.kiro/settings/templates/specs/` exists
 - Report specific missing file
 - Exit with error
 

.claude/skills/kiro-spec-requirements/SKILL.md

@@ -32,7 +32,7 @@ Otherwise, load all necessary context:
 ### Step 2: Read Guidelines
 - Read `rules/ears-format.md` from this skill's directory for EARS syntax rules
 - Read `rules/requirements-review-gate.md` from this skill's directory for pre-write review criteria
-- Read `templates/specs/requirements.md` from this skill's directory for document structure
+- Read `.kiro/settings/templates/specs/requirements.md` for document structure
 
 #### Parallel Research (subagent dispatch)
 

.claude/skills/kiro-spec-tasks/SKILL.md

@@ -39,7 +39,7 @@ Otherwise, load all necessary context:
 
 - Read `rules/tasks-generation.md` from this skill's directory for principles
 - Read `rules/tasks-parallel-analysis.md` from this skill's directory for parallel judgement criteria
-- Read `templates/specs/tasks.md` from this skill's directory for format (supports `(P)` markers)
+- Read `.kiro/settings/templates/specs/tasks.md` for format (supports `(P)` markers)
 
 #### Parallel Research
 
@@ -176,9 +176,9 @@ Provide brief summary in the language specified in spec.json:
 - **Suggested Action**: "Refine requirements.md or design.md, then re-run `/kiro-spec-tasks {feature}`"
 
 **Template/Rules Missing**:
-- **User Message**: "Template or rules files missing in this skill's `templates/specs/` or `rules/` directory"
+- **User Message**: "Template or rules files missing in `.kiro/settings/`"
 - **Fallback**: Use inline basic structure with warning
-- **Suggested Action**: "Check skill installation or restore template files"
+- **Suggested Action**: "Check repository setup or restore template files"
 - **Missing Numeric Requirement IDs**:
   - **Stop Execution**: All requirements in requirements.md MUST have numeric IDs. If any requirement lacks a numeric ID, stop and request that requirements.md be fixed before generating tasks.
 

.claude/skills/kiro-steering-custom/SKILL.md

@@ -27,7 +27,7 @@ You are a specialized skill for creating custom steering documents beyond core f
 
 If steering context is already available from conversation, skip redundant file reads.
 Otherwise:
-- Check `templates/steering-custom/` in this skill's directory for available templates
+- Check `.kiro/settings/templates/steering-custom/` for available templates
 - Read `rules/steering-principles.md` from this skill's directory for steering principles
 
 ## Workflow
@@ -37,7 +37,7 @@ Otherwise:
    - Specific requirements or patterns to document
 
 2. **Check if template exists**:
-   - Load from `templates/steering-custom/{name}.md` in this skill's directory if available
+   - Load from `.kiro/settings/templates/steering-custom/{name}.md` if available
    - Use as starting point, customize based on project
 
 3. **Analyze codebase** (JIT) for relevant patterns:
@@ -60,7 +60,7 @@ After all parallel research completes, synthesize findings for steering document
 
 ## Available Templates
 
-Templates available in `templates/steering-custom/` (this skill's directory):
+Templates available in `.kiro/settings/templates/steering-custom/`:
 
 1. **api-standards.md** - REST/GraphQL conventions, error handling
 2. **testing.md** - Test organization, mocking, coverage

.claude/skills/kiro-steering/SKILL.md

@@ -30,7 +30,7 @@ You are a specialized skill for maintaining `.kiro/steering/` as persistent proj
 
 If steering context is already available from conversation, skip redundant file reads.
 
-- For Bootstrap mode: Read templates from `templates/steering/` in this skill's directory
+- For Bootstrap mode: Read templates from `.kiro/settings/templates/steering/`
 - For Sync mode: Read all existing `.kiro/steering/*.md` files
 - Read `rules/steering-principles.md` from this skill's directory for steering principles
 
@@ -45,7 +45,7 @@ Check `.kiro/steering/` status:
 
 ## Bootstrap Flow
 
-1. Load templates from `templates/steering/` in this skill's directory
+1. Load templates from `.kiro/settings/templates/steering/`
 2. Analyze codebase (JIT):
 
 #### Parallel Research