chore: reformat codebase with oxfmt

Apply prettier-compatible formatting across the repo to match the incoming oxfmt configuration. Mechanical reformat only — no logic changes. Covers YAML quote normalization, package.json key sorting, Markdown/TOML formatting, and minor TS whitespace tweaks.
2026-04-23 21:44:48 +07:00
parent 9b25f8fc36
commit ce4b0d54c7
81 changed files with 1171 additions and 1009 deletions
@@ -81,6 +81,7 @@ Do NOT edit files."
 ## If Issues Are Found

 If any final QA agent reports issues:
+
 1. Launch an impl or refactorer agent to fix them
 2. Re-run the specific QA check that failed
 3. Repeat until all checks pass
@@ -5,6 +5,7 @@ Deploy impl agents to execute the plan phase by phase. Each phase is independent
 ## TDD — Not Optional

 Every impl agent works TDD:
+
 1. Write a failing test that defines the expected behavior
 2. Make it pass
 3. Refactor if needed
@@ -17,6 +18,7 @@ If an impl agent finds a broken test, it fixes it. No "pre-existing failures." N
 Execute phases sequentially from the plan. Refactoring phases first, then feature phases, then UI passes.

 After each phase:
+
 1. Verify (see verification.md)
 2. Fix any issues found
 3. Re-verify
@@ -29,11 +31,13 @@ Use the Paseo **create agent** tool with `background: true` and `notifyOnFinish:
 ### How to describe the work

 **Describe the problem, not the solution.** Your prompt should tell the agent:
+
 - What's wrong or what needs to be built (the goal)
 - How it currently fails (error output, test output, user-visible behavior)
 - The acceptance criteria (what "done" looks like)

 **Do NOT tell the agent:**
+
 - Which specific lines to change
 - What code to write
 - Which functions to call or which patterns to use
@@ -95,6 +99,7 @@ Run typecheck when done. Do NOT commit."
 ## Handling Blockers

 If an impl agent reports a blocker:
+
 - Do NOT ask the user (in either mode)
 - Spin up a researcher to investigate
 - Spin up an impl agent to fix it
@@ -7,6 +7,7 @@ Deploy planners to create an implementation plan informed by research findings.
 Every planner prompt must emphasize this: the default agent instinct is to bolt new code on top of existing code. Resist this.

 The right approach:
+
 1. Study the existing code — understand why it's shaped the way it is
 2. Design the target shape — what would the code look like if this feature had always existed?
 3. Identify the refactoring gap — what needs to change so the new feature slots in cleanly?
@@ -65,6 +66,7 @@ Challenge the plan:
 ## Multiple Planners (Order 3+)

 For cross-module tasks, deploy planners focusing on different slices:
+
 - One for backend phases
 - One for frontend phases
 - One for test strategy
@@ -74,6 +76,7 @@ Then deploy a plan-reviewer to challenge the combined plan.
 ## Iteration

 If the plan-reviewer finds significant issues, either:
+
 1. Send follow-up instructions via the Paseo **send agent prompt** tool to the planner
 2. Launch a new planner if the original is stale

@@ -24,15 +24,16 @@ Maps role categories to `<agent-type>/<model>` strings. These map directly to th
 - The part before `/` is the `agentType` (e.g., `codex`, `claude`, `opencode`)
 - The part after `/` is the `model` (e.g., `gpt-5.4`, `opus`)

-| Category | Roles covered |
-|----------|--------------|
-| `impl` | impl, tester, refactorer |
-| `ui` | impl agents doing UI/styling work |
-| `research` | researcher |
-| `planning` | planner, plan-reviewer |
-| `audit` | auditor, qa |
+| Category   | Roles covered                     |
+| ---------- | --------------------------------- |
+| `impl`     | impl, tester, refactorer          |
+| `ui`       | impl agents doing UI/styling work |
+| `research` | researcher                        |
+| `planning` | planner, plan-reviewer            |
+| `audit`    | auditor, qa                       |

 If a category is missing, use these defaults:
+
 - `impl` -> `codex/gpt-5.4`
 - `ui` -> `claude/opus`
 - `research` -> `codex/gpt-5.4`
@@ -44,6 +45,7 @@ If a category is missing, use these defaults:
 Freeform array of natural language strings. The user states preferences and the orchestrator appends them here. Read these at startup and weave them into your behavior contextually.

 Examples:
+
 - "Prefer small, focused PRs over large bundled ones"
 - "Run E2E tests with Maestro, not Playwright"
 - "Always check mobile responsiveness"
@@ -18,46 +18,46 @@ State the order and briefly why: "Order 3 — touches server session management

 A contained change: fix a bug in one function, add a field to one type, update one component.

-| Phase | Agents |
-|-------|--------|
-| Research | 1 researcher |
-| Planning | 0 — orchestrator plans inline |
-| Implement | 1 impl |
-| Verify | 1-2 auditors |
-| Cleanup | 0-1 refactorer |
+| Phase     | Agents                        |
+| --------- | ----------------------------- |
+| Research  | 1 researcher                  |
+| Planning  | 0 — orchestrator plans inline |
+| Implement | 1 impl                        |
+| Verify    | 1-2 auditors                  |
+| Cleanup   | 0-1 refactorer                |

 ### Order 2 — Single module, few files

 A feature or fix within one package that touches 3-8 files. Might involve new types, new tests, a few component changes.

-| Phase | Agents |
-|-------|--------|
-| Research | 2 researchers |
-| Planning | 1 planner |
+| Phase     | Agents           |
+| --------- | ---------------- |
+| Research  | 2 researchers    |
+| Planning  | 1 planner        |
 | Implement | 1 impl per phase |
-| Verify | 2-3 auditors |
-| Cleanup | 1 refactorer |
+| Verify    | 2-3 auditors     |
+| Cleanup   | 1 refactorer     |

 ### Order 3 — Cross-module, multiple packages

 A feature that spans packages (e.g., server + app, or CLI + server). Multiple concerns, multiple file groups, likely needs interface changes between layers.

-| Phase | Agents |
-|-------|--------|
-| Research | 3-4 researchers (one per area: backend, frontend, tests, external docs) |
-| Planning | 2 planners + 1 plan-reviewer |
-| Implement | 1-2 impl agents per phase |
-| Verify | 3-4 auditors (overeng, tests, regression, types) |
-| Cleanup | 1-2 refactorers |
+| Phase     | Agents                                                                  |
+| --------- | ----------------------------------------------------------------------- |
+| Research  | 3-4 researchers (one per area: backend, frontend, tests, external docs) |
+| Planning  | 2 planners + 1 plan-reviewer                                            |
+| Implement | 1-2 impl agents per phase                                               |
+| Verify    | 3-4 auditors (overeng, tests, regression, types)                        |
+| Cleanup   | 1-2 refactorers                                                         |

 ### Order 4 — Architectural, system-wide

 A new subsystem, major refactor, or change that touches most of the codebase. New abstractions, new patterns, potentially breaking changes that need migration.

-| Phase | Agents |
-|-------|--------|
-| Research | 5+ researchers across all relevant areas |
-| Planning | 2+ planners (one per major area) + 2 plan-reviewers |
-| Implement | 2+ impl agents per phase, sequenced carefully |
-| Verify | Full auditor suite per phase |
-| Cleanup | 2+ refactorers with different specializations |
+| Phase     | Agents                                              |
+| --------- | --------------------------------------------------- |
+| Research  | 5+ researchers across all relevant areas            |
+| Planning  | 2+ planners (one per major area) + 2 plan-reviewers |
+| Implement | 2+ impl agents per phase, sequenced carefully       |
+| Verify    | Full auditor suite per phase                        |
+| Cleanup   | 2+ refactorers with different specializations       |
@@ -6,13 +6,13 @@ After every implementation phase, deploy auditors to verify the work. Auditors a

 Not every phase needs every auditor. Match auditors to the work:

-| Phase type | Auditors |
-|-----------|----------|
-| Refactor | `parity`, `regression`, `types` |
-| Feature (backend) | `overeng`, `tests`, `regression`, `types` |
+| Phase type         | Auditors                                               |
+| ------------------ | ------------------------------------------------------ |
+| Refactor           | `parity`, `regression`, `types`                        |
+| Feature (backend)  | `overeng`, `tests`, `regression`, `types`              |
 | Feature (frontend) | `overeng`, `tests`, `types`, `browser` (if applicable) |
-| UI pass | `overeng`, `browser` (if applicable) |
-| Test-only | `regression` |
+| UI pass            | `overeng`, `browser` (if applicable)                   |
+| Test-only          | `regression`                                           |

 Deploy all relevant auditors in parallel — they're read-only so they don't conflict.

@@ -151,6 +151,7 @@ Do NOT edit files."
 ## Interpreting Findings

 If any auditor reports issues:
+
 1. Check the auditor's activity with the Paseo **get agent activity** tool for details
 2. Direct the impl agent to fix them via the Paseo **send agent prompt** tool, or launch a new impl agent if the old one is stale
 3. Re-deploy the same auditor after fixes