docs(prompts): align Spark command templates to canonical .documentation paths

Replace non-canonical guide path references and fix command template path guidance.

Standardize constitution prompt guidance across source and initialized repo layouts for consistent Spec Kit Spark behavior.

Author: markhazleton

templates/commands/constitution.md

@@ -41,11 +41,11 @@ Follow this execution flow:
    - Ensure Governance section lists amendment procedure, versioning policy, and compliance review expectations.
 
 4. Consistency propagation checklist (convert prior checklist into active validations):
-   - Read `/.documentation/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
-   - Read `/.documentation/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
-   - Read `/.documentation/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
-   - Read each command file in `/.documentation/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
-   - Read any runtime guidance docs (e.g., `README.md`, `.documentation/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
+   - Read `/.documentation/templates/plan-template.md` (or `templates/plan-template.md` in source repos) and ensure any "Constitution Check" or rules align with updated principles.
+   - Read `/.documentation/templates/spec-template.md` (or `templates/spec-template.md` in source repos) for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
+   - Read `/.documentation/templates/tasks-template.md` (or `templates/tasks-template.md` in source repos) and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
+   - Read command prompt templates from `templates/commands/*.md` when available; otherwise inspect generated command files under active agent folders (for example `.github/agents/`, `.claude/commands/`, `.cursor/commands/`, `.gemini/commands/`). Verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
+   - Read runtime guidance docs (for example `README.md`, `/.documentation/Guide.md`, and agent-specific guidance files if present). Update references to principles changed.
 
 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):
    - Version change: old → new

templates/commands/harvest.md

@@ -26,7 +26,7 @@ Harvest valuable knowledge from completed specs, stale documentation, and in-pro
 
 This command is a **knowledge-preserving cleanup** workflow:
 
-1. Preserve durable knowledge in living documents such as `CHANGELOG.md`, `/.documentation/guides/`, and `/.github/copilot-instructions.md`
+1. Preserve durable knowledge in living documents such as `CHANGELOG.md`, `/.documentation/Guide.md`, and `/.github/copilot-instructions.md`
 2. Rewrite source code comments that reference completed specs, plans, or tasks into self-contained explanations
 3. Move stale artifacts into `/.archive/` while preserving directory structure
 4. Produce a harvest report at `/.documentation/copilot/harvest-YYYY-MM-DD.md`