gaslighting-engine 0.3.0 → 0.4.0

package/examples/hospital-homepage/.agents/mcp/manifest.json

@@ -0,0 +1,5 @@
+{
+  "servers": [],
+  "installedAt": null,
+  "source": ".agents/mcp"
+}

package/examples/hospital-homepage/.agents/runtimes/claude.json

@@ -0,0 +1,6 @@
+{
+  "id": "claude",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": true
+}

package/examples/hospital-homepage/.agents/runtimes/codex.json

@@ -0,0 +1,6 @@
+{
+  "id": "codex",
+  "enabled": true,
+  "supportsMcp": true,
+  "supportsSkills": true
+}

package/examples/hospital-homepage/.agents/runtimes/kimi.json

@@ -0,0 +1,6 @@
+{
+  "id": "kimi",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": true
+}

package/examples/hospital-homepage/.agents/runtimes/local.json

@@ -0,0 +1,6 @@
+{
+  "id": "local",
+  "enabled": false,
+  "supportsMcp": false,
+  "supportsSkills": false
+}

package/examples/hospital-homepage/.agents/runtimes/openai_compatible.json

@@ -0,0 +1,6 @@
+{
+  "id": "openai_compatible",
+  "enabled": false,
+  "supportsMcp": false,
+  "supportsSkills": false
+}

package/examples/hospital-homepage/.agents/runtimes/opencode.json

@@ -0,0 +1,6 @@
+{
+  "id": "opencode",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": false
+}

package/examples/hospital-homepage/.agents/runtimes/qwen.json

@@ -0,0 +1,6 @@
+{
+  "id": "qwen",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": false
+}

package/examples/hospital-homepage/.codex/prompts/gaslighting.md

@@ -2,16 +2,16 @@
 
 Read the Gaslighting-engine project-control files before doing any work:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/product/PRD.md`
+5. `.gaslighting/features/core-scope/TASKS.md`
+6. `.gaslighting/operations/PROJECT_CARE.md`
 7. `AGENTS.md`
-8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/AGENT_RUNTIME.md`
-10. `.gaslighting/PROJECT_CARE.md`
+8. `.gaslighting/GASLIGHTING.md`
+9. `.gaslighting/MISSING_INFO.md`
+10. `.gaslighting/DECISION_LOG.md`
 
 Then execute the user's requested implementation.
 

package/examples/hospital-homepage/.gaslighting/AGENTS.md

@@ -4,15 +4,15 @@ This repository uses Gaslighting-engine.
 
 Before doing any work, read these files in order:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
-7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/AGENT_RUNTIME.md`
-9. `.gaslighting/PROJECT_CARE.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/mission/COMPLETION_STANDARD.md`
+5. `.gaslighting/product/PRD.md`
+6. `.gaslighting/features/core-scope/TASKS.md`
+7. `.gaslighting/operations/PROJECT_CARE.md`
+8. `.gaslighting/loops/current-session.json`
+9. `.gaslighting/GASLIGHTING.md`
 
 ## Prime Directive
 

package/examples/hospital-homepage/.gaslighting/CODEX_PROMPT.md

@@ -6,16 +6,16 @@ Copy and paste this into Codex:
 
 Read the following files before doing any work:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/product/PRD.md`
+5. `.gaslighting/features/core-scope/TASKS.md`
+6. `.gaslighting/operations/PROJECT_CARE.md`
 7. `AGENTS.md`
-8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/AGENT_RUNTIME.md`
-10. `.gaslighting/PROJECT_CARE.md`
+8. `.gaslighting/GASLIGHTING.md`
+9. `.gaslighting/MISSING_INFO.md`
+10. `.gaslighting/DECISION_LOG.md`
 
 Then implement the project MVP.
 

package/examples/hospital-homepage/.gaslighting/INDEX.md

@@ -0,0 +1,37 @@
+# Gaslighting-engine Index
+
+This is the structured source of truth for the project discipline layer.
+
+## Mission
+
+- Original request: I want to build a hospital website.
+- Project type: hospital_homepage
+- Classification confidence: medium
+- Default runtime: codex
+- Loop mode: off
+- Permission mode: auto_review
+
+## Read Order For Agents
+
+1. `mission/PROJECT_PURPOSE.md`
+2. `mission/EXECUTION_RULES.md`
+3. `mission/COMPLETION_STANDARD.md`
+4. `product/PRD.md`
+5. `product/PAGE_MAP.md`
+6. `features/core-scope/TASKS.md`
+7. `operations/PROJECT_CARE.md`
+8. `loops/current-session.json`
+
+## Pages
+
+- Home
+- Hospital Introduction
+- Departments / Treatments
+- Doctor Profiles
+- Consultation / Contact
+- Location
+- Privacy Policy
+
+## Compatibility Files
+
+Older agents may still read the root compatibility markdown files in `.gaslighting/`. Those files remain generated for backward compatibility, but this index is the preferred entrypoint.

package/examples/hospital-homepage/.gaslighting/checkpoints/latest.md

@@ -0,0 +1,7 @@
+# Latest Checkpoint
+
+No loop iteration has completed yet.
+
+Original request:
+
+> I want to build a hospital website.

package/examples/hospital-homepage/.gaslighting/config.json

@@ -0,0 +1,7 @@
+{
+  "defaultRuntime": "codex",
+  "loopMode": "off",
+  "permissionMode": "auto_review",
+  "skillSource": ".agents",
+  "documentLayout": "structured"
+}

package/examples/hospital-homepage/.gaslighting/decisions/ADR-0001-stack.md

@@ -0,0 +1,11 @@
+# ADR-0001: Stack Policy
+
+Date: 2026-05-23
+
+## Decision
+
+No stack hints were provided. Use the default practical web stack unless the user later changes it.
+
+## Consequence
+
+The agent must avoid over-engineering and choose technology that serves the project purpose.

package/examples/hospital-homepage/.gaslighting/decisions/ADR-0002-agent-runtime.md

@@ -0,0 +1,11 @@
+# ADR-0002: Agent Runtime
+
+Date: 2026-05-23
+
+## Decision
+
+Default runtime is `codex`.
+
+Loop mode defaults to `off`.
+
+Permission mode defaults to `auto_review`.

package/examples/hospital-homepage/.gaslighting/features/core-scope/DECISIONS.md

@@ -0,0 +1,5 @@
+# Feature Decisions
+
+- Project type initialized as `hospital_homepage`.
+- Deterministic template generation is used instead of an LLM API.
+- Scope preservation is mandatory.

package/examples/hospital-homepage/.gaslighting/features/core-scope/FEATURE.md

@@ -0,0 +1,7 @@
+# Core Scope Feature
+
+Original request: I want to build a hospital website.
+
+This feature captures the complete MVP scope for `hospital_homepage`.
+
+The agent must not reduce it to a sample, scaffold, or visual-only shell.

package/examples/hospital-homepage/.gaslighting/features/core-scope/RISKS.md

@@ -0,0 +1,5 @@
+# Feature Risks
+
+- Classification confidence: medium
+- Missing information can affect copy, data model, page details, and production readiness.
+- Repetitive surfaces are at risk of being summarized instead of implemented.

package/examples/hospital-homepage/.gaslighting/features/core-scope/TASKS.md

@@ -0,0 +1,17 @@
+# Core Scope Tasks
+
+- [ ] Preserve and restate the project purpose for `hospital_homepage`.
+- [ ] Implement all required MVP pages or feature surfaces.
+- [ ] Implement and verify page/surface: Home
+- [ ] Implement and verify page/surface: Hospital Introduction
+- [ ] Implement and verify page/surface: Departments / Treatments
+- [ ] Implement and verify page/surface: Doctor Profiles
+- [ ] Implement and verify page/surface: Consultation / Contact
+- [ ] Implement and verify page/surface: Location
+- [ ] Implement and verify page/surface: Privacy Policy
+- [ ] Verify build/test/lint/browser flow as appropriate.
+- [ ] Update decisions, missing info, memory, and project care files.
+
+Original request:
+
+> I want to build a hospital website.

package/examples/hospital-homepage/.gaslighting/loops/current-session.json

@@ -0,0 +1,9 @@
+{
+  "active": false,
+  "status": "off",
+  "currentTask": "TASK-0001",
+  "runtime": "codex",
+  "permissionMode": "auto_review",
+  "iterations": 0,
+  "stopRequested": false
+}

package/examples/hospital-homepage/.gaslighting/memory/OPEN_QUESTIONS.md

@@ -0,0 +1,5 @@
+# Open Questions
+
+- Medical department, doctors, and clinic credentials: Replace with verified doctors, treatments, licenses, address, phone, and medical copy.
+- Final brand identity and production copy: Collect final brand name, tone, assets, and legally approved copy before launch.
+- Exact deployment credentials and accounts: Add project-specific env vars and provider accounts before production deployment.

package/examples/hospital-homepage/.gaslighting/memory/PROJECT_MEMORY.md

@@ -0,0 +1,5 @@
+# Project Memory
+
+- Original request: I want to build a hospital website.
+- Project type: hospital_homepage
+- Classification confidence: medium

package/examples/hospital-homepage/.gaslighting/memory/SESSION_LOG.md

@@ -0,0 +1,3 @@
+# Session Log
+
+- 2026-05-23: Gaslighting-engine structured mission initialized for: I want to build a hospital website.

package/examples/hospital-homepage/.gaslighting/mission/COMPLETION_STANDARD.md

@@ -0,0 +1,11 @@
+# Completion Standard
+
+A task is complete only when:
+
+- Requested scope is fully handled.
+- No required item was silently skipped.
+- No placeholder is pretending to be implementation.
+- No TODO replaces requested implementation.
+- Verification was run or the reason it could not run is stated.
+- Assumptions, missing information, and operational care risks are updated.
+- The result can actually be used.

package/examples/hospital-homepage/.gaslighting/mission/EXECUTION_RULES.md

@@ -0,0 +1,20 @@
+# Execution Rules
+
+- Runtime: codex
+- Loop mode: off
+- Permission mode: auto_review
+
+## Non-Negotiables
+
+- Do the actual work.
+- Do not shrink scope.
+- Do not use TODOs as fake implementation.
+- Do not present representative examples as full coverage.
+- Document missing information and continue unless truly blocked.
+- Record operational risk in `operations/PROJECT_CARE.md`.
+
+## Permission Modes
+
+- `ask_each_task`: request approval before each task action.
+- `auto_review`: continue ordinary work; request approval for destructive, publishing, deployment, secret, DNS, payment, MCP install, or global configuration changes.
+- `full_autonomy`: continue without approval, but log every action and never expose secrets.

package/examples/hospital-homepage/.gaslighting/mission/PROJECT_PURPOSE.md

@@ -0,0 +1,20 @@
+# Project Purpose
+
+Original request:
+
+> I want to build a hospital website.
+
+Project type: `hospital_homepage`
+
+The purpose is:
+
+- increase trust
+- generate consultation inquiries
+- support reservation conversion
+- make departments and treatments understandable
+- make doctors and hospital credibility visible
+- help mobile visitors contact the hospital quickly
+- support local SEO
+- make location and contact information obvious
+
+Do not turn this project into a generic showcase. Preserve the business purpose and conversion/operation goals implied by the project type.

package/examples/hospital-homepage/.gaslighting/operations/DEPLOYMENT.md

@@ -0,0 +1,6 @@
+# Deployment Operations
+
+- Deployment provider: unconfirmed until detected or selected.
+- Preview URL policy: missing until confirmed.
+- Rollback path: missing until confirmed.
+- Deployment commands require approval in auto-review mode.

package/examples/hospital-homepage/.gaslighting/operations/DOMAIN.md

@@ -0,0 +1,6 @@
+# Domain Operations
+
+- Production domain: missing until confirmed.
+- DNS provider: missing until confirmed.
+- Domain owner: missing until confirmed.
+- Do not treat missing domain data as implementation-blocking unless launch is requested.

package/examples/hospital-homepage/.gaslighting/operations/ENV.md

@@ -0,0 +1,5 @@
+# Environment Operations
+
+- Keep real secrets out of generated documents.
+- Prefer `.env.example` for required variables.
+- Secret changes require approval in auto-review mode.

package/examples/hospital-homepage/.gaslighting/operations/GIT.md

@@ -0,0 +1,7 @@
+# Git Operations
+
+Project root: `examples/hospital-homepage`
+
+- Keep meaningful checkpoints.
+- Do not rewrite user changes.
+- Record remote changes in decisions.

package/examples/hospital-homepage/.gaslighting/operations/GITHUB.md

@@ -0,0 +1,7 @@
+# GitHub Operations
+
+Project root: `examples/hospital-homepage`
+
+- If no GitHub remote exists, ask for the GitHub URL and offer to connect it.
+- If a remote exists, preserve it unless the user explicitly asks to replace it.
+- Push only when permission mode allows it or approval is granted.

package/examples/hospital-homepage/.gaslighting/operations/PROJECT_CARE.md

@@ -0,0 +1,76 @@
+# PROJECT_CARE.md
+
+This file is the project-care ledger for Gaslighting-engine.
+
+It is not a blocker wall.
+
+It is the place where the agent keeps noticing operational risk, ownership gaps, Git/GitHub status, deployment readiness, domain ownership, and missing production decisions.
+
+The agent must treat this project as mission-critical. If something can put delivery, trust, data, launch, SEO, legal compliance, or operations at risk, record it here and keep pushing it forward.
+
+## Project Snapshot
+
+- Date: 2026-05-23
+- Original request: I want to build a hospital website.
+- Project type: hospital_homepage
+- Classification confidence: medium
+- Project purpose:
+  - increase trust
+  - generate consultation inquiries
+  - support reservation conversion
+  - make departments and treatments understandable
+  - make doctors and hospital credibility visible
+  - help mobile visitors contact the hospital quickly
+  - support local SEO
+  - make location and contact information obvious
+
+## Git And GitHub Registry
+
+| Item | Status | Next Action |
+|---|---|---|
+| Git repository | Detected, branch `main` | Commit meaningful checkpoints. |
+| Origin remote | `https://github.com/nohsangwoo/GaslightingEngineering.git` | Keep remote ownership recorded when it changes. |
+| GitHub remote | Detected | Use GitHub as the source-of-truth remote. |
+
+## Domain And Deployment Registry
+
+| Item | Current Status | Risk | Next Action |
+|---|---|---|---|
+| Production domain | Missing | Users cannot reach production reliably. | Confirm domain owner, DNS provider, and final domain. |
+| DNS provider | Missing | Launch can be delayed by DNS access issues. | Record provider, account owner, and nameserver strategy. |
+| Deployment target | Not confirmed | Environment drift and launch confusion. | Confirm Vercel, Netlify, Cloudflare, or other target. |
+| Preview URL policy | Missing | Stakeholders cannot review safely. | Decide preview deployment workflow. |
+| Rollback path | Missing | Production incidents become slower to recover. | Define rollback command/provider workflow. |
+
+## Care Checklist
+
+- [x] Git repository: Git repository detected on branch main. Next: Keep committing discipline and implementation changes.
+- [x] GitHub remote: GitHub remote detected: https://github.com/nohsangwoo/GaslightingEngineering.git Next: Record repository decisions in DECISION_LOG.md when remote ownership changes.
+- [ ] Project package file: package.json is missing. Next: Create package.json when implementation starts, unless this is not a Node project.
+- [ ] Deployment target: No explicit deployment config detected. Next: Confirm deployment target, production domain, preview environment, and rollback path before launch.
+- [ ] Environment template: .env.example is missing. Next: Add .env.example before sharing the project so required secrets are visible without exposing real values.
+- [ ] Production domain confirmed.
+- [ ] DNS owner confirmed.
+- [ ] Deployment provider confirmed.
+- [ ] Analytics ownership confirmed.
+- [ ] Form/email delivery owner confirmed.
+- [ ] Privacy/legal review path confirmed.
+- [ ] Launch checklist created before production release.
+
+## Agent Care Rules
+
+- Do not stop implementation just because an operational detail is missing.
+- Do make a practical assumption, record it, and keep moving.
+- If Git is not initialized, ask for a GitHub URL and offer the exact commands.
+- If Git is initialized but no GitHub remote exists, ask for the remote URL and offer `git remote add origin <url>`.
+- If the user provides a GitHub URL, run `gaslighting-engine care --github-url <url>` or connect it directly with Git CLI.
+- If GitHub is connected, record the remote URL here and in `DECISION_LOG.md` when it changes.
+- If domain or deployment details are missing, keep warning until they are confirmed.
+- Treat missing domain, deployment, analytics, email, and privacy ownership as mission-critical launch risks, not as reasons to abandon the task.
+- Never turn care warnings into fake blockers.
+
+## Current Care Warnings
+
+- Project package file: package.json is missing. Action: Create package.json when implementation starts, unless this is not a Node project.
+- Deployment target: No explicit deployment config detected. Action: Confirm deployment target, production domain, preview environment, and rollback path before launch.
+- Environment template: .env.example is missing. Action: Add .env.example before sharing the project so required secrets are visible without exposing real values.

package/examples/hospital-homepage/.gaslighting/pages/consultation-contact/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Consultation / Contact Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/hospital-homepage/.gaslighting/pages/consultation-contact/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Consultation / Contact Page PRD
+
+Project type: `hospital_homepage`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.

package/examples/hospital-homepage/.gaslighting/pages/departments-treatments/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Departments / Treatments Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/hospital-homepage/.gaslighting/pages/departments-treatments/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Departments / Treatments Page PRD
+
+Project type: `hospital_homepage`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.

package/examples/hospital-homepage/.gaslighting/pages/doctor-profiles/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Doctor Profiles Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/hospital-homepage/.gaslighting/pages/doctor-profiles/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Doctor Profiles Page PRD
+
+Project type: `hospital_homepage`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.

package/examples/hospital-homepage/.gaslighting/pages/home/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Home Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/hospital-homepage/.gaslighting/pages/home/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Home Page PRD
+
+Project type: `hospital_homepage`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.

package/examples/hospital-homepage/.gaslighting/pages/hospital-introduction/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Hospital Introduction Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/hospital-homepage/.gaslighting/pages/hospital-introduction/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Hospital Introduction Page PRD
+
+Project type: `hospital_homepage`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.

package/examples/hospital-homepage/.gaslighting/pages/location/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Location Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/hospital-homepage/.gaslighting/pages/location/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Location Page PRD
+
+Project type: `hospital_homepage`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.

package/examples/hospital-homepage/.gaslighting/pages/privacy-policy/ACCEPTANCE.md

@@ -0,0 +1,7 @@
+# Privacy Policy Acceptance Criteria
+
+- [ ] Page purpose is visible.
+- [ ] Required content is not placeholder-only.
+- [ ] CTA or operational action is usable.
+- [ ] Mobile layout is usable.
+- [ ] No TODO replaces implementation.

package/examples/hospital-homepage/.gaslighting/pages/privacy-policy/PAGE_PRD.md

@@ -0,0 +1,15 @@
+# Privacy Policy Page PRD
+
+Project type: `hospital_homepage`
+
+## Purpose
+
+This page must support the project purpose and not become decorative filler.
+
+## Required Coverage
+
+- Clear user goal.
+- Clear content hierarchy.
+- Clear CTA or operational action.
+- Mobile usability.
+- Empty/error states when relevant.