chore(cleanup): remove obsolete team-mode workspace artifacts

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>

.sisyphus/evidence/team-mode/task-2-category-prompt-required.txt

@@ -1,7 +0,0 @@
-bun test v1.3.12 (700fc117)
-
- 1 pass
- 3 filtered out
- 0 fail
- 1 expect() calls
-Ran 1 test across 1 file. [64.00ms]

.sisyphus/evidence/team-mode/task-2-disc-both.txt

@@ -1,7 +0,0 @@
-bun test v1.3.12 (700fc117)
-
- 1 pass
- 3 filtered out
- 0 fail
- 1 expect() calls
-Ran 1 test across 1 file. [65.00ms]

.sisyphus/evidence/team-mode/task-2-disc-category.txt

@@ -1,7 +0,0 @@
-bun test v1.3.12 (700fc117)
-
- 1 pass
- 3 filtered out
- 0 fail
- 3 expect() calls
-Ran 1 test across 1 file. [69.00ms]

.sisyphus/evidence/team-mode/task-2-eligibility-registry.txt

@@ -1,7 +0,0 @@
-bun test v1.3.12 (700fc117)
-
- 1 pass
- 3 filtered out
- 0 fail
- 12 expect() calls
-Ran 1 test across 1 file. [61.00ms]

.sisyphus/notepads/team-mode/learnings.md

@@ -1,10 +0,0 @@
-## 2026-04-18 Task 2: types module
-
-- `MemberSchema` needs `.strict()` on the base shape so the discriminatedUnion rejects members that mix `category` and `subagent_type`.
-- `backendType` and `isActive` defaults are part of the schema contract, so tests should use `toMatchObject` instead of exact object equality.
-- The eligibility registry must preserve the plan strings verbatim, especially the hard-reject messages for Momus verification.
-## Task 12 learnings
-
-- `git worktree remove` can leave prunable entries behind, so pruning after removal keeps the repo index tidy.
-- For testability, a tiny git command runner hook made git-unavailable coverage simpler than mocking Bun directly.
-- Detached worktrees need unique temp paths in tests to avoid cross-run collisions.

.sisyphus/rules/modular-code-enforcement.md

@@ -1,117 +0,0 @@
----
-globs: ["**/*.ts", "**/*.tsx"]
-alwaysApply: false
-description: "Enforces strict modular code architecture: SRP, no monolithic index.ts, 200 LOC hard limit"
----
-
-<MANDATORY_ARCHITECTURE_RULE severity="BLOCKING" priority="HIGHEST">
-
-# Modular Code Architecture — Zero Tolerance Policy
-
-This rule is NON-NEGOTIABLE. Violations BLOCK all further work until resolved.
-
-## Rule 1: index.ts is an ENTRY POINT, NOT a dumping ground
-
-`index.ts` files MUST ONLY contain:
-- Re-exports (`export { ... } from "./module"`)
-- Factory function calls that compose modules
-- Top-level wiring/registration (hook registration, plugin setup)
-
-`index.ts` MUST NEVER contain:
-- Business logic implementation
-- Helper/utility functions
-- Type definitions beyond simple re-exports
-- Multiple unrelated responsibilities mixed together
-
-**If you find mixed logic in index.ts**: Extract each responsibility into its own dedicated file BEFORE making any other changes. This is not optional.
-
-## Rule 2: No Catch-All Files — utils.ts / service.ts are CODE SMELLS
-
-A single `utils.ts`, `helpers.ts`, `service.ts`, or `common.ts` is a **gravity well** — every unrelated function gets tossed in, and it grows into an untestable, unreviewable blob.
-
-**These file names are BANNED as top-level catch-alls.** Instead:
-
-| Anti-Pattern | Refactor To |
-|--------------|-------------|
-| `utils.ts` with `formatDate()`, `slugify()`, `retry()` | `date-formatter.ts`, `slugify.ts`, `retry.ts` |
-| `service.ts` handling auth + billing + notifications | `auth-service.ts`, `billing-service.ts`, `notification-service.ts` |
-| `helpers.ts` with 15 unrelated exports | One file per logical domain |
-
-**Design for reusability from the start.** Each module should be:
-- **Independently importable** — no consumer should need to pull in unrelated code
-- **Self-contained** — its dependencies are explicit, not buried in a shared grab-bag
-- **Nameable by purpose** — the filename alone tells you what it does
-
-If you catch yourself typing `utils.ts` or `service.ts`, STOP and name the file after what it actually does.
-
-## Rule 3: Single Responsibility Principle — ABSOLUTE
-
-Every `.ts` file MUST have exactly ONE clear, nameable responsibility.
-
-**Self-test**: If you cannot describe the file's purpose in ONE short phrase (e.g., "parses YAML frontmatter", "matches rules against file paths"), the file does too much. Split it.
-
-| Signal | Action |
-|--------|--------|
-| File has 2+ unrelated exported functions | **SPLIT NOW** — each into its own module |
-| File mixes I/O with pure logic | **SPLIT NOW** — separate side effects from computation |
-| File has both types and implementation | **SPLIT NOW** — types.ts + implementation.ts |
-| You need to scroll to understand the file | **SPLIT NOW** — it's too large |
-
-## Rule 4: 200 LOC Hard Limit — CODE SMELL DETECTOR
-
-Any `.ts`/`.tsx` file exceeding **200 lines of code** (excluding prompt strings, template literals containing prompts, and `.md` content) is an **immediate code smell**.
-
-**When you detect a file > 200 LOC**:
-1. **STOP** current work
-2. **Identify** the multiple responsibilities hiding in the file
-3. **Extract** each responsibility into a focused module
-4. **Verify** each resulting file is < 200 LOC and has a single purpose
-5. **Resume** original work
-
-Prompt-heavy files (agent definitions, skill definitions) where the bulk of content is template literal prompt text are EXEMPT from the LOC count — but their non-prompt logic must still be < 200 LOC.
-
-### How to Count LOC
-
-**Count these** (= actual logic):
-- Import statements
-- Variable/constant declarations
-- Function/class/interface/type definitions
-- Control flow (`if`, `for`, `while`, `switch`, `try/catch`)
-- Expressions, assignments, return statements
-- Closing braces `}` that belong to logic blocks
-
-**Exclude these** (= not logic):
-- Blank lines
-- Comment-only lines (`//`, `/* */`, `/** */`)
-- Lines inside template literals that are prompt/instruction text (e.g., the string body of `` const prompt = `...` ``)
-- Lines inside multi-line strings used as documentation/prompt content
-
-**Quick method**: Read the file → subtract blank lines, comment-only lines, and prompt string content → remaining count = LOC.
-
-**Example**:
-```typescript
-// 1  import { foo } from "./foo";          ← COUNT
-// 2                                         ← SKIP (blank)
-// 3  // Helper for bar                      ← SKIP (comment)
-// 4  export function bar(x: number) {       ← COUNT
-// 5    const prompt = `                     ← COUNT (declaration)
-// 6      You are an assistant.              ← SKIP (prompt text)
-// 7      Follow these rules:                ← SKIP (prompt text)
-// 8    `;                                   ← COUNT (closing)
-// 9    return process(prompt, x);           ← COUNT
-// 10 }                                      ← COUNT
-```
-→ LOC = **5** (lines 1, 4, 5, 9, 10). Not 10.
-
-When in doubt, **round up** — err on the side of splitting.
-
-## How to Apply
-
-When reading, writing, or editing ANY `.ts`/`.tsx` file:
-
-1. **Check the file you're touching** — does it violate any rule above?
-2. **If YES** — refactor FIRST, then proceed with your task
-3. **If creating a new file** — ensure it has exactly one responsibility and stays under 200 LOC
-4. **If adding code to an existing file** — verify the addition doesn't push the file past 200 LOC or add a second responsibility. If it does, extract into a new module.
-
-</MANDATORY_ARCHITECTURE_RULE>

src/hooks/.sisyphus/ralph-loop.local.md

@@ -1,12 +0,0 @@
----
-active: true
-iteration: 2
-max_iterations: 100
-completion_promise: "DONE"
-initial_completion_promise: "DONE"
-started_at: "2026-03-14T04:20:58.486Z"
-session_id: "new-session-1"
-strategy: "reset"
-message_count_at_start: 0
----
-Build feature