qualia-framework 2.5.1 → 3.1.0

package/framework/skills/responsive/SKILL.md

@@ -1,231 +0,0 @@
----
-name: responsive
-description: Deep responsive design expert. Analyzes and fixes layouts for all screens - mobile, tablet, desktop, ultrawide. Understands breakpoints, container queries, fluid typography, and touch targets.
-tags: [responsive, mobile, layout, breakpoints, accessibility]
----
-
-# Responsive Design Expert
-
-I make your UI work perfectly on every screen size.
-
-## What I Do
-
-1. **Audit current responsiveness** - Find what breaks
-2. **Fix layout issues** - Overflow, cramped content, tiny text
-3. **Optimize touch targets** - 44px minimum for mobile
-4. **Apply fluid scaling** - Typography, spacing, containers
-5. **Test edge cases** - Landscape phones, tablets, ultrawides
-
-## How to Use
-
-- "Make this page responsive"
-- "Fix the mobile layout"
-- "The navbar breaks on tablet"
-- "This looks bad on ultrawide"
-
-I'll analyze and fix it.
-
-## My Analysis Process
-
-### 1. Find Breaking Points
-```
-- Scan for fixed widths (px values that should be fluid)
-- Check for horizontal overflow
-- Find text that gets too small or too large
-- Identify touch targets under 44px
-- Look for images without max-width
-```
-
-### 2. Check Key Breakpoints
-```
-320px  - Small phones (iPhone SE)
-375px  - Standard phones
-428px  - Large phones (iPhone Pro Max)
-768px  - Tablets portrait
-1024px - Tablets landscape / small laptops
-1280px - Laptops
-1536px - Desktops
-1920px - Large desktops
-2560px - Ultrawides
-```
-
-### 3. Test Interactions
-```
-- Hover states need touch alternatives
-- Dropdowns need mobile-friendly triggers
-- Modals need proper mobile sizing
-- Forms need appropriate input sizes
-```
-
-## Common Fixes I Apply
-
-### Layout
-```css
-/* Fluid container — full width with responsive padding */
-.container {
-  width: 100%;
-  padding-inline: clamp(1rem, 5vw, 4rem);
-  margin-inline: auto;
-}
-
-/* Content container — for readable text sections only */
-.container-prose {
-  max-width: 65ch;
-  margin-inline: auto;
-}
-
-/* Responsive grid */
-.grid {
-  display: grid;
-  grid-template-columns: repeat(auto-fit, minmax(min(300px, 100%), 1fr));
-  gap: clamp(1rem, 3vw, 2rem);
-}
-
-/* Stack on mobile */
-.flex-row {
-  display: flex;
-  flex-direction: column;
-  @media (min-width: 768px) {
-    flex-direction: row;
-  }
-}
-```
-
-### Typography
-```css
-/* Fluid type scale */
-.heading {
-  font-size: clamp(1.5rem, 4vw + 1rem, 3rem);
-}
-
-.body {
-  font-size: clamp(1rem, 0.5vw + 0.875rem, 1.125rem);
-}
-
-/* Readable line length */
-.prose {
-  max-width: 65ch;
-}
-```
-
-### Spacing
-```css
-/* Fluid spacing */
-.section {
-  padding-block: clamp(2rem, 8vw, 6rem);
-  padding-inline: clamp(1rem, 5vw, 3rem);
-}
-```
-
-### Images
-```css
-img {
-  max-width: 100%;
-  height: auto;
-  display: block;
-}
-
-/* Responsive aspect ratio */
-.hero-image {
-  aspect-ratio: 16/9;
-  @media (max-width: 768px) {
-    aspect-ratio: 4/3;
-  }
-}
-```
-
-### Touch Targets
-```css
-/* Minimum touch target */
-button, a, input {
-  min-height: 44px;
-  min-width: 44px;
-}
-
-/* Spacing between targets */
-.nav-links {
-  gap: 0.5rem; /* At least 8px between */
-}
-```
-
-## Container Queries (Modern Approach)
-
-```css
-/* Component responds to its container, not viewport */
-.card-container {
-  container-type: inline-size;
-}
-
-@container (width < 300px) {
-  .card { flex-direction: column; }
-  .card-image { aspect-ratio: 16/9; }
-}
-
-@container (width >= 300px) {
-  .card { flex-direction: row; }
-  .card-image { width: 120px; }
-}
-```
-
-## Mobile-First Checklist
-
-- [ ] Base styles work without media queries
-- [ ] Text readable without zooming (16px+ body)
-- [ ] Touch targets 44px+
-- [ ] No horizontal scroll
-- [ ] Forms have proper input types
-- [ ] Images scale down
-- [ ] Modals fit screen
-- [ ] Navigation accessible
-- [ ] Focus states visible
-- [ ] Landscape orientation works
-
-## Red Flags I Look For
-
-```
-❌ width: 500px (fixed widths)
-❌ font-size: 12px (too small for mobile)
-❌ height: 100vh on mobile (iOS issues)
-❌ hover-only interactions
-❌ Tiny close buttons
-❌ Side-by-side on mobile
-❌ Overflow: hidden hiding content
-❌ Position: fixed without mobile consideration
-```
-
-## Tailwind Responsive Patterns
-
-```html
-<!-- Mobile-first stacking -->
-<div class="flex flex-col md:flex-row gap-4">
-
-<!-- Responsive text -->
-<h1 class="text-2xl sm:text-3xl md:text-4xl lg:text-5xl">
-
-<!-- Responsive padding -->
-<section class="px-4 sm:px-6 lg:px-8 py-12 md:py-20">
-
-<!-- Hide/show -->
-<div class="hidden md:block">Desktop only</div>
-<div class="md:hidden">Mobile only</div>
-
-<!-- Responsive grid -->
-<div class="grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-4 gap-4">
-```
-
-## I Test At These Widths
-
-1. **320px** - Does it fit? Is text readable?
-2. **375px** - Standard mobile, should look good
-3. **768px** - Tablet, layout should adapt
-4. **1024px** - Small desktop, full features
-5. **1440px** - Standard desktop
-6. **1920px+** - Should it max-width or fill?
-
-## Output
-
-I provide:
-1. List of issues found
-2. Specific fixes with code
-3. Before/after mental model
-4. Priority order (critical → nice-to-have)

package/framework/skills/retro/SKILL.md

@@ -1,284 +0,0 @@
----
-name: retro
-description: "Generate retrospective analytics from git log, session data, and SUMMARY files. Produces a markdown trend report with commits per session, lines added/removed, test ratio, deviation rate, hotspot files, and shipping velocity. Run from any project directory or ~/.claude for cross-project view."
-user-invocable: true
-args:
-  - name: weeks
-    description: "Number of weeks to analyze (default: 4)"
-    required: false
-  - name: project
-    description: "Specific project name to filter (default: current directory)"
-    required: false
----
-
-# Retrospective Analytics
-
-> Team-level shipping analytics. No individual attribution. Outcome-focused.
-
-Generate a retrospective report showing how shipping patterns evolve over time. All metrics are aggregate -- no per-developer breakdowns or policing metrics (RETR-05).
-
-## Usage
-
-- `/retro` -- Analyze current project, last 4 weeks
-- `/retro --weeks 8` -- Analyze current project, last 8 weeks
-- `/retro --project under` -- Analyze specific project, last 4 weeks
-
-## Data Sources
-
-Collect data from three sources. If a source is unavailable, skip it and note "N/A" in the report.
-
-### Source 1: Git Log
-
-Run from the current project directory (or the project specified by `--project`):
-
-```bash
-# Commits in date range
-git log --since="{WEEKS} weeks ago" --format="%H|%aI|%s" --no-merges
-
-# Lines added/removed per commit
-git log --since="{WEEKS} weeks ago" --format="%H" --no-merges | while read hash; do
-  git diff --shortstat "${hash}^..${hash}" 2>/dev/null
-done
-
-# File change frequency (hotspots)
-git log --since="{WEEKS} weeks ago" --name-only --format="" --no-merges | sort | uniq -c | sort -rn | head -15
-
-# Test file vs source file ratio in commits
-git log --since="{WEEKS} weeks ago" --name-only --format="" --no-merges | grep -c '\.test\.\|\.spec\.\|test_\|_test\.'
-git log --since="{WEEKS} weeks ago" --name-only --format="" --no-merges | grep -c '\.\(ts\|tsx\|js\|jsx\|py\)$'
-```
-
-### Source 2: Session Data
-
-Read session JSON files from `~/.claude/session-env/session_*.json`:
-
-```bash
-# List all session files
-ls -t ~/.claude/session-env/session_*.json
-
-# Each file contains: timestamp, project, branch, files_changed, summary
-# Parse with jq or grep to extract metrics
-```
-
-Also read `~/.claude/knowledge/session-digest.md` for the rolling session log (pipe-delimited table with date, project, branch, files_changed, summary).
-
-**Session detection heuristic:** Each `session_*.json` file = one session. Count files matching the date range.
-
-### Source 3: SUMMARY Files
-
-Scan for SUMMARY files in the current project's `.planning/phases/` directory:
-
-```bash
-# Find all SUMMARY files
-find .planning/phases/ -name "*-SUMMARY.md" -type f 2>/dev/null
-
-# From each SUMMARY, extract:
-# - Duration (from frontmatter or body)
-# - Deviation count (from "## Deviations" or "## Deferred Discoveries" sections)
-# - Task count (from provides/affects lists)
-```
-
-## Metric Calculations
-
-Calculate these 6 metrics from collected data:
-
-### M1: Commits Per Session
-```
-commits_per_session = total_commits / total_sessions
-```
-Where `total_sessions` = count of session_*.json files matching the project and date range. If session data unavailable, report "N/A (no session data)".
-
-### M2: Lines Added / Removed
-```
-lines_added = sum of insertions from git shortstat
-lines_removed = sum of deletions from git shortstat
-net_lines = lines_added - lines_removed
-churn_ratio = lines_removed / lines_added  (lower = more additive work)
-```
-
-### M3: Test Ratio
-```
-test_ratio = test_file_changes / total_source_file_changes
-```
-Where test files match `*.test.*`, `*.spec.*`, `test_*`, `_test.*` and source files match `*.ts`, `*.tsx`, `*.js`, `*.jsx`, `*.py`. Report as percentage: "23% of file changes include tests".
-
-### M4: Deviation Rate
-```
-deviation_rate = total_deviations / total_tasks_completed
-```
-Parse from SUMMARY files. Deviations appear under `## Deviations` or `## Deferred Discoveries` sections. If no SUMMARY files exist, report "N/A (no planning data)".
-
-### M5: Hotspot Files
-Top 10 most frequently changed files in the period. Flag files with >5 changes as "high churn" -- these may indicate architectural issues or high-risk areas.
-
-### M6: Shipping Velocity
-```
-plans_per_week = completed_plans / weeks_analyzed
-commits_per_week = total_commits / weeks_analyzed
-```
-Completed plans = count of SUMMARY files created in the date range (by file modification time). Commits per week from git log.
-
-## Report Template
-
-Generate the report in this exact format:
-
-```markdown
-# Retrospective Report
-
-**Project:** {project_name}
-**Period:** {start_date} to {end_date} ({weeks} weeks)
-**Generated:** {current_date}
-
-## Metrics Summary
-
-| Metric | Value | vs Last |
-|--------|-------|---------|
-| Commits/Session | {value} | {computed_trend} |
-| Lines Added | {value} | {computed_trend} |
-| Lines Removed | {value} | {computed_trend} |
-| Net Lines | {value} | {computed_trend} |
-| Test Ratio | {value}% | {computed_trend} |
-| Deviation Rate | {value}% | {computed_trend} |
-| Plans/Week | {value} | {computed_trend} |
-| Commits/Week | {value} | {computed_trend} |
-
-## Hotspot Files
-
-| Rank | File | Changes | Status |
-|------|------|---------|--------|
-| 1 | {file} | {count} | {normal|high churn} |
-| ... | ... | ... | ... |
-
-## Observations
-
-{Auto-generated observations based on data:}
-- {If test ratio < 20%: "Low test coverage in commits -- consider TDD for new features"}
-- {If churn_ratio > 0.5: "High code churn -- significant rewrites happening"}
-- {If any hotspot > 10 changes: "{file} is a hotspot with {N} changes -- consider splitting"}
-- {If deviation_rate > 30%: "High deviation rate -- plans may need better scoping"}
-- {If commits_per_session < 1: "Low commit frequency -- consider more atomic commits"}
-
-## Raw Data
-
-<details>
-<summary>Data sources used</summary>
-
-- Git log: {commit_count} commits analyzed
-- Sessions: {session_count} sessions found
-- SUMMARYs: {summary_count} plan summaries parsed
-</details>
-```
-
-The "vs Last" column shows week-over-week deltas computed from prior JSON snapshots in `~/.claude/knowledge/retros/`. First run shows "---" for all trends.
-
-## Snapshot Storage
-
-After generating the report, save a JSON snapshot for trend tracking:
-
-```bash
-mkdir -p ~/.claude/knowledge/retros
-```
-
-Save to `~/.claude/knowledge/retros/retro_{project}_{YYYYMMDD}.json`:
-
-```json
-{
-  "project": "{project_name}",
-  "date": "{YYYY-MM-DD}",
-  "period_weeks": {weeks},
-  "metrics": {
-    "commits_per_session": {value},
-    "lines_added": {value},
-    "lines_removed": {value},
-    "net_lines": {value},
-    "test_ratio": {value},
-    "deviation_rate": {value},
-    "plans_per_week": {value},
-    "commits_per_week": {value}
-  },
-  "hotspots": [
-    {"file": "{path}", "changes": {count}}
-  ]
-}
-```
-
-This snapshot is consumed by week-over-week trend analysis (see below).
-
-## Week-over-Week Trend Analysis
-
-After collecting current metrics, load prior snapshots to compute deltas (RETR-03).
-
-### Loading Prior Snapshots
-
-```bash
-# Find the most recent prior snapshot for this project
-ls -t ~/.claude/knowledge/retros/retro_{project}_*.json 2>/dev/null | head -2
-```
-
-Read the **second most recent** snapshot (the most recent will be the one about to be saved). If no prior snapshot exists, set all trends to "---" (first run, no comparison available).
-
-### Computing Deltas
-
-For each metric, calculate:
-
-```
-delta = current_value - prior_value
-delta_pct = ((current_value - prior_value) / prior_value) * 100
-```
-
-### Trend Formatting
-
-Format each trend using direction arrow + magnitude:
-
-| Condition | Format | Example |
-|-----------|--------|---------|
-| delta_pct > 10% | {arrow_up} +{delta_pct}% | ^ +25% |
-| delta_pct between -10% and +10% | {arrow_right} ~{delta_pct}% | ~ ~3% |
-| delta_pct < -10% | {arrow_down} {delta_pct}% | v -15% |
-| No prior data | --- | --- |
-| Prior value was 0 | NEW | NEW |
-
-Use text arrows: `^` for up, `v` for down, `~` for flat. Do NOT use unicode arrows (they render inconsistently in terminals).
-
-**Trend interpretation context (add after each metric in the report):**
-
-- Commits/Session: higher is neutral (more granular work), lower is neutral (bigger chunks)
-- Lines Added: higher may mean new features, lower may mean maintenance mode
-- Lines Removed: higher means cleanup/refactoring is happening
-- Test Ratio: higher is GOOD (more testing), lower is CONCERNING
-- Deviation Rate: lower is GOOD (better planning), higher is CONCERNING
-- Plans/Week: higher means faster shipping velocity
-- Commits/Week: higher is neutral (activity indicator only)
-
-### Trend Summary
-
-Add a "## Trend Summary" section to the report, after the metrics table:
-
-```markdown
-## Trend Summary
-
-**Compared to:** {prior_snapshot_date}
-
-**Positive signals:**
-- {List metrics trending in desirable direction, e.g., "Test ratio up 15% -- more tests being written"}
-
-**Watch items:**
-- {List metrics trending in concerning direction, e.g., "Deviation rate up 20% -- plans may need better scoping"}
-
-**Stable:**
-- {List metrics within +/-10%}
-```
-
-If no prior snapshot exists, replace the Trend Summary with:
-
-```markdown
-## Trend Summary
-
-First retrospective run -- no prior data for comparison. Run `/retro` again next week to see trends.
-```
-
-## Guardrails
-
-- **No individual attribution:** Never break down metrics by author. All metrics are project-level aggregate (RETR-05).
-- **Graceful degradation:** If git log fails (not a git repo), report only session data. If session data missing, report only git data. If both missing, report error with instructions.
-- **No policing metrics:** No "lines per hour", "commits per day per person", or productivity scoring. Focus on outcomes: what shipped, what's changing, what needs attention.

package/framework/skills/sakani-conventions/SKILL.md

@@ -1,136 +0,0 @@
----
-name: sakani-conventions
-description: "Sakani project conventions — monorepo structure, shared types, error codes, entity naming, role definitions, and domain rules from SRS V1.14. Use this skill whenever working on the Sakani project, including backend, mobile, admin console, or any shared code. Trigger on: sakani, building management, property management, tenant, owner, guard, building manager, dues, ledger, or any reference to the Sakani codebase."
-tags: [sakani, conventions, domain, property-management]
----
-
-# Sakani Project Conventions
-
-Sakani is a property management platform for Jordan. Native iOS/Android app (React Native Expo) + NestJS backend + Next.js staff admin console + Supabase (Postgres). This skill defines project-wide conventions that all other skills reference.
-
-## Monorepo Structure
-
-```
-sakani/
-├── apps/
-│   ├── mobile/              # React Native Expo (iOS + Android)
-│   ├── api/                 # NestJS backend
-│   └── admin/               # Next.js staff admin console
-├── packages/
-│   ├── shared/              # Shared types, constants, validation
-│   │   ├── src/
-│   │   │   ├── types/       # Domain entity types
-│   │   │   ├── constants/   # Error codes, role definitions, enums
-│   │   │   ├── validation/  # Zod schemas shared across apps
-│   │   │   └── utils/       # Pure utility functions
-│   │   └── package.json
-│   └── config/              # Shared ESLint, TS configs
-├── supabase/
-│   ├── migrations/          # SQL migrations (source of truth)
-│   └── functions/           # Edge Functions (background jobs)
-├── docs/                    # Reference docs (gitignored)
-├── turbo.json
-├── package.json
-└── .gitignore
-```
-
-Import convention: `@sakani/shared` resolves to `packages/shared`. All apps import domain types and validation from here — never duplicate type definitions across apps.
-
-## User Roles
-
-8 roles with RBAC+ABAC hybrid. Deny-by-default — every action requires explicit grant.
-
-| Role | Code | Scope | Description |
-|------|------|-------|-------------|
-| Staff Admin | `STAFF_ADMIN` | Global | Verification governance, audited overrides |
-| BM Candidate | `BM_CANDIDATE` | Building | Initial building manager, pre-verification |
-| BM Verified | `BM_VERIFIED` | Building | Verified building manager, full ops access |
-| Owner Unverified | `OWNER_UNVERIFIED` | Unit | Pending ownership verification |
-| Owner Verified | `OWNER_VERIFIED` | Unit | Verified owner (one per unit) |
-| Tenant | `TENANT` | Unit | Invite-only, unit-scoped, cannot browse |
-| Guard | `GUARD` | Building | Building ops, timed tasks, calendar |
-| Dev Admin | `DEV_ADMIN` | Building | Pre-handover only, identity doc access |
-
-Scopes: `S` (self), `U` (unit), `B` (building), `G` (global). Server-side predicates enforce all scope rules — UI conventions are display-only, never security boundaries.
-
-## Entity Naming
-
-All entities use `snake_case` in the database and API. TypeScript types use `PascalCase`. Properties use `camelCase` in TypeScript, `snake_case` in API responses.
-
-### Core Entities
-
-Read `references/entities.md` for the full entity list with field definitions. Key entities:
-
-**Identity:** `building`, `unit`, `unit_claim_request`, `building_setup_request`, `unit_membership`, `building_role_assignment`, `document`
-
-**Finance:** `dues_cycle`, `dues_config`, `dues_obligation`, `ledger_entry`, `credit_topup_request`, `settlement_entry`, `expense`
-
-**Subscription:** `subscription_entitlement`, `subscription_plan`, `subscription_pricing_tier`, `subscription_price_quote`, `subscription_checkout_session`, `promo_code`, `promo_redemption`, `reimbursement_obligation`
-
-**Operations:** `guard_invite`, `guard_assignment`, `guard_task`, `task_template`, `task_instance`, `ticket`
-
-**Audit:** `audit_log`, `statement_version`
-
-## Error Contract
-
-All API errors follow a standardized shape. 44 error codes defined in V1.14 (EH-6.02 through EH-6.44).
-
-```typescript
-interface ApiError {
-  http_status: number;
-  error_code: string;       // e.g., "BUILDING_NOT_FOUND"
-  message_key: string;      // i18n key, e.g., "error.building.not_found"
-  request_id: string;       // UUID correlation
-  details?: Record<string, unknown>; // safe details only
-}
-```
-
-**Safe-details rule:** Never include `building_key_v1`, `unit_key_v1`, identity values, or extracted document text in error responses. This prevents entity enumeration.
-
-Read `references/error-codes.md` for the full mapping of all 44 error codes with HTTP status codes.
-
-## Financial Rules
-
-These are non-negotiable domain rules that every piece of code touching money must follow:
-
-- **Append-only ledger.** Never update or delete a `ledger_entry`. Corrections use `REVERSAL` entries only.
-- **Idempotency keys** on every financial write operation. Duplicate requests with same idempotency key return the original result.
-- **FIFO credit settlement.** No partial settlement — credit either covers the full obligation or doesn't apply.
-- **7 entry types only:** `CREDIT_TOPUP`, `MANUAL_UNIT_INCOME`, `OPENING_BALANCE`, `EXPENSE`, `SUBSCRIPTION_FEE`, `AUTOSETTLEMENT_APPLIED`, `REVERSAL`.
-- **Monetary values** always stored as `{ amount: number, currency: string }` with ISO 4217 currency code (JOD for Jordan).
-- **Daily auto-settlement** at 07:00 Asia/Amman — atomically applies credit to cover obligations.
-
-## Timestamps & Localization
-
-- All timestamps stored in UTC. Presented in `Asia/Amman` for Jordan buildings.
-- Numerals display as `0-9` (Western Arabic), not `٠-٩`.
-- Arabic (RTL) + English. Every user-facing string uses a `message_key` — no hardcoded labels in backend responses.
-- All `reason_code` values are stable identifiers, not display text.
-
-## Database Conventions
-
-- Every table has `id` (UUID), `created_at` (timestamptz), `updated_at` (timestamptz).
-- Every request carries a `request_id` (UUID) for audit correlation.
-- RLS policies on every table — no exceptions.
-- `building_key_v1` and `unit_key_v1` are opaque canonical keys for deterministic matching. Never expose in API responses or logs.
-
-## Authentication
-
-OTP-based login via SMS. Access/refresh token rotation with server-side session enforcement. No password-based auth.
-
-## Subscription States
-
-Per-building subscription: `TRIAL` (30 days) → `ACTIVE` → `INACTIVE`. Paywall gates most features when `INACTIVE`, but identity documents remain accessible.
-
-## Commit Convention
-
-All commits within Sakani follow: `{type}({phase}-{plan}): {description}` during Qualia execution, or `{type}(sakani): {description}` for standalone changes.
-
-## When to Read References
-
-| You're working on... | Read |
-|---|---|
-| Any entity CRUD, schema design | `references/entities.md` |
-| Error handling, API responses | `references/error-codes.md` |
-| Permission checks, role guards | This file (Roles table above) |
-| Financial logic, ledger ops | This file (Financial Rules above) |

package/framework/skills/sakani-conventions/evals/evals.json

@@ -1,23 +0,0 @@
-{
-  "skill_name": "sakani-conventions",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I need to create the NestJS DTOs and Supabase migration for the credit top-up request feature. Owner submits a top-up with evidence (CliQ screenshot), BM approves or rejects. Create the migration SQL file and the TypeScript types.",
-      "expected_output": "Should produce: migration with correct table schema matching entities.md (idempotency_key, evidence_document_id FK, status enum, etc.), TypeScript types with snake_case DB fields and camelCase TS properties, error handling using the exact SAKANI_ERRORS codes (DUPLICATE_TOPUP_REQUEST, TOPUP_ALREADY_REVIEWED), and the ledger_entry for CREDIT_TOPUP type following append-only rules.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "Write the guard invite API endpoint for Sakani. BM invites a guard to the building by phone number. The invite expires after 7 days and is single-use. Only one active guard per building.",
-      "expected_output": "Should produce: NestJS controller/service following monorepo import pattern (@sakani/shared), correct error codes (GUARD_INVITE_EXPIRED, GUARD_INVITE_REVOKED, GUARD_ALREADY_ACTIVE), proper role check (BM_VERIFIED only), idempotency handling, and the API error response shape matching the ApiError interface exactly.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "Create the Supabase RLS policies for the ticket table. Owners and tenants can create tickets for their unit. BMs can see all tickets in their building. Guards can see tickets assigned to them. Staff admins can see everything.",
-      "expected_output": "Should produce: RLS policies using auth.uid() with correct role checks against building_role_assignment and unit_membership tables, proper scope enforcement (unit-scoped for owners/tenants, building-scoped for BM/guard, global for staff), and deny-by-default approach (no permissive policies without role check).",
-      "files": []
-    }
-  ]
-}