refactor: Update agent path references for core-workspace split (Task 2)

- Updated all agent instruction files to use new path conventions
- Template paths: .devagent/agents/ → .devagent/core/agents/
- Template paths: .devagent/templates/ → .devagent/core/templates/
- Working paths: .devagent/product/ → .devagent/workspace/product/
- Working paths: .devagent/memory/ → .devagent/workspace/memory/
- Working paths: .devagent/features/ → .devagent/workspace/features/
- Working paths: .devagent/research/ → .devagent/workspace/research/

Files updated (11):
- AgentBuilder.md
- FeatureBrainstormAgent.md
- FeatureClarifyAgent.md
- ProductMissionPartner.md
- ResearchAgent.md
- SpecArchitect.md
- TaskExecutor.md
- TaskPlanner.md
- TechStackAgent.md
- UpdateConstitution.md
- codegen/CodegenBackgroundAgent.md

Validation: grep confirmed no old path patterns remain in agent files

Co-authored-by: Jake Ruesink <jaruesink@gmail.com>

Author: codegen-sh[bot]

.devagent/core/agents/AgentBuilder.md

@@ -16,14 +16,14 @@
 - Clarify usage patterns, optional approval gates, and escalation paths so teams can wire resources into their own environments without assuming extra roles.
 
 ## Knowledge Sources
-- Internal: `.devagent/agents/`, `.devagent/product/`, `.devagent/templates/`, `.devagent/README.md`.
+- Internal: `.devagent/core/agents/`, `.devagent/workspace/product/`, `.devagent/core/templates/`, `.devagent/README.md`.
 - External: Context7 library docs for tooling references, Exa search for industry examples when inputs are sparse.
 - Retrieval etiquette: Reuse existing patterns when agents share responsibilities; cite new research in `guiding-questions.md` if the source is tentative.
 
 ## Workflow
 1. Kickoff: Confirm mission statement and desired outputs.
 2. Context gathering: Review existing agents and relevant product artifacts to avoid overlap.
-3. Outline: Start from `.devagent/templates/agent-brief-template.md`, note sections to keep, drop, or customize, and capture any new module needs.
+3. Outline: Start from `.devagent/core/templates/agent-brief-template.md`, note sections to keep, drop, or customize, and capture any new module needs.
 4. Drafting: Fill each section (Mission, Inputs, Resource Strategy, Knowledge, Workflow, Adaptation, Failure modes, Outputs) with project-specific detail.
 5. Validation: Cross-check for completeness, guardrail coverage, and alignment with the constitution clauses.
 6. Packaging: Save/update the agent doc, summarize changes, and note follow-ups in `guiding-questions.md` if needed.
@@ -37,8 +37,8 @@
 - Surface conflicts with existing agents (duplicated mission or overlapping scope) and request direction before proceeding.
 
 ## Expected Output
-- Markdown agent brief saved under `.devagent/agents/<AgentName>.md` using the standard template or a documented variation.
-- Updates to shared templates when the base structure evolves, committed to `.devagent/templates/`.
+- Markdown agent brief saved under `.devagent/core/agents/<AgentName>.md` using the standard template or a documented variation.
+- Updates to shared templates when the base structure evolves, committed to `.devagent/core/templates/`.
 
 ## Follow-up Hooks
 - Recommend which roster agents should review or consume the new agent (e.g., #SpecArchitect, #TaskPlanner).

.devagent/core/agents/FeatureBrainstormAgent.md

@@ -7,18 +7,18 @@
 - Invocation assumption: The executing developer has standing approval to run brainstorm sessions immediately; results are logged but don't require approval gates before proceeding to research or planning.
 
 ## Inputs
-- Required: Brainstorm topic or problem statement, desired mode (`exploratory`, `targeted`, or `expansion`), mission context (from `product/mission.md`), known constraints (technical, compliance, budget, timeline).
-- Optional: Prior brainstorm results, user feedback or pain points, competitive intelligence, specific stakeholder perspectives to explore (user, developer, business, technical), guiding questions from `product/guiding-questions.md`.
+- Required: Brainstorm topic or problem statement, desired mode (`exploratory`, `targeted`, or `expansion`), mission context (from `workspace/product/mission.md`), known constraints (technical, compliance, budget, timeline).
+- Optional: Prior brainstorm results, user feedback or pain points, competitive intelligence, specific stakeholder perspectives to explore (user, developer, business, technical), guiding questions from `workspace/product/guiding-questions.md`.
 - Request missing info by: Sending a mode-specific checklist (e.g., "Provide specific mission gap or user need for targeted mode", "Link existing feature concept for expansion mode"); if core inputs are still missing, record them as assumptions and proceed with available context, flagging gaps in the output.
 
 ## Resource Strategy
-- `.devagent/templates/brainstorm-packet-template.md` — base outline for all brainstorm outputs; duplicate and customize per mode.
-- `.devagent/product/brainstorms/` — canonical storage for brainstorm packets (format: `YYYY-MM-DD_<topic>.md`).
-- `.devagent/product/mission.md` — primary source for mission alignment and success metrics.
-- `.devagent/product/guiding-questions.md` — reference for known gaps and open questions; update with new insights from brainstorms.
-- `.devagent/memory/constitution.md` — guardrails and principles that ideas must respect; cite relevant clauses when evaluating candidates.
-- `.devagent/product/roadmap.md` — context for existing priorities and strategic themes.
-- `.devagent/memory/decision-journal.md` — log brainstorm sessions and key decision rationale.
+- `.devagent/core/templates/brainstorm-packet-template.md` — base outline for all brainstorm outputs; duplicate and customize per mode.
+- `.devagent/workspace/product/brainstorms/` — canonical storage for brainstorm packets (format: `YYYY-MM-DD_<topic>.md`).
+- `.devagent/workspace/product/mission.md` — primary source for mission alignment and success metrics.
+- `.devagent/workspace/product/guiding-questions.md` — reference for known gaps and open questions; update with new insights from brainstorms.
+- `.devagent/workspace/memory/constitution.md` — guardrails and principles that ideas must respect; cite relevant clauses when evaluating candidates.
+- `.devagent/workspace/product/roadmap.md` — context for existing priorities and strategic themes.
+- `.devagent/workspace/memory/decision-journal.md` — log brainstorm sessions and key decision rationale.
 - #ProductMissionPartner — validate mission alignment or request clarification on strategic priorities before deep ideation.
 - #ResearchAgent — hand off prioritized feature candidates with formulated research questions for evidence gathering.
 
@@ -28,7 +28,7 @@
 - **Expansion:** Take an existing feature concept and generate variations, enhancements, or alternative approaches. Explore different implementation angles, scope adjustments, and complementary capabilities. Produce a comparative evaluation of variations with recommended directions.
 
 ## Knowledge Sources
-- Internal: `.devagent/product/` artifacts (mission, roadmap, guiding-questions), `.devagent/memory/` logs (constitution, decision-journal), feature hubs for related work, existing specs and task plans for context.
+- Internal: `.devagent/workspace/product/` artifacts (mission, roadmap, guiding-questions), `.devagent/workspace/memory/` logs (constitution, decision-journal), feature hubs for related work, existing specs and task plans for context.
 - External: Industry best practices (via research tools when needed), technology trends, competitive patterns (when explicitly provided or researched).
 - Retrieval etiquette: Start with internal mission and constitution sources, cite file paths for all internal references, flag when external research would strengthen evaluation, and refresh mission context before each session.
 
@@ -51,7 +51,7 @@
    - Research questions for #ResearchAgent
    - Parking lot for lower-priority or future ideas
    - Session metadata (date, participants, constraints, assumptions)
-8. **Post-run logging:** Store brainstorm packet at `.devagent/product/brainstorms/YYYY-MM-DD_<topic>.md`, update `.devagent/memory/decision-journal.md` with session summary and key decisions, note relevant insights in `product/guiding-questions.md` if they address open questions, and prepare hand-off for downstream agents.
+8. **Post-run logging:** Store brainstorm packet at `.devagent/workspace/product/brainstorms/YYYY-MM-DD_<topic>.md`, update `.devagent/workspace/memory/decision-journal.md` with session summary and key decisions, note relevant insights in `workspace/product/guiding-questions.md` if they address open questions, and prepare hand-off for downstream agents.
 
 ## Adaptation Notes
 - **Exploratory mode** emphasizes breadth and creative diversity—encourage wild ideas and defer judgment until convergent phase. Use multiple ideation techniques to maximize idea space exploration.
@@ -69,7 +69,7 @@
   - When ideas consistently conflict with constitution: Pause ideation, review principles with session owner, consider whether mission or constitution needs updating.
 
 ## Expected Output
-- **All modes:** Markdown brainstorm packet stored in `.devagent/product/brainstorms/YYYY-MM-DD_<topic>.md` following the template structure, plus chat response summarizing top candidates and next steps.
+- **All modes:** Markdown brainstorm packet stored in `.devagent/workspace/product/brainstorms/YYYY-MM-DD_<topic>.md` following the template structure, plus chat response summarizing top candidates and next steps.
 - **Exploratory:** Full idea list with clustered themes, top 3-5 prioritized candidates with evaluation matrix, research questions for #ResearchAgent, and parking lot for future ideas.
 - **Targeted:** Solutions addressing specific criteria, comparative evaluation against constraints, recommended solution(s) with trade-off analysis, and research questions for validation.
 - **Expansion:** Feature variations with comparative analysis, recommended directions with rationale, implementation trade-offs, and suggested phasing or scoping adjustments.
@@ -81,8 +81,8 @@
   - #ProductMissionPartner — can be notified if brainstorm reveals mission gaps or strategic pivots
   - #SpecArchitect — receives validated candidates (post-research) for spec drafting
 - Integration points:
-  - Update `.devagent/product/guiding-questions.md` when brainstorm addresses or raises open questions
-  - Log session in `.devagent/memory/decision-journal.md` with key decisions and rationale
+  - Update `.devagent/workspace/product/guiding-questions.md` when brainstorm addresses or raises open questions
+  - Log session in `.devagent/workspace/memory/decision-journal.md` with key decisions and rationale
   - Cross-reference relevant constitution clauses in outputs
   - Link to related feature hubs if brainstorm extends existing work
 - Metrics / signals: Track brainstorm cadence, number of candidates progressing to research, alignment scores with mission metrics, and downstream agent rework rates (signals need for clearer outputs).

.devagent/core/agents/FeatureClarifyAgent.md

@@ -12,12 +12,12 @@
 - Request missing info by: Compile a structured gaps checklist mapped to the 8 clarification dimensions (Problem, Users, Success, Scope, Constraints, Principles, Dependencies, Acceptance), ping stakeholders with specific questions, and document unresolved items in the clarification packet for follow-up.
 
 ## Resource Strategy
-- `.devagent/templates/clarification-packet-template.md` (Clarification Packet Template) — duplicate per feature and use as the output structure.
-- `.devagent/templates/clarification-questions-framework.md` (Question Framework) — systematic question sets covering 8 requirement dimensions with ambiguity detection patterns.
-- `.devagent/templates/spec-document-template.md` (Spec Template as Checklist) — use to validate that clarified requirements cover all sections needed for spec work.
-- `.devagent/product/mission.md` — validate requirement alignment with product mission and strategic direction.
-- `.devagent/memory/constitution.md` — check requirement decisions against organizational principles.
-- `.devagent/features/YYYY-MM-DD_feature-slug/clarification/` — canonical storage location for clarification sessions and outputs.
+- `.devagent/core/templates/clarification-packet-template.md` (Clarification Packet Template) — duplicate per feature and use as the output structure.
+- `.devagent/core/templates/clarification-questions-framework.md` (Question Framework) — systematic question sets covering 8 requirement dimensions with ambiguity detection patterns.
+- `.devagent/core/templates/spec-document-template.md` (Spec Template as Checklist) — use to validate that clarified requirements cover all sections needed for spec work.
+- `.devagent/workspace/product/mission.md` — validate requirement alignment with product mission and strategic direction.
+- `.devagent/workspace/memory/constitution.md` — check requirement decisions against organizational principles.
+- `.devagent/workspace/features/YYYY-MM-DD_feature-slug/clarification/` — canonical storage location for clarification sessions and outputs.
 - #SpecArchitect — primary downstream consumer of validated requirements; escalation source for gap-filling mode.
 - #ResearchAgent — receives research questions for evidence gaps identified during clarification.
 - #ProductMissionPartner — escalation point for mission conflicts or strategic alignment questions.
@@ -144,7 +144,7 @@ Choose operating mode based on invocation context:
 ## Expected Output
 
 ### Feature Clarification Mode
-**Primary artifact:** Clarified Requirement Packet (`.devagent/features/YYYY-MM-DD_feature-slug/clarification/YYYY-MM-DD_initial-clarification.md`)
+**Primary artifact:** Clarified Requirement Packet (`.devagent/workspace/features/YYYY-MM-DD_feature-slug/clarification/YYYY-MM-DD_initial-clarification.md`)
 
 **Packet structure:**
 - Feature Overview (name, requestor, stakeholders, business context, trigger)
@@ -164,7 +164,7 @@ Choose operating mode based on invocation context:
 - Change Log (track requirement evolution)
 
 ### Gap Filling Mode
-**Primary artifact:** Gap-Fill Supplement (`.devagent/features/YYYY-MM-DD_feature-slug/clarification/YYYY-MM-DD_gap-fill-<topic>.md`)
+**Primary artifact:** Gap-Fill Supplement (`.devagent/workspace/features/YYYY-MM-DD_feature-slug/clarification/YYYY-MM-DD_gap-fill-<topic>.md`)
 
 **Supplement structure:**
 - Reference to original clarification packet
@@ -174,7 +174,7 @@ Choose operating mode based on invocation context:
 - Handoff note to escalating agent
 
 ### Requirements Review Mode
-**Primary artifact:** Validation Report (`.devagent/features/YYYY-MM-DD_feature-slug/clarification/YYYY-MM-DD_validation-report.md`)
+**Primary artifact:** Validation Report (`.devagent/workspace/features/YYYY-MM-DD_feature-slug/clarification/YYYY-MM-DD_validation-report.md`)
 
 **Report structure:**
 - Completeness score (X/8 dimensions)

.devagent/core/agents/ProductMissionPartner.md

@@ -3,33 +3,33 @@
 ## Mission
 - Primary goal: Facilitate focused working sessions that keep the DevAgent product mission current, actionable, and reflected across product artifacts in real time.
 - Boundaries / non-goals: Do not unilaterally write product strategy, commit roadmap items without required confirmation, or trigger downstream build agents. Surface gaps instead of guessing.
-- Success signals: `product/mission.md` and related artifacts updated during the session, open questions logged in `guiding-questions.md`, and the session owner confirms the mission narrative mirrors their intent.
+- Success signals: `workspace/product/mission.md` and related artifacts updated during the session, open questions logged in `guiding-questions.md`, and the session owner confirms the mission narrative mirrors their intent.
 
 ## Inputs
-- Required: Latest versions of `product/mission.md`, `product/roadmap.md`, `product/guiding-questions.md`, the current constitution clauses, and the most recent memory entries covering mission-related decisions; session owner (default: executing developer) availability; target outcomes for the working session.
+- Required: Latest versions of `workspace/product/mission.md`, `workspace/product/roadmap.md`, `workspace/product/guiding-questions.md`, the current constitution clauses, and the most recent memory entries covering mission-related decisions; session owner (default: executing developer) availability; target outcomes for the working session.
 - Optional: Recent user research notes, analytics snapshots, market intelligence, recorded transcripts from prior sessions.
 - Request missing info by: Listing the absent artifacts or unanswered questions, offering example answers (e.g., “Primary customer segment could be X or Y—please confirm”), and pausing until ownership is clarified.
 
 ## Resource Strategy
-- `product/mission.md`: Canonical baseline; read before kickoff, diff after updates to highlight changes.
-- `product/guiding-questions.md`: Capture prompts, verbatim answers, and unresolved items; rely on the “Open Follow-ups” table for continuity.
-- `.devagent/memory/decision-journal.md`: Log session summary (date, participants, key changes) before closing.
-- `.devagent/memory/constitution.md`: Review delivery principles and guardrails; adjust clause proposals only when the mission shift demands new behaviors.
-- `product/roadmap.md`: Adjust only when the mission shift demands new milestones; otherwise note “no change.”
+- `workspace/product/mission.md`: Canonical baseline; read before kickoff, diff after updates to highlight changes.
+- `workspace/product/guiding-questions.md`: Capture prompts, verbatim answers, and unresolved items; rely on the “Open Follow-ups” table for continuity.
+- `.devagent/workspace/memory/decision-journal.md`: Log session summary (date, participants, key changes) before closing.
+- `.devagent/workspace/memory/constitution.md`: Review delivery principles and guardrails; adjust clause proposals only when the mission shift demands new behaviors.
+- `workspace/product/roadmap.md`: Adjust only when the mission shift demands new milestones; otherwise note “no change.”
 - `#ResearchAgent`: Pull in when evidence backing the mission is thin or conflicting; request targeted validation tasks.
 - `#SpecArchitect`: Notify when mission updates imply spec revisions or net-new capability briefs.
 
 ## Workspace & Filing
-- Use `.devagent/product/` as the shared surface for mission context that other agents consume during planning.
+- Use `.devagent/workspace/product/` as the shared surface for mission context that other agents consume during planning.
 - Key artifacts:
   - `mission.md` — canonical product narrative (Product, Who, Problem, Why now, Solution, Metrics).
   - `roadmap.md` — milestones translating mission themes into delivery horizons.
   - `guiding-questions.md` — outstanding discovery threads earmarked for research or follow-up input.
-  - `.devagent/memory/constitution.md` — long-term guardrails the mission must honour.
+  - `.devagent/workspace/memory/constitution.md` — long-term guardrails the mission must honour.
 - Keep these documents synchronized during working sessions; when substantial shifts occur, tag downstream agents so they can pull the updated context.
 
 ## Knowledge Sources
-- Internal: `.devagent/product/` artifacts, prior working session notes, decision logs.
+- Internal: `.devagent/workspace/product/` artifacts, prior working session notes, decision logs.
 - External: Research summaries supplied by #ResearchAgent, market/competitive snapshots validated by the session owner.
 - Retrieval etiquette: Always read the most recent artifacts before a session, cite the source document when referencing data, and time-stamp new external intel in `guiding-questions.md`.
 
@@ -51,7 +51,7 @@
 - Recovery playbook: Flag the blocker in-session, document it in `guiding-questions.md`, request assistance from the session owner, and pause updates until clarity is restored.
 
 ## Expected Output
-- Artifacts: Updated `product/mission.md`, `product/roadmap.md`, appended entries in `product/guiding-questions.md`, proposed constitution updates (if any), and a new entry in `.devagent/memory/decision-journal.md`.
+- Artifacts: Updated `workspace/product/mission.md`, `workspace/product/roadmap.md`, appended entries in `workspace/product/guiding-questions.md`, proposed constitution updates (if any), and a new entry in `.devagent/workspace/memory/decision-journal.md`.
 - Communication: End-of-session summary covering key mission changes, unresolved questions, and recommended next focus areas delivered to the session owner (chat or note).
 
 ## Follow-up Hooks