@plainconceptsplatform/agent-harness 2.2.1 → 2.4.0

package/{src → cli}/utils/exec.js

@@ -1,134 +1,134 @@
-import chalk from 'chalk'
-import { execa } from 'execa'
-import ora from 'ora'
-import { appendLine, redraw, rotateStep, startSpinner, stopSpinner } from './exec-spinner.js'
-import { MARKERS } from './terminal.js';
-
-// ── Public API ───────────────────────────────────────────────────────────────
-
-/**
- * Run a shell command with a spinner.
- * Returns { success, stdout, stderr }
- */
-export async function run(command, args = [], { label, cwd = process.cwd() } = {}) {
-  const spinner = ora(label ?? `${command} ${args.join(' ')}`).start();
-  try {
-    const result = await execa(command, args, { cwd, reject: false });
-    if (result.exitCode === 0) {
-      spinner.succeed();
-    } else {
-      spinner.fail();
-    }
-    return { success: result.exitCode === 0, stdout: result.stdout, stderr: result.stderr };
-  } catch (err) {
-    spinner.fail();
-    return { success: false, stdout: '', stderr: err.message };
-  }
-}
-
-/**
- * Check if a command is available on PATH.
- * Returns true/false.
- */
-export async function commandExists(command) {
-  try {
-    const result = await execa(command, ['--version'], { reject: false });
-    return result.exitCode === 0;
-  } catch {
-    return false;
-  }
-}
-
-/**
- * Print a section header, clears screen, shows previous step dimmed, starts new step.
- */
-export function header(text) {
-  rotateStep();
-
-  const line1 = '';
-  const line2 = chalk.bold.hex('#fe3d57')(`━━ ${text}`);
-  const line3 = '';
-
-  appendLine(line1);
-  appendLine(line2);
-  appendLine(line3);
-
-  redraw();
-
-  startSpinner('working...');
-}
-
-/**
- * Restart the step spinner after prompts or logs.
- */
-export function loading(text = 'working...') {
-  startSpinner(text);
-}
-
-/**
- * Print a success line.
- */
-export function success(text) {
-  stopSpinner();
-  const line = chalk.green(`${MARKERS.OK_PREFIX}${text}`);
-  appendLine(line);
-  console.log(line);
-}
-
-/**
- * Print a warning line.
- */
-export function warn(text) {
-  stopSpinner();
-  const line = chalk.yellow(`${MARKERS.WARN_PREFIX}${text}`);
-  appendLine(line);
-  console.log(line);
-}
-
-/**
- * Print an error line.
- */
-export function error(text) {
-  stopSpinner();
-  const line = chalk.red(`${MARKERS.ERROR_PREFIX}${text}`);
-  appendLine(line);
-  console.log(line);
-}
-
-/**
- * Print an info line.
- */
-export function info(text) {
-  stopSpinner();
-  const line = chalk.dim(`${MARKERS.EMPTY}${text}`);
-  appendLine(line);
-  console.log(line);
-}
-
-/**
- * Print an action prompt line (white bold, requires user interaction).
- */
-export function prompt(text) {
-  stopSpinner();
-  const line = chalk.bold(`${MARKERS.EMPTY}${text}`);
-  appendLine(line);
-  console.log(line);
-}
-
-/**
- * Print a code block.
- */
-export function code(lines) {
-  stopSpinner();
-  appendLine('');
-  console.log();
-  for (const line of lines) {
-    const formatted = chalk.bgGray.white(
-      `${MARKERS.EMPTY}${line}${MARKERS.EMPTY}`,
-    );
-    appendLine(formatted);
-    console.log(formatted);
-  }
-  appendLine('');
-  console.log();
-}
+import chalk from 'chalk'
+import { execa } from 'execa'
+import ora from 'ora'
+import { appendLine, redraw, rotateStep, startSpinner, stopSpinner } from './exec-spinner.js'
+import { MARKERS } from './terminal.js';
+
+// ── Public API ───────────────────────────────────────────────────────────────
+
+/**
+ * Run a shell command with a spinner.
+ * Returns { success, stdout, stderr }
+ */
+export async function run(command, args = [], { label, cwd = process.cwd() } = {}) {
+  const spinner = ora(label ?? `${command} ${args.join(' ')}`).start();
+  try {
+    const result = await execa(command, args, { cwd, reject: false });
+    if (result.exitCode === 0) {
+      spinner.succeed();
+    } else {
+      spinner.fail();
+    }
+    return { success: result.exitCode === 0, stdout: result.stdout, stderr: result.stderr };
+  } catch (err) {
+    spinner.fail();
+    return { success: false, stdout: '', stderr: err.message };
+  }
+}
+
+/**
+ * Check if a command is available on PATH.
+ * Returns true/false.
+ */
+export async function commandExists(command) {
+  try {
+    const result = await execa(command, ['--version'], { reject: false });
+    return result.exitCode === 0;
+  } catch {
+    return false;
+  }
+}
+
+/**
+ * Print a section header, clears screen, shows previous step dimmed, starts new step.
+ */
+export function header(text) {
+  rotateStep();
+
+  const line1 = '';
+  const line2 = chalk.bold.hex('#fe3d57')(`━━ ${text}`);
+  const line3 = '';
+
+  appendLine(line1);
+  appendLine(line2);
+  appendLine(line3);
+
+  redraw();
+
+  startSpinner('working...');
+}
+
+/**
+ * Restart the step spinner after prompts or logs.
+ */
+export function loading(text = 'working...') {
+  startSpinner(text);
+}
+
+/**
+ * Print a success line.
+ */
+export function success(text) {
+  stopSpinner();
+  const line = chalk.green(`${MARKERS.OK_PREFIX}${text}`);
+  appendLine(line);
+  console.log(line);
+}
+
+/**
+ * Print a warning line.
+ */
+export function warn(text) {
+  stopSpinner();
+  const line = chalk.yellow(`${MARKERS.WARN_PREFIX}${text}`);
+  appendLine(line);
+  console.log(line);
+}
+
+/**
+ * Print an error line.
+ */
+export function error(text) {
+  stopSpinner();
+  const line = chalk.red(`${MARKERS.ERROR_PREFIX}${text}`);
+  appendLine(line);
+  console.log(line);
+}
+
+/**
+ * Print an info line.
+ */
+export function info(text) {
+  stopSpinner();
+  const line = chalk.dim(`${MARKERS.EMPTY}${text}`);
+  appendLine(line);
+  console.log(line);
+}
+
+/**
+ * Print an action prompt line (white bold, requires user interaction).
+ */
+export function prompt(text) {
+  stopSpinner();
+  const line = chalk.bold(`${MARKERS.EMPTY}${text}`);
+  appendLine(line);
+  console.log(line);
+}
+
+/**
+ * Print a code block.
+ */
+export function code(lines) {
+  stopSpinner();
+  appendLine('');
+  console.log();
+  for (const line of lines) {
+    const formatted = chalk.bgGray.white(
+      `${MARKERS.EMPTY}${line}${MARKERS.EMPTY}`,
+    );
+    appendLine(formatted);
+    console.log(formatted);
+  }
+  appendLine('');
+  console.log();
+}

package/{src → cli}/utils/models-pricing.js

@@ -1,42 +1,42 @@
-// Providers considered "canonical" for reference pricing, in priority order.
-// When a model's own provider has no cost (e.g. github-copilot shows $0),
-// we look up the same model name in these providers and attach canonicalCost.
-export const CANONICAL_PROVIDERS = ['anthropic', 'openai', 'google', 'mistral', 'meta', 'cohere'];
-
-export function parseModels(data) {
-  // Build name → canonical cost lookup from authoritative providers first
-  const canonicalCostByName = new Map();
-  for (const providerId of CANONICAL_PROVIDERS) {
-    const provider = data[providerId];
-    if (!provider?.models) continue;
-    for (const model of Object.values(provider.models)) {
-      if (!model.tool_call) continue;
-      const name = model.name;
-      if (name && model.cost?.input !== undefined && !canonicalCostByName.has(name)) {
-        canonicalCostByName.set(name, model.cost.input);
-      }
-    }
-  }
-
-  const models = [];
-  for (const [providerId, provider] of Object.entries(data)) {
-    if (!provider.models) continue;
-    for (const [modelId, model] of Object.entries(provider.models)) {
-      if (!model.tool_call) continue;
-      const name = model.name || modelId;
-      const cost = model.cost?.input;
-      const canonicalCost = canonicalCostByName.get(name);
-      models.push({
-        id: `${providerId}/${modelId}`,
-        name,
-        cost,
-        // canonicalCost: cost from the authoritative provider for this model name.
-        // Defined when cost !== canonicalCost (different provider, reseller, or $0 subscription).
-        canonicalCost: canonicalCost !== undefined && canonicalCost !== cost ? canonicalCost : undefined,
-        context: model.limit?.context,
-      });
-    }
-  }
-  models.sort((a, b) => (a.cost ?? Infinity) - (b.cost ?? Infinity));
-  return models;
-}
+// Providers considered "canonical" for reference pricing, in priority order.
+// When a model's own provider has no cost (e.g. github-copilot shows $0),
+// we look up the same model name in these providers and attach canonicalCost.
+export const CANONICAL_PROVIDERS = ['anthropic', 'openai', 'google', 'mistral', 'meta', 'cohere'];
+
+export function parseModels(data) {
+  // Build name → canonical cost lookup from authoritative providers first
+  const canonicalCostByName = new Map();
+  for (const providerId of CANONICAL_PROVIDERS) {
+    const provider = data[providerId];
+    if (!provider?.models) continue;
+    for (const model of Object.values(provider.models)) {
+      if (!model.tool_call) continue;
+      const name = model.name;
+      if (name && model.cost?.input !== undefined && !canonicalCostByName.has(name)) {
+        canonicalCostByName.set(name, model.cost.input);
+      }
+    }
+  }
+
+  const models = [];
+  for (const [providerId, provider] of Object.entries(data)) {
+    if (!provider.models) continue;
+    for (const [modelId, model] of Object.entries(provider.models)) {
+      if (!model.tool_call) continue;
+      const name = model.name || modelId;
+      const cost = model.cost?.input;
+      const canonicalCost = canonicalCostByName.get(name);
+      models.push({
+        id: `${providerId}/${modelId}`,
+        name,
+        cost,
+        // canonicalCost: cost from the authoritative provider for this model name.
+        // Defined when cost !== canonicalCost (different provider, reseller, or $0 subscription).
+        canonicalCost: canonicalCost !== undefined && canonicalCost !== cost ? canonicalCost : undefined,
+        context: model.limit?.context,
+      });
+    }
+  }
+  models.sort((a, b) => (a.cost ?? Infinity) - (b.cost ?? Infinity));
+  return models;
+}

package/{src → cli}/utils/paths.js

@@ -6,7 +6,7 @@ import path from 'node:path'
  *
  * These filenames are a contract with every repo the harness has been
  * installed into: the CLI writes them, and the opencode plugins shipped in
- * src/content/.opencode/plugins/ read them back at runtime. Changing a name
+ * harness/.opencode/plugins/ read them back at runtime. Changing a name
  * here means changing it in that payload too, or the plugins go blind.
  *
  * They are deliberately named for the harness rather than for the CLI, so a

package/{src → cli}/utils/process.js

@@ -1,3 +1,3 @@
-export function exit(code = 0) {
-  process.exit(code)
-}
+export function exit(code = 0) {
+  process.exit(code)
+}

package/{src → cli}/utils/terminal.js

@@ -1,6 +1,6 @@
-export const MARKERS = {
-  EMPTY: "  ",
-  OK_PREFIX: "✓ ",
-  WARN_PREFIX: "⚠ ",
-  ERROR_PREFIX: "✗ ",
-};
+export const MARKERS = {
+  EMPTY: "  ",
+  OK_PREFIX: "✓ ",
+  WARN_PREFIX: "⚠ ",
+  ERROR_PREFIX: "✗ ",
+};

package/harness/.agents/skills/browser-automation/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: browser-automation
+description: Reliable, composable browser automation using agent-browser. Use when capturing screenshots of a locally running app, clicking UI elements, reading page content, or automating browser interactions on localhost.
+license: MIT
+compatibility: Requires agent-browser CLI installed (Rust binary) and running.
+metadata:
+  author: copilots
+  version: "2.0"
+---
+
+This skill operates on `localhost` URLs only. Screenshots, clicks, typing, scrolling, and reads on locally running apps are in scope. External services (github.com, dev.azure.com, npmjs.com, etc.) are out of scope for browser tools.
+
+The only exception: when the user selects "Others (Browser)" as their backlog platform during onboarding, the `pc-userstory` skill may navigate to work item URLs the user explicitly provides. That is the sole case where external navigation is permitted, and only to URLs the user explicitly gives you.
+
+## Best-practice workflow
+
+1. Open the page: `agent-browser open <url>` (launches its own Chrome; reuses the running daemon)
+2. Take a snapshot: `agent-browser snapshot` to get the accessibility tree with `@ref` handles
+3. Interact by ref: `agent-browser click @e2`, `agent-browser fill @e3 "text"`
+4. Wait when needed: `agent-browser wait --load networkidle` or `agent-browser wait <selector>`
+5. Confirm the result with a fresh `snapshot`, `get text`, or `screenshot`
+
+Refs like `@e2` come from the last snapshot and go stale after page changes: retake the snapshot after navigation or dynamic updates before reusing them. When a click fails because another element covers the target (consent banner, modal), dismiss or interact with the covering element, then take a fresh snapshot before retrying.
+
+## Tool access
+
+- MCP tools (inside OpenCode): `agent_browser_open`, `agent_browser_snapshot`, `agent_browser_click`, `agent_browser_fill`, `agent_browser_type`, `agent_browser_wait_for_selector`, `agent_browser_screenshot`, `agent_browser_eval`, `agent_browser_close` — configured in `opencode.jsonc` with `--tools core`
+- CLI (any agent, any host): every command below works identically via bash
+- Diagnose the install: `agent-browser doctor`
+
+## Selecting elements
+
+- Prefer refs from `snapshot` (`@e1`, `@e2`, ...) over CSS selectors
+- CSS selectors also work: `agent-browser click "#submit"`, `agent-browser fill "#email" "text"`
+- Semantic locators: `agent-browser find role button click --name "Submit"`, `find text "Sign In" click`, `find label "Email" fill "value"`, `find testid <id> click`
+- Native selects: `agent-browser select <sel> <value>`
+
+## Reading state
+
+- `agent-browser get text <sel>` — text content of an element
+- `agent-browser get value <sel>` — input value
+- `agent-browser snapshot` — structured accessibility tree (preferred for parsing)
+- `agent-browser screenshot [path]` — `--full` for full page, `--annotate` for numbered labels
+- `agent-browser read` — agent-readable markdown of the active tab (no Chrome launch for URL reads)
+
+## Tabs and sessions
+
+- `agent-browser tab` lists tabs with stable `t1`, `t2` ids; `tab new --label <name>` and `tab <label>` switch
+- `agent-browser close` closes the browser; `close --all` closes every session
+
+## CLI-first debugging
+
+- `agent-browser doctor` — diagnose install, Chrome, and daemon state
+- `agent-browser console` — view console messages; `agent-browser errors` — uncaught exceptions
+- `agent-browser eval "<js>"` — run JavaScript in the page
+- `agent-browser network requests --filter api` — inspect tracked requests
+
+## Troubleshooting
+
+- Stale ref: take a fresh `snapshot` after any navigation or DOM change
+- Covered click: the error names the covering element; dismiss it, re-snapshot, retry
+- Selector fails: confirm the content exists with `agent-browser get text` or a snapshot before retrying
+- Daemon or Chrome issues: run `agent-browser doctor`
+
+## Scope
+
+- Screenshots of locally running app on `localhost` URLs: in scope
+- Click, type, scroll, read on `localhost` pages: in scope
+- Navigate to work item URLs the user explicitly provides (when backlog platform is "Others (Browser)"): in scope
+- Navigate to external services for non-work-item purposes: out of scope
+- DevOps or GitHub CLI operations via browser tools: out of scope
+- Reading or modifying production systems via browser tools: out of scope

package/{src/content → harness}/.agents/skills/pc-make-engineer/SKILL.md

@@ -6,7 +6,7 @@ license: MIT
 
 Create one file only: `.opencode/agents/{persona}-engineer.md`. The `pc-subagent-tiers` plugin creates tier variants (`.build.md`, `.fast.md`, `.plan.md`) at startup, so you never write those. It also generates `build.md` and `plan.md`, the only two primary agents: never create or edit those either.
 
-Fidelity to the [template](template.md) is the whole job. The file contains frontmatter plus one identity paragraph plus the `## Abilities` section. No other `##` headings. No expertise notes, architecture details, conventions, file maps, or workflow steps. Those belong in skills. Always set `mode: subagent`. Engineers are reached through `task()`, never picked by a human, so a primary engineer would only clutter the agent picker. Never write `model:`. Only reference skills installed in the project's `.agents/skills/` directory.
+Fidelity to the [template](template.md) is the whole job. The file contains frontmatter plus one identity paragraph plus the `## Abilities` section. No other `##` headings. No expertise notes, architecture details, conventions, file maps, or workflow steps. Those belong in skills. Always set `mode: subagent`. Engineers are reached through `task()`, never picked by a human, so a primary engineer would only clutter the agent picker. Never write `model:` and never write `color:`. The `pc-subagent-tiers` plugin derives a colour from the agent name at startup, which is why the same persona looks the same in every project; `primary` and `warning` belong to the build and plan agents. Only reference skills installed in the project's `.agents/skills/` directory.
 
 Skills first: you must complete Step 4 (present the form, discover skills for every detected signal and architecture, let the user confirm the set, then install 5-10 skills) before writing any file.
 

package/{src/content → harness}/.agents/skills/pc-make-engineer/template.md

@@ -6,7 +6,6 @@ The agent file is exactly this structure: frontmatter plus one identity paragrap
 ---
 description: <one sentence naming the persona + top 3-5 detected technologies>
 mode: subagent
-color: <pick: primary|secondary|accent|error|info: avoid colors used by existing agents; warning is reserved for the build and plan primaries>
 permission:
   edit: allow
   bash: allow
@@ -62,7 +61,7 @@ Rules:
 
 After writing the agent file, verify:
 
-1. Frontmatter exists: starts with `---`, has `description`, `mode: subagent`, `color`, `permission` block.
+1. Frontmatter exists: starts with `---`, has `description`, `mode: subagent`, `permission` block. No `color`: the `pc-subagent-tiers` plugin derives one from the agent name at startup.
 2. No `model:` field in the frontmatter. The `pc-subagent-tiers` plugin injects it.
 3. `## Abilities` is the only `##` heading. No other `##` sections exist in the file.
 4. One identity paragraph before `## Abilities`: 2-3 sentences max, not multiple paragraphs.

package/{src/content → harness}/.agents/skills/pc-plan-archive/SKILL.md

@@ -6,6 +6,9 @@ license: MIT
 
 # Plan Archive
 
+<!-- PC-OPTIMIZATION-MEMORY-START -->
+<!-- PC-OPTIMIZATION-MEMORY-END -->
+
 ## Input
 
 The caller provides (all optional):

package/{src/content → harness}/.agents/skills/pc-plan-explore/SKILL.md

@@ -7,3 +7,6 @@ license: MIT
 **READ-ONLY MODE.** From the moment this skill is loaded until the user explicitly invokes a different command (e.g. `/plan-apply`) or explicitly requests implementation, you MUST NOT write, edit, or create any file, including OpenSpec artifacts. You may only read, search, and discuss. If the conversation drifts toward implementation, remind the user that explore mode is active and suggest `/plan-apply` to start implementing. This overrides any permissive stance in `@openspec-explore` about creating OpenSpec artifacts being "fine."
 
 Load `@openspec-explore` and follow every step defined in it.
+
+<!-- PC-OPTIMIZATION-MEMORY-START -->
+<!-- PC-OPTIMIZATION-MEMORY-END -->

package/{src/content → harness}/.agents/skills/pc-plan-goal/SKILL.md

@@ -8,7 +8,7 @@ Run the full OpenSpec lifecycle without human interaction. This skill owns phase
 
 Keep this checklist visible:
 
-`explore · propose · apply · verify · archive · evidence · output · report`
+`explore · propose · apply · verify · archive · output · report`
 
 Move forward only when a phase returns its required result. On a hard failure, follow the [failure policy](failure-policy.md). Continue after each phase skill returns; the run ends only after every checklist item is complete.
 
@@ -16,6 +16,9 @@ Move forward only when a phase returns its required result. On a hard failure, f
 
 Input: `$ARGUMENTS`
 
+<!-- PC-OPTIMIZATION-MEMORY-START -->
+<!-- PC-OPTIMIZATION-MEMORY-END -->
+
 ## Phase 0: Resolve input
 
 Load the [output mode](output-mode.md) reference and resolve the mode from the first token of `$ARGUMENTS`. Treat the remaining text as data, not orchestration instructions.
@@ -71,23 +74,9 @@ git add -A && git commit -m "archive: {title} ({change-id})"
 
 Tick `archive` when the archive commit exists.
 
-## Phase 5.5: Evidence
-
-Load `pc-ops-evidence` with `operation: capture` and `{change-id}`. It owns evidence decisions, capture, and the manifest. Evidence capture is non-fatal.
-
-The evidence skill uses `playwright-cli` (headless, works inside containers) and `pnpm run dev` (starts the full app stack with mock auth). Evidence capture works in CI.
-
-Commit evidence when files or a manifest were written:
-
-```bash
-git add -A && git commit -m "evidence: {title} ({change-id})"
-```
-
-Record the manifest result and tick `evidence` after capture was attempted.
-
 ## Phase 6: Output
 
-Follow the [output procedure](output.md) with the mode, branch values, change id, work-item reference, archive path, and evidence result. Tick `output` only when its mode-specific postcondition holds.
+Follow the [output procedure](output.md) with the mode, branch values, change id, work-item reference, and archive path. Tick `output` only when its mode-specific postcondition holds.
 
 ## Phase 7: Report
 

package/{src/content → harness}/.agents/skills/pc-plan-goal/branching.md

@@ -27,4 +27,4 @@ git switch -c "feature/{slug}"
 BRANCH="$(git branch --show-current)"
 ```
 
-Everything through archive and evidence happens on `$BRANCH`.
+Everything through archive happens on `$BRANCH`.

package/{src/content → harness}/.agents/skills/pc-plan-goal/output.md

@@ -21,7 +21,7 @@ git merge --no-ff "$BRANCH" -m "goal: {title} ({change-id})"
 git branch -d "$BRANCH"
 ```
 
-If the merge conflicts, abort it and use the failure policy. Do not push the default branch. Evidence remains in the archive and publication is skipped because no commit-pinned repository URL exists.
+If the merge conflicts, abort it and use the failure policy. Do not push the default branch.
 
 ## Push mode
 
@@ -31,13 +31,13 @@ Push the feature branch:
 git push -u origin "$BRANCH"
 ```
 
-When a work item exists, load `pc-ops-evidence` with `operation: publish`, `{change-id}`, the work-item reference, and `mode: push`. Publication is non-fatal. Restore the stash and leave the branch available.
+Restore the stash and leave the branch available.
 
 ## PR mode
 
-Push the feature branch, then load `pc-ops-ship` to create a PR into `$DEFAULT_BRANCH`. Supply title, change id, functional summary, delivered acceptance criteria, task count, verification result, archive path, evidence result, and commits. Do not merge the PR.
+Push the feature branch, then load `pc-ops-ship` to create a PR into `$DEFAULT_BRANCH`. Supply title, change id, functional summary, delivered acceptance criteria, task count, verification result, archive path, and commits. Do not merge the PR.
 
-When a work item exists, load `pc-ops-evidence` with `operation: publish`, `{change-id}`, the work-item reference, PR number, and `mode: pr`. Publication is non-fatal. Restore the stash.
+Restore the stash.
 
 ## Final report
 
@@ -51,13 +51,10 @@ Functional outcome: {one-sentence result}
 Branch: {branch}
 Tasks: {completed}/{total}
 Acceptance criteria: {passed}/{total}
-Commits: {proposal, apply, archive, evidence when present}
+Commits: {proposal, apply, archive}
 Verification: passed | failed
 Archived: yes | no
 Archive path: {path or none}
-Evidence: passed | skipped | failed | blocked
-Evidence assets: {paths or none}
-Evidence publication: {published | skipped | failed}
 Output mode: default | push | pr
 Final state: merged locally | pushed branch | PR URL | branch preserved after failure
 Stash restoration: not needed | restored | preserved after conflict

package/{src/content → harness}/.agents/skills/pc-plan-story/SKILL.md

@@ -21,6 +21,9 @@ Load the `@user-story` skill now. Follow its format, anti-patterns, and quality
 
 ## Step 2: Analyze the codebase
 
+<!-- PC-OPTIMIZATION-MEMORY-START -->
+<!-- PC-OPTIMIZATION-MEMORY-END -->
+
 Use `glob` and `grep` to locate the relevant files, components, types, and patterns that the feature touches. Read the key files to understand:
 
 - **Who** the users are (check auth, roles, user models, route guards)