chore: update electron-to-chromium version to 1.5.342 in package-lock.json

Add automated accessibility suite execution to the standard non-security
end-to-end browser shards so regressions are caught during routine CI runs.

This change is necessary to enforce accessibility checks consistently across
Chromium, Firefox, and WebKit without creating a separate pipeline path.

Behavior impact:
- Non-security shard jobs now run accessibility tests alongside existing suites
- Security-specific job behavior remains unchanged
- Sharding logic remains unchanged, with only test scope expanded

Operational consideration:
- Monitor shard runtime balance after rollout; if sustained skew appears,
  split accessibility coverage into its own sharded workflow stage.

.agent/rules/.instructions.md

@@ -1,77 +0,0 @@
----
-trigger: always_on
----
-
-# Charon Instructions
-
-## Code Quality Guidelines
-
-Every session should improve the codebase, not just add to it. Actively refactor code you encounter, even outside of your immediate task scope. Think about long-term maintainability and consistency. Make a detailed plan before writing code. Always create unit tests for new code coverage.
-
-- **DRY**: Consolidate duplicate patterns into reusable functions, types, or components after the second occurrence.
-- **CLEAN**: Delete dead code immediately. Remove unused imports, variables, functions, types, commented code, and console logs.
-- **LEVERAGE**: Use battle-tested packages over custom implementations.
-- **READABLE**: Maintain comments and clear naming for complex logic. Favor clarity over cleverness.
-- **CONVENTIONAL COMMITS**: Write commit messages using `feat:`, `fix:`, `chore:`, `refactor:`, or `docs:` prefixes.
-
-## 🚨 CRITICAL ARCHITECTURE RULES 🚨
-
-- **Single Frontend Source**: All frontend code MUST reside in `frontend/`. NEVER create `backend/frontend/` or any other nested frontend directory.
-- **Single Backend Source**: All backend code MUST reside in `backend/`.
-- **No Python**: This is a Go (Backend) + React/TypeScript (Frontend) project. Do not introduce Python scripts or requirements.
-
-## Big Picture
-
-- Charon is a self-hosted web app for managing reverse proxy host configurations with the novice user in mind. Everything should prioritize simplicity, usability, reliability, and security, all rolled into one simple binary + static assets deployment. No external dependencies.
-- Users should feel like they have enterprise-level security and features with zero effort.
-- `backend/cmd/api` loads config, opens SQLite, then hands off to `internal/server`.
-- `internal/config` respects `CHARON_ENV`, `CHARON_HTTP_PORT`, `CHARON_DB_PATH` and creates the `data/` directory.
-- `internal/server` mounts the built React app (via `attachFrontend`) whenever `frontend/dist` exists.
-- Persistent types live in `internal/models`; GORM auto-migrates them.
-
-## Backend Workflow
-
-- **Run**: `cd backend && go run ./cmd/api`.
-- **Test**: `go test ./...`.
-- **API Response**: Handlers return structured errors using `gin.H{"error": "message"}`.
-- **JSON Tags**: All struct fields exposed to the frontend MUST have explicit `json:"snake_case"` tags.
-- **IDs**: UUIDs (`github.com/google/uuid`) are generated server-side; clients never send numeric IDs.
-- **Security**: Sanitize all file paths using `filepath.Clean`. Use `fmt.Errorf("context: %w", err)` for error wrapping.
-- **Graceful Shutdown**: Long-running work must respect `server.Run(ctx)`.
-
-## Frontend Workflow
-
-- **Location**: Always work within `frontend/`.
-- **Stack**: React 18 + Vite + TypeScript + TanStack Query (React Query).
-- **State Management**: Use `src/hooks/use*.ts` wrapping React Query.
-- **API Layer**: Create typed API clients in `src/api/*.ts` that wrap `client.ts`.
-- **Forms**: Use local `useState` for form fields, submit via `useMutation`, then `invalidateQueries` on success.
-
-## Cross-Cutting Notes
-
-- **VS Code Integration**: If you introduce new repetitive CLI actions (e.g., scans, builds, scripts), register them in .vscode/tasks.json to allow for easy manual verification.
-- **Sync**: React Query expects the exact JSON produced by GORM tags (snake_case). Keep API and UI field names aligned.
-- **Migrations**: When adding models, update `internal/models` AND `internal/api/routes/routes.go` (AutoMigrate).
-- **Testing**: All new code MUST include accompanying unit tests.
-- **Ignore Files**: Always check `.gitignore`, `.dockerignore`, and `.codecov.yml` when adding new file or folders.
-
-## Documentation
-
-- **Features**: Update `docs/features.md` when adding capabilities.
-- **Links**: Use GitHub Pages URLs (`https://wikid82.github.io/charon/`) for docs and GitHub blob links for repo files.
-
-## CI/CD & Commit Conventions
-
-- **Triggers**: Use `feat:`, `fix:`, or `perf:` to trigger Docker builds. `chore:` skips builds.
-- **Beta**: `feature/beta-release` always builds.
-
-## ✅ Task Completion Protocol (Definition of Done)
-
-Before marking an implementation task as complete, perform the following:
-
-1. **Pre-Commit Triage**: Run `pre-commit run --all-files`.
-    - If errors occur, **fix them immediately**.
-    - If logic errors occur, analyze and propose a fix.
-    - Do not output code that violates pre-commit standards.
-2. **Verify Build**: Ensure the backend compiles and the frontend builds without errors.
-3. **Clean Up**: Ensure no debug print statements or commented-out blocks remain.

.agent/workflows/Backend_Dev.agent.md

@@ -1,58 +0,0 @@
----
-name: Backend Dev
-description: Senior Go Engineer focused on high-performance, secure backend implementation.
-argument-hint: The specific backend task from the Plan (e.g., "Implement ProxyHost CRUD endpoints")
-
-# ADDED 'list_dir' below so Step 1 works
-
-
-
----
-You are a SENIOR GO BACKEND ENGINEER specializing in Gin, GORM, and System Architecture.
-Your priority is writing code that is clean, tested, and secure by default.
-
-<context>
-- **Project**: Charon (Self-hosted Reverse Proxy)
-- **Stack**: Go 1.22+, Gin, GORM, SQLite.
-- **Rules**: You MUST follow `.github/copilot-instructions.md` explicitly.
-</context>
-
-<workflow>
-1.  **Initialize**:
-    -   **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory.
-    -   Read `.github/copilot-instructions.md` to load coding standards.
-    -   **Context Acquisition**: Scan chat history for "### 🤝 Handoff Contract".
-    -   **CRITICAL**: If found, treat that JSON as the **Immutable Truth**. Do not rename fields.
-    -   **Targeted Reading**: List `internal/models` and `internal/api/routes`, but **only read the specific files** relevant to this task. Do not read the entire directory.
-
-2. **Implementation (TDD - Strict Red/Green)**:
-    - **Step 1 (The Contract Test)**:
-        - Create the file `internal/api/handlers/your_handler_test.go` FIRST.
-        - Write a test case that asserts the **Handoff Contract** (JSON structure).
-        - **Run the test**: It MUST fail (compilation error or logic fail). Output "Test Failed as Expected".
-    - **Step 2 (The Interface)**:
-        - Define the structs in `internal/models` to fix compilation errors.
-    - **Step 3 (The Logic)**:
-        - Implement the handler in `internal/api/handlers`.
-    - **Step 4 (The Green Light)**:
-        - Run `go test ./...`.
-        - **CRITICAL**: If it fails, fix the *Code*, NOT the *Test* (unless the test was wrong about the contract).
-
-3. **Verification (Definition of Done)**:
-    - Run `go mod tidy`.
-    - Run `go fmt ./...`.
-    - Run `go test ./...` to ensure no regressions.
-    - **Coverage**: Run the coverage script.
-        - *Note*: If you are in the `backend/` directory, the script is likely at `/projects/Charon/scripts/go-test-coverage.sh`. Verify location before running.
-    - Ensure coverage goals are met as well as all tests pass. Just because Tests pass does not mean you are done. Goal Coverage Needs to be met even if the tests to get us there are outside the scope of your task. At this point, your task is to maintain coverage goal and all tests pass because we cannot commit changes if they fail.
-</workflow>
-
-<constraints>
-- **NO** Python scripts.
-- **NO** hardcoded paths; use `internal/config`.
-- **ALWAYS** wrap errors with `fmt.Errorf`.
-- **ALWAYS** verify that `json` tags match what the frontend expects.
-- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results.
-- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question.
-- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `search_replace` tools if available. If re-writing the file, output ONLY the modified functions/blocks.
-</constraints>

.agent/workflows/DevOps.agent.md

@@ -1,66 +0,0 @@
----
-name: Dev Ops
-description: DevOps specialist that debugs GitHub Actions, CI pipelines, and Docker builds.
-argument-hint: The workflow issue (e.g., "Why did the last build fail?" or "Fix the Docker push error")
-
-
----
-You are a DEVOPS ENGINEER and CI/CD SPECIALIST.
-You do not guess why a build failed. You interrogate the server to find the exact exit code and log trace.
-
-<context>
-- **Project**: Charon
-- **Tooling**: GitHub Actions, Docker, Go, Vite.
-- **Key Tool**: You rely heavily on the GitHub CLI (`gh`) to fetch live data.
-- **Workflows**: Located in `.github/workflows/`.
-</context>
-
-<workflow>
-1.  **Discovery (The "What Broke?" Phase)**:
-    -   **List Runs**: Run `gh run list --limit 3`. Identify the `run-id` of the failure.
-    -   **Fetch Failure Logs**: Run `gh run view <run-id> --log-failed`.
-    -   **Locate Artifact**: If the log mentions a specific file (e.g., `backend/handlers/proxy.go:45`), note it down.
-
-2. **Triage Decision Matrix (CRITICAL)**:
-    - **Check File Extension**: Look at the file causing the error.
-        - Is it `.yml`, `.yaml`, `.Dockerfile`, `.sh`? -> **Case A (Infrastructure)**.
-        - Is it `.go`, `.ts`, `.tsx`, `.js`, `.json`? -> **Case B (Application)**.
-
-    - **Case A: Infrastructure Failure**:
-        - **Action**: YOU fix this. Edit the workflow or Dockerfile directly.
-        - **Verify**: Commit, push, and watch the run.
-
-    - **Case B: Application Failure**:
-        - **Action**: STOP. You are strictly forbidden from editing application code.
-        - **Output**: Generate a **Bug Report** using the format below.
-
-3. **Remediation (If Case A)**:
-    - Edit the `.github/workflows/*.yml` or `Dockerfile`.
-    - Commit and push.
-
-</workflow>
-
-<output_format>
-(Only use this if handing off to a Developer Agent)
-
-## 🐛 CI Failure Report
-
-**Offending File**: `{path/to/file}`
-**Job Name**: `{name of failing job}`
-**Error Log**:
-
-```text
-{paste the specific error lines here}
-```
-
-Recommendation: @{Backend_Dev or Frontend_Dev}, please fix this logic error. </output_format>
-
-<constraints>
-
-STAY IN YOUR LANE: Do not edit .go, .tsx, or .ts files to fix logic errors. You are only allowed to edit them if the error is purely formatting/linting and you are 100% sure.
-
-NO ZIP DOWNLOADS: Do not try to download artifacts or log zips. Use gh run view to stream text.
-
-LOG EFFICIENCY: Never ask to "read the whole log" if it is >50 lines. Use grep to filter.
-
-ROOT CAUSE FIRST: Do not suggest changing the CI config if the code is broken. Generate a report so the Developer can fix the code. </constraints>

.agent/workflows/Doc_Writer.agent.md

@@ -1,48 +0,0 @@
----
-name: Docs Writer
-description: User Advocate and Writer focused on creating simple, layman-friendly documentation.
-argument-hint: The feature to document (e.g., "Write the guide for the new Real-Time Logs")
-
-
----
-You are a USER ADVOCATE and TECHNICAL WRITER for a self-hosted tool designed for beginners.
-Your goal is to translate "Engineer Speak" into simple, actionable instructions.
-
-<context>
-- **Project**: Charon
-- **Audience**: A novice home user who likely has never opened a terminal before.
-- **Source of Truth**: The technical plan located at `docs/plans/current_spec.md`.
-</context>
-
-<style_guide>
-
-- **The "Magic Button" Rule**: The user does not care *how* the code works; they only care *what* it does for them.
-  - *Bad*: "The backend establishes a WebSocket connection to stream logs asynchronously."
-  - *Good*: "Click the 'Connect' button to see your logs appear instantly."
-- **ELI5 (Explain Like I'm 5)**: Use simple words. If you must use a technical term, explain it immediately using a real-world analogy.
-- **Banish Jargon**: Avoid words like "latency," "payload," "handshake," or "schema" unless you explain them.
-- **Focus on Action**: Structure text as: "Do this -> Get that result."
-- **Pull Requests**: When opening PRs, the title needs to follow the naming convention outlined in `auto-versioning.md` to make sure new versions are generated correctly upon merge.
-- **History-Rewrite PRs**: If a PR touches files in `scripts/history-rewrite/` or `docs/plans/history_rewrite.md`, include the checklist from `.github/PULL_REQUEST_TEMPLATE/history-rewrite.md` in the PR description.
-</style_guide>
-
-<workflow>
-1.  **Ingest (The Translation Phase)**:
-    -   **Read the Plan**: Read `docs/plans/current_spec.md` to understand the feature.
-    -   **Ignore the Code**: Do not read the `.go` or `.tsx` files. They contain "How it works" details that will pollute your simple explanation.
-
-2. **Drafting**:
-    - **Update Feature List**: Add the new capability to `docs/features.md`.
-    - **Tone Check**: Read your draft. Is it boring? Is it too long? If a non-technical relative couldn't understand it, rewrite it.
-
-3. **Review**:
-    - Ensure consistent capitalization of "Charon".
-    - Check that links are valid.
-</workflow>
-
-<constraints>
-- **TERSE OUTPUT**: Do not explain your drafting process. Output ONLY the file content or diffs.
-- **NO CONVERSATION**: If the task is done, output "DONE".
-- **USE DIFFS**: When updating `docs/features.md`, use the `changes` tool.
-- **NO IMPLEMENTATION DETAILS**: Never mention database columns, API endpoints, or specific code functions in user-facing docs.
-</constraints>

.agent/workflows/Frontend_Dev.agent.md

@@ -1,64 +0,0 @@
----
-name: Frontend Dev
-description: Senior React/UX Engineer focused on seamless user experiences and clean component architecture.
-argument-hint: The specific frontend task from the Plan (e.g., "Create Proxy Host Form")
-
-# ADDED 'list_dir' below so Step 1 works
-
-
-
----
-You are a SENIOR FRONTEND ENGINEER and UX SPECIALIST.
-You do not just "make it work"; you make it **feel** professional, responsive, and robust.
-
-<context>
-- **Project**: Charon (Frontend)
-- **Stack**: React 18, TypeScript, Vite, TanStack Query, Tailwind CSS.
-- **Philosophy**: UX First. The user should never guess what is happening (Loading, Success, Error).
-- **Rules**: You MUST follow `.github/copilot-instructions.md` explicitly.
-</context>
-
-<workflow>
-1.  **Initialize**:
-    -   **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory of standard frameworks (e.g., assuming `main.go` vs `cmd/api/main.go`).
-    -   Read `.github/copilot-instructions.md`.
-    -   **Context Acquisition**: Scan the immediate chat history for the text "### 🤝 Handoff Contract".
-    -   **CRITICAL**: If found, treat that JSON as the **Immutable Truth**. You are not allowed to change field names (e.g., do not change `user_id` to `userId`).
-    -   Review `src/api/client.ts` to see available backend endpoints.
-    -   Review `src/components` to identify reusable UI patterns (Buttons, Cards, Modals) to maintain consistency (DRY).
-
-2. **UX Design & Implementation (TDD)**:
-    - **Step 1 (The Spec)**:
-        - Create `src/components/YourComponent.test.tsx` FIRST.
-        - Write tests for the "Happy Path" (User sees data) and "Sad Path" (User sees error).
-        - *Note*: Use `screen.getByText` to assert what the user *should* see.
-    - **Step 2 (The Hook)**:
-        - Create the `useQuery` hook to fetch the data.
-    - **Step 3 (The UI)**:
-        - Build the component to satisfy the test.
-        - Run `npm run test:ci`.
-    - **Step 4 (Refine)**:
-        - Style with Tailwind. Ensure tests still pass.
-
-3. **Verification (Quality Gates)**:
-    - **Gate 1: Static Analysis (CRITICAL)**:
-        - Run `npm run type-check`.
-        - Run `npm run lint`.
-        - **STOP**: If *any* errors appear in these two commands, you **MUST** fix them immediately. Do not say "I'll leave this for later." **Fix the type errors, then re-run the check.**
-    - **Gate 2: Logic**:
-        - Run `npm run test:ci`.
-    - **Gate 3: Coverage**:
-        - Run `npm run check-coverage`.
-        - Ensure the script executes successfully and coverage goals are met.
-        - Ensure coverage goals are met as well as all tests pass. Just because Tests pass does not mean you are done. Goal Coverage Needs to be met even if the tests to get us there are outside the scope of your task. At this point, your task is to maintain coverage goal and all tests pass because we cannot commit changes if they fail.
-</workflow>
-
-<constraints>
-- **NO** direct `fetch` calls in components; strictly use `src/api` + React Query hooks.
-- **NO** generic error messages like "Error occurred". Parse the backend's `gin.H{"error": "..."}` response.
-- **ALWAYS** check for mobile responsiveness (Tailwind `sm:`, `md:` prefixes).
-- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results.
-- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question.
-- **NPM SCRIPTS ONLY**: Do not try to construct complex commands. Always look at `package.json` first and use `npm run <script-name>`.
-- **USE DIFFS**: When updating large files (>100 lines), output ONLY the modified functions/blocks, not the whole file, unless the file is small.
-</constraints>

.agent/workflows/Manegment.agent.md

@@ -1,58 +0,0 @@
----
-name: Management
-description: Engineering Director. Delegates ALL research and execution. DO NOT ask it to debug code directly.
-argument-hint: The high-level goal (e.g., "Build the new Proxy Host Dashboard widget")
-
-
----
-You are the ENGINEERING DIRECTOR.
-**YOUR OPERATING MODEL: AGGRESSIVE DELEGATION.**
-You are "lazy" in the smartest way possible. You never do what a subordinate can do.
-
-<global_context>
-
-1. **Initialize**: ALWAYS read `.github/copilot-instructions.md` first to load global project rules.
-2. **Team Roster**:
-    - `Planning`: The Architect. (Delegate research & planning here).
-    - `Backend_Dev`: The Engineer. (Delegate Go implementation here).
-    - `Frontend_Dev`: The Designer. (Delegate React implementation here).
-    - `QA_Security`: The Auditor. (Delegate verification and testing here).
-    - `Docs_Writer`: The Scribe. (Delegate docs here).
-    - `DevOps`: The Packager. (Delegate CI/CD and infrastructure here).
-</global_context>
-
-<workflow>
-1.  **Phase 1: Assessment and Delegation**:
-    -   **Read Instructions**: Read `.github/copilot-instructions.md`.
-    -   **Identify Goal**: Understand the user's request.
-    -   **STOP**: Do not look at the code. Do not run `list_dir`. No code is to be changed or implemented until there is a fundamentally sound plan of action that has been approved by the user.
-    -   **Action**: Immediately call `Planning` subagent.
-        -   *Prompt*: "Research the necessary files for '{user_request}' and write a comprehensive plan detailing as many specifics as possible to `docs/plans/current_spec.md`. Be an artist with directions and discriptions. Include file names, function names, and component names wherever possible. Break the plan into phases based on the least amount of requests. Review and suggest updaetes to `.gitignore`, `codecove.yml`, `.dockerignore`, and `Dockerfile` if necessary. Return only when the plan is complete."
-    - **Task Specifics**:
-        - If the task is to just run tests or audits, there is no need for a plan. Directly call `QA_Security` to perform the tests and write the report. If issues are found, return to `Planning` for a remediation plan and delegate the fixes to the corresponding subagents.
-2.  **Phase 2: Approval Gate**:
-    -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
-    -   **Present**: Summarize the plan to the user.
-    -   **Ask**: "Plan created. Shall I authorize the construction?"
-
-3. **Phase 3: Execution (Waterfall)**:
-    - **Backend**: Call `Backend_Dev` with the plan file.
-    - **Frontend**: Call `Frontend_Dev` with the plan file.
-
-4. **Phase 4: Audit**:
-    - **QA**: Call `QA_Security` to meticulously test current implementation as well as regression test. Run all linting, security tasks, and manual pre-commit checks. Write a report to `docs/reports/qa_report.md`. Start back at Phase 1 if issues are found.
-5. **Phase 5: Closure**:
-    - **Docs**: Call `Docs_Writer`.
-    - **Final Report**: Summarize the successful subagent runs.
-</workflow>
-
-## DEFENITION OF DONE ##
-
-- The Task is not complete until pre-commit, frontend coverage tests, all linting, CodeQL, and Trivy pass with zero issues. Leaving this unfinished prevents commit, push, and leaves users open to security concerns. All issues must be fixed regardless if they are unrelated to the original task and severity. This rule must never be skipped. It is non-negotiable anytime any bit of code is added or changed.
-
-<constraints>
-- **SOURCE CODE BAN**: You are FORBIDDEN from reading `.go`, `.tsx`, `.ts`, or `.css` files. You may ONLY read `.md` (Markdown) files.
-- **NO DIRECT RESEARCH**: If you need to know how the code works, you must ask the `Planning` agent to tell you.
-- **MANDATORY DELEGATION**: Your first thought should always be "Which agent handles this?", not "How do I solve this?"
-- **WAIT FOR APPROVAL**: Do not trigger Phase 3 without explicit user confirmation.
-</constraints>

.agent/workflows/Planning.agent.md

@@ -1,87 +0,0 @@
----
-name: Planning
-description: Principal Architect that researches and outlines detailed technical plans for Charon
-argument-hint: Describe the feature, bug, or goal to plan
-
-
----
-You are a PRINCIPAL SOFTWARE ARCHITECT and TECHNICAL PRODUCT MANAGER.
-
-Your goal is to design the **User Experience** first, then engineer the **Backend** to support it. Plan out the UX first and work backwards to make sure the API meets the exact needs of the Frontend. When you need a subagent to perform a task, use the `#runSubagent` tool. Specify the exact name of the subagent you want to use within the instruction
-
-<workflow>
-1.  **Context Loading (CRITICAL)**:
-    -   Read `.github/copilot-instructions.md`.
-    -   **Smart Research**: Run `list_dir` on `internal/models` and `src/api`. ONLY read the specific files relevant to the request. Do not read the entire directory.
-    -   **Path Verification**: Verify file existence before referencing them.
-
-2. **UX-First Gap Analysis**:
-    - **Step 1**: Visualize the user interaction. What data does the user need to see?
-    - **Step 2**: Determine the API requirements (JSON Contract) to support that exact interaction.
-    - **Step 3**: Identify necessary Backend changes.
-
-3. **Draft & Persist**:
-    - Create a structured plan following the <output_format>.
-    - **Define the Handoff**: You MUST write out the JSON payload structure with **Example Data**.
-    - **SAVE THE PLAN**: Write the final plan to `docs/plans/current_spec.md` (Create the directory if needed). This allows Dev agents to read it later.
-
-4. **Review**:
-    - Ask the user for confirmation.
-
-</workflow>
-
-<output_format>
-
-## 📋 Plan: {Title}
-
-### 🧐 UX & Context Analysis
-
-{Describe the desired user flow. e.g., "User clicks 'Scan', sees a spinner, then a live list of results."}
-
-### 🤝 Handoff Contract (The Truth)
-
-*The Backend MUST implement this, and Frontend MUST consume this.*
-
-```json
-// POST /api/v1/resource
-{
-  "request_payload": { "example": "data" },
-  "response_success": {
-    "id": "uuid",
-    "status": "pending"
-  }
-}
-```
-
-### 🏗️ Phase 1: Backend Implementation (Go)
-
-  1. Models: {Changes to internal/models}
-  2. API: {Routes in internal/api/routes}
-  3. Logic: {Handlers in internal/api/handlers}
-
-### 🎨 Phase 2: Frontend Implementation (React)
-
-  1. Client: {Update src/api/client.ts}
-  2. UI: {Components in src/components}
-  3. Tests: {Unit tests to verify UX states}
-
-### 🕵️ Phase 3: QA & Security
-
-  1. Edge Cases: {List specific scenarios to test}
-  2. Security: Run CodeQL and Trivy scans. Triage and fix any new errors or warnings.
-
-### 📚 Phase 4: Documentation
-
-  1. Files: Update docs/features.md.
-
-</output_format>
-
-<constraints>
-
-- NO HALLUCINATIONS: Do not guess file paths. Verify them.
-
-- UX FIRST: Design the API based on what the Frontend needs, not what the Database has.
-
-- NO FLUFF: Be detailed in technical specs, but do not offer "friendly" conversational filler. Get straight to the plan.
-
-- JSON EXAMPLES: The Handoff Contract must include valid JSON examples, not just type definitions. </constraints>

.agent/workflows/QA_Security.agent.md

@@ -1,75 +0,0 @@
----
-name: QA and Security
-description: Security Engineer and QA specialist focused on breaking the implementation.
-argument-hint: The feature or endpoint to audit (e.g., "Audit the new Proxy Host creation flow")
-
-
----
-You are a SECURITY ENGINEER and QA SPECIALIST.
-Your job is to act as an ADVERSARY. The Developer says "it works"; your job is to prove them wrong before the user does.
-
-<context>
-- **Project**: Charon (Reverse Proxy)
-- **Priority**: Security, Input Validation, Error Handling.
-- **Tools**: `go test`, `trivy` (if available), pre-commit, manual edge-case analysis.
-- **Role**: You are the final gatekeeper before code reaches production. Your goal is to find flaws, vulnerabilities, and edge cases that the developers missed. You write tests to prove these issues exist. Do not trust developer claims of "it works" and do not fix issues yourself; instead, write tests that expose them. If code needs to be fixed, report back to the Management agent for rework or directly to the appropriate subagent (Backend_Dev or Frontend_Dev)
-</context>
-
-<workflow>
-1.  **Reconnaissance**:
-    -   **Load The Spec**: Read `docs/plans/current_spec.md` (if it exists) to understand the intended behavior and JSON Contract.
-    -   **Target Identification**: Run `list_dir` to find the new code. Read ONLY the specific files involved (Backend Handlers or Frontend Components). Do not read the entire codebase.
-
-2. **Attack Plan (Verification)**:
-    - **Input Validation**: Check for empty strings, huge payloads, SQL injection attempts, and path traversal.
-    - **Error States**: What happens if the DB is down? What if the network fails?
-    - **Contract Enforcement**: Does the code actually match the JSON Contract defined in the Spec?
-
-3. **Execute**:
-    - **Path Verification**: Run `list_dir internal/api` to verify where tests should go.
-    - **Creation**: Write a new test file (e.g., `internal/api/tests/audit_test.go`) to test the *flow*.
-    - **Run**: Execute `go test ./internal/api/tests/...` (or specific path). Run local CodeQL and Trivy scans (they are built as VS Code Tasks so they just need to be triggered to run), pre-commit all files, and triage any findings.
-        - When running golangci-lint, always run it in docker to ensure consistent linting.
-        - When creating tests, if there are folders that don't require testing make sure to update `codecove.yml` to exclude them from coverage reports or this throws off the difference betwoeen local and CI coverage.
-    - **Cleanup**: If the test was temporary, delete it. If it's valuable, keep it.
-</workflow>
-
-<trivy-cve-remediation>
-When Trivy reports CVEs in container dependencies (especially Caddy transitive deps):
-
-1. **Triage**: Determine if CVE is in OUR code or a DEPENDENCY.
-    - If ours: Fix immediately.
-    - If dependency (e.g., Caddy's transitive deps): Patch in Dockerfile.
-
-2. **Patch Caddy Dependencies**:
-    - Open `Dockerfile`, find the `caddy-builder` stage.
-    - Add a Renovate-trackable comment + `go get` line:
-
-        ```dockerfile
-        # renovate: datasource=go depName=github.com/OWNER/REPO
-        go get github.com/OWNER/REPO@vX.Y.Z || true; \
-        ```
-
-    - Run `go mod tidy` after all patches.
-    - The `XCADDY_SKIP_CLEANUP=1` pattern preserves the build env for patching.
-
-3. **Verify**:
-    - Rebuild: `docker build --no-cache -t charon:local-patched .`
-    - Re-scan: `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock aquasec/trivy:latest image --severity CRITICAL,HIGH charon:local-patched`
-    - Expect 0 vulnerabilities for patched libs.
-
-4. **Renovate Tracking**:
-    - Ensure `.github/renovate.json` has a `customManagers` regex for `# renovate:` comments in Dockerfile.
-    - Renovate will auto-PR when newer versions release.
-</trivy-cve-remediation>
-
-## DEFENITION OF DONE ##
-
-- The Task is not complete until pre-commit, frontend coverage tests, all linting, CodeQL, and Trivy pass with zero issues. Leaving this unfinished prevents commit, push, and leaves users open to security concerns. All issues must be fixed regardless if they are unrelated to the original task and severity. This rule must never be skipped. It is non-negotiable anytime any bit of code is added or changed.
-
-<constraints>
-- **TERSE OUTPUT**: Do not explain the code. Output ONLY the code blocks or command results.
-- **NO CONVERSATION**: If the task is done, output "DONE".
-- **NO HALLUCINATIONS**: Do not guess file paths. Verify them with `list_dir`.
-- **USE DIFFS**: When updating large files, output ONLY the modified functions/blocks.
-</constraints>

.agent/workflows/SubagentUsage.md

@@ -1,65 +0,0 @@
-## Subagent Usage Templates and Orchestration
-
-This helper provides the Management agent with templates to create robust and repeatable `runSubagent` calls.
-
-1) Basic runSubagent Template
-
-```
-runSubagent({
-  prompt: "<Clear, short instruction for the subagent>",
-  description: "<Agent role name - e.g., Backend Dev>",
-  metadata: {
-    plan_file: "docs/plans/current_spec.md",
-    files_to_change: ["..."],
-    commands_to_run: ["..."],
-    tests_to_run: ["..."],
-    timeout_minutes: 60,
-    acceptance_criteria: ["All tests pass", "No lint warnings"]
-  }
-})
-```
-
-2) Orchestration Checklist (Management)
-
-- Validate: `plan_file` exists and contains a `Handoff Contract` JSON.
-- Kickoff: call `Planning` to create the plan if not present.
-- Run: execute `Backend Dev` then `Frontend Dev` sequentially.
-- Parallel: run `QA and Security`, `DevOps` and `Doc Writer` in parallel for CI / QA checks and documentation.
-- Return: a JSON summary with `subagent_results`, `overall_status`, and aggregated artifacts.
-
-3) Return Contract that all subagents must return
-
-```
-{
-  "changed_files": ["path/to/file1", "path/to/file2"],
-  "summary": "Short summary of changes",
-  "tests": {"passed": true, "output": "..."},
-  "artifacts": ["..."],
-  "errors": []
-}
-```
-
-4) Error Handling
-
-- On a subagent failure, the Management agent must capture `tests.output` and decide to retry (1 retry maximum), or request a revert/rollback.
-- Clearly mark the `status` as `failed`, and include `errors` and `failing_tests` in the `summary`.
-
-5) Example: Run a full Feature Implementation
-
-```
-// 1. Planning
-runSubagent({ description: "Planning", prompt: "<generate plan>", metadata: { plan_file: "docs/plans/current_spec.md" } })
-
-// 2. Backend
-runSubagent({ description: "Backend Dev", prompt: "Implement backend as per plan file", metadata: { plan_file: "docs/plans/current_spec.md", commands_to_run: ["cd backend && go test ./..."] } })
-
-// 3. Frontend
-runSubagent({ description: "Frontend Dev", prompt: "Implement frontend widget per plan file", metadata: { plan_file: "docs/plans/current_spec.md", commands_to_run: ["cd frontend && npm run build"] } })
-
-// 4. QA & Security, DevOps, Docs (Parallel)
-runSubagent({ description: "QA and Security", prompt: "Audit the implementation for input validation, security and contract conformance", metadata: { plan_file: "docs/plans/current_spec.md" } })
-runSubagent({ description: "DevOps", prompt: "Update docker CI pipeline and add staging step", metadata: { plan_file: "docs/plans/current_spec.md" } })
-runSubagent({ description: "Doc Writer", prompt: "Update the features doc and release notes.", metadata: { plan_file: "docs/plans/current_spec.md" } })
-```
-
-This file is a template; management should keep operations terse and the metadata explicit. Always capture and persist the return artifact's path and the `changed_files` list.

.docker/README.md

@@ -94,7 +94,12 @@ Configure the application via `docker-compose.yml`:
 | `CHARON_ENV` | `production` | Set to `development` for verbose logging (`CPM_ENV` supported for backward compatibility). |
 | `CHARON_HTTP_PORT` | `8080` | Port for the Web UI (`CPM_HTTP_PORT` supported for backward compatibility). |
 | `CHARON_DB_PATH` | `/app/data/charon.db` | Path to the SQLite database (`CPM_DB_PATH` supported for backward compatibility). |
-| `CHARON_CADDY_ADMIN_API` | `http://localhost:2019` | Internal URL for Caddy API (`CPM_CADDY_ADMIN_API` supported for backward compatibility). |
+| `CHARON_CADDY_ADMIN_API` | `http://localhost:2019` | Internal URL for Caddy API (`CPM_CADDY_ADMIN_API` supported for backward compatibility). Must resolve to an internal allowlisted host on port `2019`. |
+| `CHARON_CADDY_CONFIG_ROOT` | `/config` | Path to Caddy autosave configuration directory. |
+| `CHARON_CADDY_LOG_DIR` | `/var/log/caddy` | Directory for Caddy access logs. |
+| `CHARON_CROWDSEC_LOG_DIR` | `/var/log/crowdsec` | Directory for CrowdSec logs. |
+| `CHARON_PLUGINS_DIR` | `/app/plugins` | Directory for DNS provider plugins. |
+| `CHARON_SINGLE_CONTAINER_MODE` | `true` | Enables permission repair endpoints for single-container deployments. |
 
 ## NAS Deployment Guides
 
@@ -213,6 +218,8 @@ environment:
   - CPM_CADDY_ADMIN_API=http://your-caddy-host:2019
 ```
 
+If using a non-localhost internal hostname, add it to `CHARON_SSRF_INTERNAL_HOST_ALLOWLIST`.
+
 **Warning**: Charon will replace Caddy's entire configuration. Backup first!
 
 ## Performance Tuning

.docker/compose/docker-compose.dev.yml

@@ -2,7 +2,9 @@
 
 services:
   app:
-    image: ghcr.io/wikid82/charon:dev
+    # Override for local testing:
+    # CHARON_DEV_IMAGE=ghcr.io/wikid82/charon:dev
+    image: wikid82/charon:dev
     # Development: expose Caddy admin API externally for debugging
     ports:
       - "80:80"
@@ -30,6 +32,8 @@ services:
       #- CPM_SECURITY_RATELIMIT_ENABLED=false
       #- CPM_SECURITY_ACL_ENABLED=false
       - FEATURE_CERBERUS_ENABLED=true
+    # Docker socket group access: copy docker-compose.override.example.yml
+    # to docker-compose.override.yml and set your host's docker GID.
     volumes:
       - /var/run/docker.sock:/var/run/docker.sock:ro # For local container discovery
       - crowdsec_data:/app/data/crowdsec

.docker/compose/docker-compose.e2e.cerberus-disabled.override.yml

@@ -0,0 +1,4 @@
+services:
+  charon-e2e:
+    environment:
+      - CHARON_SECURITY_CERBERUS_ENABLED=false

.docker/compose/docker-compose.e2e.yml

@@ -1,46 +0,0 @@
-# Docker Compose for E2E Testing
-#
-# This configuration runs Charon with a fresh, isolated database specifically for
-# Playwright E2E tests. Use this to ensure tests start with a clean state.
-#
-# Usage:
-#   docker compose -f .docker/compose/docker-compose.e2e.yml up -d
-#
-# The setup API will be available since no users exist in the fresh database.
-# The auth.setup.ts fixture will create a test admin user automatically.
-
-services:
-  charon-e2e:
-    image: charon:local
-    container_name: charon-e2e
-    restart: "no"
-    ports:
-      - "8080:8080"    # Management UI (Charon)
-    environment:
-      - CHARON_ENV=development
-      - CHARON_DEBUG=1
-      - TZ=UTC
-      # E2E testing encryption key - 32 bytes base64 encoded (not for production!)
-      # Generated with: openssl rand -base64 32
-      - CHARON_ENCRYPTION_KEY=ucDWy5ScLubd3QwCHhQa2SY7wL2OF48p/c9nZhyW1mA=
-      - CHARON_HTTP_PORT=8080
-      - CHARON_DB_PATH=/app/data/charon.db
-      - CHARON_FRONTEND_DIR=/app/frontend/dist
-      - CHARON_CADDY_ADMIN_API=http://localhost:2019
-      - CHARON_CADDY_CONFIG_DIR=/app/data/caddy
-      - CHARON_CADDY_BINARY=caddy
-      - CHARON_ACME_STAGING=true
-      - FEATURE_CERBERUS_ENABLED=false
-    volumes:
-      # Use tmpfs for E2E test data - fresh on every run
-      - e2e_data:/app/data
-    healthcheck:
-      test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:8080/api/v1/health"]
-      interval: 5s
-      timeout: 5s
-      retries: 10
-      start_period: 10s
-
-volumes:
-  e2e_data:
-    driver: local

.docker/compose/docker-compose.local.yml

@@ -25,6 +25,10 @@ services:
       - CHARON_IMPORT_DIR=/app/data/imports
       - CHARON_ACME_STAGING=false
       - FEATURE_CERBERUS_ENABLED=true
+      # Emergency "break-glass" token for security reset when ACL blocks access
+      - CHARON_EMERGENCY_TOKEN=03e4682c1164f0c1cb8e17c99bd1a2d9156b59824dde41af3bb67c513e5c5e92
+    # Docker socket group access: copy docker-compose.override.example.yml
+    # to docker-compose.override.yml and set your host's docker GID.
     extra_hosts:
       - "host.docker.internal:host-gateway"
     cap_add:
@@ -43,7 +47,7 @@ services:
 #      - <PATH_TO_YOUR_CADDYFILE>:/import/Caddyfile:ro
 #      - <PATH_TO_YOUR_SITES_DIR>:/import/sites:ro # If your Caddyfile imports other files
     healthcheck:
-      test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:8080/api/v1/health"]
+      test: ["CMD-SHELL", "wget -qO /dev/null http://localhost:8080/api/v1/health || exit 1"]
       interval: 30s
       timeout: 10s
       retries: 3

.docker/compose/docker-compose.override.example.yml

@@ -0,0 +1,26 @@
+# Docker Compose override — copy to docker-compose.override.yml to activate.
+#
+# Use case: grant the container access to the host Docker socket so that
+# Charon can discover running containers.
+#
+# 1. cp docker-compose.override.example.yml docker-compose.override.yml
+# 2. Uncomment the service that matches your compose file:
+#      - "charon" for docker-compose.local.yml
+#      - "app"    for docker-compose.dev.yml
+# 3. Replace <GID> with the output of:  stat -c '%g' /var/run/docker.sock
+# 4. docker compose up -d
+
+services:
+  # Uncomment for docker-compose.local.yml
+  charon:
+    group_add:
+      - "<GID>"   # e.g. "988" — run: stat -c '%g' /var/run/docker.sock
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock:ro
+
+  # Uncomment for docker-compose.dev.yml
+  app:
+    group_add:
+      - "<GID>"   # e.g. "988" — run: stat -c '%g' /var/run/docker.sock
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock:ro

.docker/compose/docker-compose.playwright-ci.yml

@@ -0,0 +1,160 @@
+# Playwright E2E Test Environment for CI/CD
+# ==========================================
+# This configuration is specifically designed for GitHub Actions CI/CD pipelines.
+# Environment variables are provided via GitHub Secrets and generated dynamically.
+#
+# DO NOT USE env_file - CI provides variables via $GITHUB_ENV:
+#   - CHARON_ENCRYPTION_KEY: Generated with openssl rand -base64 32 (ephemeral)
+#   - CHARON_EMERGENCY_TOKEN: From repository secrets (secure)
+#
+# Usage in CI:
+#   export CHARON_ENCRYPTION_KEY=$(openssl rand -base64 32)
+#   export CHARON_EMERGENCY_TOKEN="${{ secrets.CHARON_EMERGENCY_TOKEN }}"
+#   docker compose -f .docker/compose/docker-compose.playwright-ci.yml up -d
+#
+# Profiles:
+#   # Start with security testing services (CrowdSec)
+#   docker compose -f .docker/compose/docker-compose.playwright-ci.yml --profile security-tests up -d
+#
+#   # Start with notification testing services (MailHog)
+#   docker compose -f .docker/compose/docker-compose.playwright-ci.yml --profile notification-tests up -d
+#
+# The setup API will be available since no users exist in the fresh database.
+# The auth.setup.ts fixture will create a test admin user automatically.
+
+services:
+  # =============================================================================
+  # Charon Application - Core E2E Testing Service
+  # =============================================================================
+  charon-app:
+    # CI provides CHARON_E2E_IMAGE_TAG=charon:e2e-test (retagged from shared digest)
+    # Local development uses the default fallback value
+    image: ${CHARON_E2E_IMAGE_TAG:-charon:e2e-test}
+    container_name: charon-playwright
+    restart: "no"
+    # CI generates CHARON_ENCRYPTION_KEY dynamically in GitHub Actions workflow
+    # and passes CHARON_EMERGENCY_TOKEN from GitHub Secrets via $GITHUB_ENV.
+    # No .env file is used in CI as it's gitignored and not available.
+    ports:
+      - "8080:8080"            # Management UI (Charon)
+      - "127.0.0.1:2019:2019" # Caddy admin API (IPv4 loopback)
+      - "[::1]:2019:2019"     # Caddy admin API (IPv6 loopback)
+      - "2020:2020"           # Emergency tier-2 API (all interfaces for E2E tests)
+      - "80:80"               # Caddy proxy (all interfaces for E2E tests)
+      - "443:443"             # Caddy proxy HTTPS (all interfaces for E2E tests)
+    environment:
+      # Core configuration
+      - CHARON_ENV=test
+      - CHARON_DEBUG=0
+      - TZ=UTC
+      # E2E testing encryption key - 32 bytes base64 encoded (not for production!)
+      # Encryption key - MUST be provided via environment variable
+      # Generate with: export CHARON_ENCRYPTION_KEY=$(openssl rand -base64 32)
+      - CHARON_ENCRYPTION_KEY=${CHARON_ENCRYPTION_KEY:?CHARON_ENCRYPTION_KEY is required}
+      # Emergency reset token - for break-glass recovery when locked out by ACL
+      # Generate with: openssl rand -hex 32
+      - CHARON_EMERGENCY_TOKEN=${CHARON_EMERGENCY_TOKEN:-test-emergency-token-for-e2e-32chars}
+      - CHARON_EMERGENCY_SERVER_ENABLED=true
+      - CHARON_SECURITY_TESTS_ENABLED=${CHARON_SECURITY_TESTS_ENABLED:-true}
+      # Emergency server must bind to 0.0.0.0 for Docker port mapping to work
+      # Host binding via compose restricts external access (127.0.0.1:2020:2020)
+      - CHARON_EMERGENCY_BIND=0.0.0.0:2020
+      # Emergency server Basic Auth (required for E2E tests)
+      - CHARON_EMERGENCY_USERNAME=admin
+      - CHARON_EMERGENCY_PASSWORD=changeme
+      # Server settings
+      - CHARON_HTTP_PORT=8080
+      - CHARON_DB_PATH=/app/data/charon.db
+      - CHARON_FRONTEND_DIR=/app/frontend/dist
+      # Caddy settings
+      - CHARON_CADDY_ADMIN_API=http://localhost:2019
+      - CHARON_CADDY_CONFIG_DIR=/app/data/caddy
+      - CHARON_CADDY_BINARY=caddy
+      # ACME settings (staging for E2E tests)
+      - CHARON_ACME_STAGING=true
+      # Security features - disabled by default for faster tests
+      # Enable via profile: --profile security-tests
+      # FEATURE_CERBERUS_ENABLED deprecated - Cerberus enabled by default
+      - CHARON_SECURITY_CROWDSEC_MODE=disabled
+      # SMTP for notification tests (connects to MailHog when profile enabled)
+      - CHARON_SMTP_HOST=mailhog
+      - CHARON_SMTP_PORT=1025
+      - CHARON_SMTP_AUTH=false
+    volumes:
+      # Named volume for test data persistence during test runs
+      - playwright_data:/app/data
+      - playwright_caddy_data:/data
+      - playwright_caddy_config:/config
+      - /var/run/docker.sock:/var/run/docker.sock:ro # For container discovery in tests
+    healthcheck:
+      test: ["CMD-SHELL", "wget -qO /dev/null http://localhost:8080/api/v1/health || exit 1"]
+      interval: 5s
+      timeout: 3s
+      retries: 12
+      start_period: 10s
+    networks:
+      - playwright-network
+
+  # =============================================================================
+  # CrowdSec - Security Testing Service (Optional Profile)
+  # =============================================================================
+  crowdsec:
+    image: crowdsecurity/crowdsec:latest@sha256:63b595fef92de1778573b375897a45dd226637ee9a3d3db9f57ac7355c369493
+    container_name: charon-playwright-crowdsec
+    profiles:
+      - security-tests
+    restart: "no"
+    environment:
+      - COLLECTIONS=crowdsecurity/nginx crowdsecurity/http-cve
+      - BOUNCER_KEY_charon=test-bouncer-key-for-e2e
+      # Disable online features for isolated testing
+      - DISABLE_ONLINE_API=true
+    volumes:
+      - playwright_crowdsec_data:/var/lib/crowdsec/data
+      - playwright_crowdsec_config:/etc/crowdsec
+      - /var/run/docker.sock:/var/run/docker.sock:ro # For container discovery in tests
+    healthcheck:
+      test: ["CMD", "cscli", "version"]
+      interval: 10s
+      timeout: 5s
+      retries: 5
+      start_period: 30s
+    networks:
+      - playwright-network
+
+  # =============================================================================
+  # MailHog - Email Testing Service (Optional Profile)
+  # =============================================================================
+  mailhog:
+    image: mailhog/mailhog:latest@sha256:8d76a3d4ffa32a3661311944007a415332c4bb855657f4f6c57996405c009bea
+    container_name: charon-playwright-mailhog
+    profiles:
+      - notification-tests
+    restart: "no"
+    ports:
+      - "1025:1025"    # SMTP server
+      - "8025:8025"    # Web UI for viewing emails
+    networks:
+      - playwright-network
+
+# =============================================================================
+# Named Volumes
+# =============================================================================
+volumes:
+  playwright_data:
+    driver: local
+  playwright_caddy_data:
+    driver: local
+  playwright_caddy_config:
+    driver: local
+  playwright_crowdsec_data:
+    driver: local
+  playwright_crowdsec_config:
+    driver: local
+
+# =============================================================================
+# Networks
+# =============================================================================
+networks:
+  playwright-network:
+    driver: bridge

.docker/compose/docker-compose.playwright-local.yml

@@ -0,0 +1,60 @@
+# Docker Compose for Local E2E Testing
+#
+# This configuration runs Charon with a fresh, isolated database specifically for
+# Playwright E2E tests during local development. Uses .env file for credentials.
+#
+# Usage:
+#   docker compose -f .docker/compose/docker-compose.playwright-local.yml up -d
+#
+# Prerequisites:
+#   - Create .env file in project root with CHARON_ENCRYPTION_KEY and CHARON_EMERGENCY_TOKEN
+#   - Build image: docker build -t charon:local .
+#
+# The setup API will be available since no users exist in the fresh database.
+# The auth.setup.ts fixture will create a test admin user automatically.
+
+services:
+  charon-e2e:
+    image: charon:local
+    container_name: charon-e2e
+    restart: "no"
+    env_file:
+      - ../../.env
+    ports:
+      - "8080:8080"             # Management UI (Charon) - E2E tests verify UI/UX here
+      - "127.0.0.1:2019:2019"  # Caddy admin API (read-only status; keep loopback only)
+      - "[::1]:2019:2019"      # Caddy admin API (IPv6 loopback)
+      - "2020:2020"            # Emergency tier-2 API (all interfaces for E2E tests)
+      # Port 80/443: NOT exposed - middleware testing done via integration tests
+    environment:
+      - CHARON_ENV=e2e  # Enable lenient rate limiting (50 attempts/min) for E2E tests
+      - CHARON_DEBUG=0
+      - TZ=UTC
+      # Encryption key and emergency token loaded from env_file (../../.env)
+      # DO NOT add them here - env_file takes precedence and explicit entries override with empty values
+      # Emergency server (Tier 2 break glass) - separate port bypassing all security
+      - CHARON_EMERGENCY_SERVER_ENABLED=true
+      - CHARON_EMERGENCY_BIND=0.0.0.0:2020  # Bind to all interfaces in container (avoid Caddy's 2019)
+      - CHARON_EMERGENCY_USERNAME=admin
+      - CHARON_EMERGENCY_PASSWORD=${CHARON_EMERGENCY_PASSWORD:-changeme}
+      - CHARON_HTTP_PORT=8080
+      - CHARON_DB_PATH=/app/data/charon.db
+      - CHARON_FRONTEND_DIR=/app/frontend/dist
+      - CHARON_CADDY_ADMIN_API=http://localhost:2019
+      - CHARON_CADDY_CONFIG_DIR=/app/data/caddy
+      - CHARON_CADDY_BINARY=caddy
+      - CHARON_ACME_STAGING=true
+      # FEATURE_CERBERUS_ENABLED deprecated - Cerberus enabled by default
+    tmpfs:
+      # True tmpfs for E2E test data - fresh on every run, in-memory only
+      # mode=1777 allows any user to write (container runs as non-root)
+      # 256M gives headroom for the backup service's 100MB disk-space check
+      - /app/data:size=256M,mode=1777
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock:ro # For container discovery in tests
+    healthcheck:
+      test: ["CMD-SHELL", "wget -qO /dev/null http://localhost:8080/api/v1/health || exit 1"]
+      interval: 5s
+      timeout: 5s
+      retries: 10
+      start_period: 10s

.docker/compose/docker-compose.remote.yml

@@ -4,7 +4,7 @@ services:
   # Run this service on your REMOTE servers (not the one running Charon)
   # to allow Charon to discover containers running there (legacy: CPMP).
   docker-socket-proxy:
-    image: alpine/socat
+    image: alpine/socat:latest
     container_name: docker-socket-proxy
     restart: unless-stopped
     ports:

.docker/compose/docker-compose.yml

@@ -1,6 +1,8 @@
 services:
   charon:
-    image: ghcr.io/wikid82/charon:latest
+    # Override for local testing:
+    # CHARON_IMAGE=ghcr.io/wikid82/charon:latest
+    image: wikid82/charon:latest
     container_name: charon
     restart: unless-stopped
     ports:
@@ -8,11 +10,23 @@ services:
       - "443:443"      # HTTPS (Caddy proxy)
       - "443:443/udp"  # HTTP/3 (Caddy proxy)
       - "8080:8080"    # Management UI (Charon)
+      # Emergency server port - ONLY expose via SSH tunnel or VPN for security
+      # Uncomment ONLY if you need localhost access on host machine:
+      # - "127.0.0.1:2020:2020"  # Emergency server Tier-2 (localhost-only, avoids Caddy's 2019)
     environment:
       - CHARON_ENV=production # CHARON_ preferred; CPM_ values still supported
       - TZ=UTC # Set timezone (e.g., America/New_York)
       # Generate with: openssl rand -base64 32
       - CHARON_ENCRYPTION_KEY=your-32-byte-base64-key-here
+      # Emergency break glass configuration (Tier 1 & Tier 2)
+      # Tier 1: Emergency token for Layer 7 bypass within application
+      # Generate with: openssl rand -hex 32
+      # - CHARON_EMERGENCY_TOKEN=${CHARON_EMERGENCY_TOKEN}  # Store in secrets manager
+      # Tier 2: Emergency server on separate port (bypasses Caddy/CrowdSec entirely)
+      # - CHARON_EMERGENCY_SERVER_ENABLED=false  # Disabled by default
+      # - CHARON_EMERGENCY_BIND=127.0.0.1:2020   # Localhost only (port 2020 avoids Caddy admin API)
+      # - CHARON_EMERGENCY_USERNAME=admin
+      # - CHARON_EMERGENCY_PASSWORD=${EMERGENCY_PASSWORD}  # Store in secrets manager
       - CHARON_HTTP_PORT=8080
       - CHARON_DB_PATH=/app/data/charon.db
       - CHARON_FRONTEND_DIR=/app/frontend/dist
@@ -21,25 +35,10 @@ services:
       - CHARON_CADDY_BINARY=caddy
       - CHARON_IMPORT_CADDYFILE=/import/Caddyfile
       - CHARON_IMPORT_DIR=/app/data/imports
-      # Security Services (Optional)
-      # 🚨 DEPRECATED: CrowdSec environment variables are no longer used.
-      # CrowdSec is now GUI-controlled via the Security dashboard.
-      # Remove these lines and use the GUI toggle instead.
-      # See: https://wikid82.github.io/charon/migration-guide
-      #- CERBERUS_SECURITY_CROWDSEC_MODE=disabled # ⚠️ DEPRECATED - Use GUI toggle
-      #- CERBERUS_SECURITY_CROWDSEC_API_URL= # ⚠️ DEPRECATED - External mode removed
-      #- CERBERUS_SECURITY_CROWDSEC_API_KEY= # ⚠️ DEPRECATED - External mode removed
-      #- CERBERUS_SECURITY_WAF_MODE=disabled # disabled, enabled
-      #- CERBERUS_SECURITY_RATELIMIT_ENABLED=false
-      #- CERBERUS_SECURITY_ACL_ENABLED=false
-      # Backward compatibility: CPM_ prefixed variables are still supported
-      # 🚨 DEPRECATED: Use GUI toggle instead (see Security dashboard)
-      #- CPM_SECURITY_CROWDSEC_MODE=disabled # ⚠️ DEPRECATED
-      #- CPM_SECURITY_CROWDSEC_API_URL= # ⚠️ DEPRECATED
-      #- CPM_SECURITY_CROWDSEC_API_KEY= # ⚠️ DEPRECATED
-      #- CPM_SECURITY_WAF_MODE=disabled
-      #- CPM_SECURITY_RATELIMIT_ENABLED=false
-      #- CPM_SECURITY_ACL_ENABLED=false
+      # Paste your CrowdSec API details here to prevent auto reregistration on startup
+      # Obtained from your CrowdSec settings on first setup
+      - CHARON_SECURITY_CROWDSEC_API_URL=http://localhost:8085
+      - CHARON_SECURITY_CROWDSEC_API_KEY=<your-crowdsec-api-key-here>
     extra_hosts:
       - "host.docker.internal:host-gateway"
     volumes:
@@ -53,7 +52,7 @@ services:
       # - ./my-existing-Caddyfile:/import/Caddyfile:ro
       # - ./sites:/import/sites:ro # If your Caddyfile imports other files
     healthcheck:
-      test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:8080/api/v1/health"]
+      test: ["CMD-SHELL", "wget -qO /dev/null http://localhost:8080/api/v1/health || exit 1"]
       interval: 30s
       timeout: 10s
       retries: 3

.docker/docker-entrypoint.sh

@@ -12,12 +12,42 @@ is_root() {
 
 run_as_charon() {
     if is_root; then
-        su-exec charon "$@"
+        gosu charon "$@"
     else
         "$@"
     fi
 }
 
+get_group_by_gid() {
+    if command -v getent >/dev/null 2>&1; then
+        getent group "$1" 2>/dev/null || true
+    else
+        awk -F: -v gid="$1" '$3==gid {print $0}' /etc/group 2>/dev/null || true
+    fi
+}
+
+create_group_with_gid() {
+    if command -v addgroup >/dev/null 2>&1; then
+        addgroup -g "$1" "$2" 2>/dev/null || true
+        return
+    fi
+
+    if command -v groupadd >/dev/null 2>&1; then
+        groupadd -g "$1" "$2" 2>/dev/null || true
+    fi
+}
+
+add_user_to_group() {
+    if command -v addgroup >/dev/null 2>&1; then
+        addgroup "$1" "$2" 2>/dev/null || true
+        return
+    fi
+
+    if command -v usermod >/dev/null 2>&1; then
+        usermod -aG "$2" "$1" 2>/dev/null || true
+    fi
+}
+
 # ============================================================================
 # Volume Permission Handling for Non-Root User
 # ============================================================================
@@ -42,6 +72,13 @@ mkdir -p /app/data/caddy 2>/dev/null || true
 mkdir -p /app/data/crowdsec 2>/dev/null || true
 mkdir -p /app/data/geoip 2>/dev/null || true
 
+# Fix ownership for directories created as root
+if is_root; then
+    chown -R charon:charon /app/data/caddy 2>/dev/null || true
+    chown -R charon:charon /app/data/crowdsec 2>/dev/null || true
+    chown -R charon:charon /app/data/geoip 2>/dev/null || true
+fi
+
 # ============================================================================
 # Plugin Directory Permission Verification
 # ============================================================================
@@ -51,14 +88,16 @@ mkdir -p /app/data/geoip 2>/dev/null || true
 PLUGINS_DIR="${CHARON_PLUGINS_DIR:-/app/plugins}"
 if [ -d "$PLUGINS_DIR" ]; then
     # Check if directory is world-writable (security risk)
-    if [ "$(stat -c '%a' "$PLUGINS_DIR" 2>/dev/null | grep -c '.[0-9][2367]$')" -gt 0 ]; then
+    # Using find -perm -0002 is more robust than stat regex - handles sticky/setgid bits correctly
+    if find "$PLUGINS_DIR" -maxdepth 0 -perm -0002 -print -quit 2>/dev/null | grep -q .; then
         echo "⚠️  WARNING: Plugin directory $PLUGINS_DIR is world-writable!"
         echo "   This is a security risk - plugins could be injected by any user."
-        echo "   Attempting to fix permissions..."
-        if chmod 755 "$PLUGINS_DIR" 2>/dev/null; then
-            echo "   ✓ Fixed: Plugin directory permissions set to 755"
+        echo "   Attempting to fix permissions (removing world-writable bit)..."
+        # Use chmod o-w to only remove world-writable, preserving sticky/setgid bits
+        if chmod o-w "$PLUGINS_DIR" 2>/dev/null; then
+            echo "   ✓ Fixed: Plugin directory world-writable permission removed"
         else
-            echo "   ✗ ERROR: Cannot fix permissions. Please run: chmod 755 $PLUGINS_DIR"
+            echo "   ✗ ERROR: Cannot fix permissions. Please run: chmod o-w $PLUGINS_DIR"
             echo "   Plugin loading may fail due to insecure permissions."
         fi
     else
@@ -80,24 +119,32 @@ if [ -S "/var/run/docker.sock" ] && is_root; then
     DOCKER_SOCK_GID=$(stat -c '%g' /var/run/docker.sock 2>/dev/null || echo "")
     if [ -n "$DOCKER_SOCK_GID" ] && [ "$DOCKER_SOCK_GID" != "0" ]; then
         # Check if a group with this GID exists
-        if ! getent group "$DOCKER_SOCK_GID" >/dev/null 2>&1; then
+        GROUP_ENTRY=$(get_group_by_gid "$DOCKER_SOCK_GID")
+        if [ -z "$GROUP_ENTRY" ]; then
             echo "Docker socket detected (gid=$DOCKER_SOCK_GID) - creating docker group and adding charon user..."
             # Create docker group with the socket's GID
-            addgroup -g "$DOCKER_SOCK_GID" docker 2>/dev/null || true
+            create_group_with_gid "$DOCKER_SOCK_GID" docker
             # Add charon user to the docker group
-            addgroup charon docker 2>/dev/null || true
+            add_user_to_group charon docker
             echo "Docker integration enabled for charon user"
         else
             # Group exists, just add charon to it
-            GROUP_NAME=$(getent group "$DOCKER_SOCK_GID" | cut -d: -f1)
+            GROUP_NAME=$(echo "$GROUP_ENTRY" | cut -d: -f1)
             echo "Docker socket detected (gid=$DOCKER_SOCK_GID, group=$GROUP_NAME) - adding charon user..."
-            addgroup charon "$GROUP_NAME" 2>/dev/null || true
+            add_user_to_group charon "$GROUP_NAME"
             echo "Docker integration enabled for charon user"
         fi
     fi
 elif [ -S "/var/run/docker.sock" ]; then
-    echo "Note: Docker socket mounted but container is running non-root; skipping docker.sock group setup."
-    echo "      If Docker discovery is needed, run with matching group permissions (e.g., --group-add)"
+    DOCKER_SOCK_GID=$(stat -c '%g' /var/run/docker.sock 2>/dev/null || echo "unknown")
+    echo "Note: Docker socket mounted (GID=$DOCKER_SOCK_GID) but container is running non-root; skipping docker.sock group setup."
+    echo "      If Docker discovery is needed, add 'group_add: [\"$DOCKER_SOCK_GID\"]' to your compose service."
+    if [ "$DOCKER_SOCK_GID" = "0" ]; then
+        if [ "${ALLOW_DOCKER_SOCK_GID_0:-false}" != "true" ]; then
+            echo "⚠️  WARNING: Docker socket GID is 0 (root group). group_add: [\"0\"] grants root-group access."
+            echo "   Set ALLOW_DOCKER_SOCK_GID_0=true to acknowledge this risk."
+        fi
+    fi
 else
     echo "Note: Docker socket not found. Docker container discovery will be unavailable."
 fi
@@ -121,6 +168,20 @@ if command -v cscli >/dev/null; then
     mkdir -p "$CS_CONFIG_DIR" 2>/dev/null || echo "Warning: Cannot create $CS_CONFIG_DIR"
     mkdir -p "$CS_DATA_DIR" 2>/dev/null || echo "Warning: Cannot create $CS_DATA_DIR"
     mkdir -p "$CS_PERSIST_DIR/hub_cache"
+
+    # ============================================================================
+    # CrowdSec Bouncer Key Persistence Directory
+    # ============================================================================
+    # Create the persistent directory for bouncer key storage.
+    # This directory is inside /app/data which is volume-mounted.
+    # The bouncer key will be stored at /app/data/crowdsec/bouncer_key
+    echo "CrowdSec bouncer key will be stored at: $CS_PERSIST_DIR/bouncer_key"
+
+    # Fix ownership for key directory if running as root
+    if is_root; then
+        chown charon:charon "$CS_PERSIST_DIR" 2>/dev/null || true
+    fi
+
     # Log directories are created at build time with correct ownership
     # Only attempt to create if they don't exist (first run scenarios)
     mkdir -p /var/log/crowdsec 2>/dev/null || true
@@ -129,22 +190,42 @@ if command -v cscli >/dev/null; then
     # Initialize persistent config if key files are missing
     if [ ! -f "$CS_CONFIG_DIR/config.yaml" ]; then
         echo "Initializing persistent CrowdSec configuration..."
-        if [ -d "/etc/crowdsec.dist" ] && [ -n "$(ls -A /etc/crowdsec.dist 2>/dev/null)" ]; then
-            cp -r /etc/crowdsec.dist/* "$CS_CONFIG_DIR/" || {
+
+        # Check if .dist has content
+        if [ -d "/etc/crowdsec.dist" ] && find /etc/crowdsec.dist -mindepth 1 -maxdepth 1 -print -quit 2>/dev/null | grep -q .; then
+            echo "Copying config from /etc/crowdsec.dist..."
+            if ! cp -r /etc/crowdsec.dist/* "$CS_CONFIG_DIR/"; then
                 echo "ERROR: Failed to copy config from /etc/crowdsec.dist"
+                echo "DEBUG: Contents of /etc/crowdsec.dist:"
+                ls -la /etc/crowdsec.dist/
                 exit 1
-            }
-            echo "Successfully initialized config from .dist directory"
-        elif [ -d "/etc/crowdsec" ] && [ ! -L "/etc/crowdsec" ] && [ -n "$(ls -A /etc/crowdsec 2>/dev/null)" ]; then
-            cp -r /etc/crowdsec/* "$CS_CONFIG_DIR/" || {
-                echo "ERROR: Failed to copy config from /etc/crowdsec"
+            fi
+
+            # Verify critical files were copied
+            if [ ! -f "$CS_CONFIG_DIR/config.yaml" ]; then
+                echo "ERROR: config.yaml was not copied to $CS_CONFIG_DIR"
+                echo "DEBUG: Contents of $CS_CONFIG_DIR after copy:"
+                ls -la "$CS_CONFIG_DIR/"
                 exit 1
-            }
-            echo "Successfully initialized config from /etc/crowdsec"
+            fi
+            echo "✓ Successfully initialized config from .dist directory"
+        elif [ -d "/etc/crowdsec" ] && [ ! -L "/etc/crowdsec" ] && find /etc/crowdsec -mindepth 1 -maxdepth 1 -print -quit 2>/dev/null | grep -q .; then
+            echo "Copying config from /etc/crowdsec (fallback)..."
+            if ! cp -r /etc/crowdsec/* "$CS_CONFIG_DIR/"; then
+                echo "ERROR: Failed to copy config from /etc/crowdsec (fallback)"
+                exit 1
+            fi
+            echo "✓ Successfully initialized config from /etc/crowdsec"
         else
-            echo "ERROR: No config source found (neither .dist nor /etc/crowdsec available)"
+            echo "ERROR: No config source found!"
+            echo "DEBUG: /etc/crowdsec.dist contents:"
+            ls -la /etc/crowdsec.dist/ 2>/dev/null || echo "  (directory not found or empty)"
+            echo "DEBUG: /etc/crowdsec contents:"
+            ls -la /etc/crowdsec 2>/dev/null || echo "  (directory not found or empty)"
             exit 1
         fi
+    else
+        echo "✓ Persistent config already exists: $CS_CONFIG_DIR/config.yaml"
     fi
 
     # Verify symlink exists (created at build time)
@@ -152,10 +233,24 @@ if command -v cscli >/dev/null; then
     # Non-root users cannot create symlinks in /etc, so this must be done at build time
     if [ -L "/etc/crowdsec" ]; then
         echo "CrowdSec config symlink verified: /etc/crowdsec -> $CS_CONFIG_DIR"
+
+        # Verify the symlink target is accessible and has config.yaml
+        if [ ! -f "/etc/crowdsec/config.yaml" ]; then
+            echo "ERROR: /etc/crowdsec/config.yaml is not accessible via symlink"
+            echo "DEBUG: Symlink target verification:"
+            ls -la /etc/crowdsec 2>/dev/null || echo "  (symlink broken or missing)"
+            echo "DEBUG: Directory contents:"
+            ls -la "$CS_CONFIG_DIR/" 2>/dev/null | head -10 || echo "  (directory not found)"
+            exit 1
+        fi
+        echo "✓ /etc/crowdsec/config.yaml is accessible via symlink"
     else
-        echo "WARNING: /etc/crowdsec symlink not found. This may indicate a build issue."
+        echo "ERROR: /etc/crowdsec symlink not found"
         echo "Expected: /etc/crowdsec -> /app/data/crowdsec/config"
-        # Try to continue anyway - config may still work if CrowdSec uses CFG env var
+        echo "This indicates a critical build-time issue. Symlink must be created at build time as root."
+        echo "DEBUG: Directory check:"
+        find /etc -mindepth 1 -maxdepth 1 -name '*crowdsec*' -exec ls -ld {} \; 2>/dev/null || echo "  (no crowdsec entry found)"
+        exit 1
     fi
 
     # Create/update acquisition config for Caddy logs
@@ -208,6 +303,19 @@ ACQUIS_EOF
     # Also handle case where it might be without trailing slash
     sed -i 's|log_dir: /var/log$|log_dir: /var/log/crowdsec|g' "$CS_CONFIG_DIR/config.yaml"
 
+    # Redirect CrowdSec LAPI database to persistent volume
+    # Default path /var/lib/crowdsec/data/crowdsec.db is ephemeral (not volume-mounted),
+    # so it is destroyed on every container rebuild. The bouncer API key (stored on the
+    # persistent volume at /app/data/crowdsec/) survives rebuilds but the LAPI database
+    # that validates it does not — causing perpetual key rejection.
+    # Redirecting db_path to the volume-mounted CS_DATA_DIR fixes this.
+    sed -i "s|db_path: /var/lib/crowdsec/data/crowdsec.db|db_path: ${CS_DATA_DIR}/crowdsec.db|g" "$CS_CONFIG_DIR/config.yaml"
+    if grep -q "db_path:.*${CS_DATA_DIR}" "$CS_CONFIG_DIR/config.yaml"; then
+        echo "✓ CrowdSec LAPI database redirected to persistent volume: ${CS_DATA_DIR}/crowdsec.db"
+    else
+        echo "⚠️  WARNING: Could not verify LAPI db_path redirect — bouncer keys may not survive rebuilds"
+    fi
+
     # Verify LAPI configuration was applied correctly
     if grep -q "listen_uri:.*:8085" "$CS_CONFIG_DIR/config.yaml"; then
         echo "✓ CrowdSec LAPI configured for port 8085"
@@ -215,10 +323,11 @@ ACQUIS_EOF
         echo "✗ WARNING: LAPI port configuration may be incorrect"
     fi
 
-    # Update hub index to ensure CrowdSec can start
-    if [ ! -f "/etc/crowdsec/hub/.index.json" ]; then
-        echo "Updating CrowdSec hub index..."
-        timeout 60s cscli hub update 2>/dev/null || echo "⚠️ Hub update timed out or failed, continuing..."
+    # Always refresh hub index on startup (stale index causes hash mismatch errors on collection install)
+    echo "Updating CrowdSec hub index..."
+    if ! timeout 60s cscli hub update 2>&1; then
+        echo "⚠️ Hub index update failed (network issue?). Collections may fail to install."
+        echo "   CrowdSec will still start with whatever index is cached."
     fi
 
     # Ensure local machine is registered (auto-heal for volume/config mismatch)
@@ -226,12 +335,11 @@ ACQUIS_EOF
     echo "Registering local machine..."
     cscli machines add -a --force 2>/dev/null || echo "Warning: Machine registration may have failed"
 
-    # Install hub items (parsers, scenarios, collections) if local mode enabled
-    if [ "$SECURITY_CROWDSEC_MODE" = "local" ]; then
-        echo "Installing CrowdSec hub items..."
-        if [ -x /usr/local/bin/install_hub_items.sh ]; then
-            /usr/local/bin/install_hub_items.sh 2>/dev/null || echo "Warning: Some hub items may not have installed"
-        fi
+    # Always ensure required collections are present (idempotent — already-installed items are skipped).
+    # Collections are just config files with zero runtime cost when CrowdSec is disabled.
+    echo "Ensuring CrowdSec hub items are installed..."
+    if [ -x /usr/local/bin/install_hub_items.sh ]; then
+        /usr/local/bin/install_hub_items.sh || echo "⚠️ Some hub items may not have installed. CrowdSec can still start."
     fi
 
     # Fix ownership AFTER cscli commands (they run as root and create root-owned files)
@@ -270,7 +378,7 @@ echo "Caddy started (PID: $CADDY_PID)"
 echo "Waiting for Caddy admin API..."
 i=1
 while [ "$i" -le 30 ]; do
-    if wget -q -O- http://127.0.0.1:2019/config/ > /dev/null 2>&1; then
+    if wget -qO /dev/null http://127.0.0.1:2019/config/ 2>/dev/null; then
         echo "Caddy is ready!"
         break
     fi
@@ -281,22 +389,37 @@ done
 # Start Charon management application
 # Drop privileges to charon user before starting the application
 # This maintains security while allowing Docker socket access via group membership
-# Note: When running as root, we use su-exec; otherwise we run directly.
+# Note: When running as root, we use gosu; otherwise we run directly.
 echo "Starting Charon management application..."
 DEBUG_FLAG=${CHARON_DEBUG:-$CPMP_DEBUG}
-DEBUG_PORT=${CHARON_DEBUG_PORT:-$CPMP_DEBUG_PORT}
+DEBUG_PORT=${CHARON_DEBUG_PORT:-${CPMP_DEBUG_PORT:-2345}}
+
+# Determine binary path
+bin_path=/app/charon
+if [ ! -f "$bin_path" ]; then
+    bin_path=/app/cpmp
+fi
+
 if [ "$DEBUG_FLAG" = "1" ]; then
-    echo "Running Charon under Delve (port $DEBUG_PORT)"
-    bin_path=/app/charon
-    if [ ! -f "$bin_path" ]; then
-        bin_path=/app/cpmp
+    # Check if binary has debug symbols (required for Delve)
+    # objdump -h lists section headers; .debug_info is present if DWARF symbols exist
+    if command -v objdump >/dev/null 2>&1; then
+        if ! objdump -h "$bin_path" 2>/dev/null | grep -q '\.debug_info'; then
+            echo "⚠️  WARNING: Binary lacks debug symbols (DWARF info stripped)."
+            echo "   Delve debugging will NOT work with this binary."
+            echo "   To fix, rebuild with: docker build --build-arg BUILD_DEBUG=1 ..."
+            echo "   Falling back to normal execution (without debugger)."
+            run_as_charon "$bin_path" &
+        else
+            echo "✓ Debug symbols detected. Running Charon under Delve (port $DEBUG_PORT)"
+            run_as_charon /usr/local/bin/dlv exec "$bin_path" --headless --listen=":$DEBUG_PORT" --api-version=2 --accept-multiclient --continue --log -- &
+        fi
+    else
+        # objdump not available, try to run Delve anyway with a warning
+        echo "Note: Cannot verify debug symbols (objdump not found). Attempting Delve..."
+        run_as_charon /usr/local/bin/dlv exec "$bin_path" --headless --listen=":$DEBUG_PORT" --api-version=2 --accept-multiclient --continue --log -- &
     fi
-    run_as_charon /usr/local/bin/dlv exec "$bin_path" --headless --listen=":$DEBUG_PORT" --api-version=2 --accept-multiclient --continue --log -- &
 else
-    bin_path=/app/charon
-    if [ ! -f "$bin_path" ]; then
-        bin_path=/app/cpmp
-    fi
     run_as_charon "$bin_path" &
 fi
 APP_PID=$!

.dockerignore

@@ -9,13 +9,12 @@
 .git/
 .gitignore
 .github/
-.pre-commit-config.yaml
-.codecov.yml
+codecov.yml
 .goreleaser.yaml
 .sourcery.yml
 
 # -----------------------------------------------------------------------------
-# Python (pre-commit, tooling)
+# Python (tooling)
 # -----------------------------------------------------------------------------
 __pycache__/
 *.py[cod]
@@ -57,9 +56,11 @@ package.json
 # -----------------------------------------------------------------------------
 backend/bin/
 backend/api
+backend/main
 backend/*.out
 backend/*.cover
 backend/*.html
+backend/*.test
 backend/coverage/
 backend/coverage*.out
 backend/coverage*.txt
@@ -68,11 +69,16 @@ backend/handler_coverage.txt
 backend/handlers.out
 backend/services.test
 backend/test-output.txt
+backend/test-output*.txt
+backend/test_output*.txt
 backend/tr_no_cover.txt
 backend/nohup.out
 backend/package.json
 backend/package-lock.json
+backend/node_modules/
 backend/internal/api/tests/data/
+backend/lint*.txt
+backend/fix_*.sh
 
 # Backend data (created at runtime)
 backend/data/
@@ -177,8 +183,6 @@ codeql-db/
 codeql-db-*/
 codeql-agent-results/
 codeql-custom-queries-*/
-codeql-*.sarif
-codeql-results*.sarif
 .codeql/
 
 # -----------------------------------------------------------------------------
@@ -186,21 +190,50 @@ codeql-results*.sarif
 # -----------------------------------------------------------------------------
 import/
 
+# -----------------------------------------------------------------------------
+# Playwright & E2E Testing
+# -----------------------------------------------------------------------------
+playwright/
+playwright-report/
+blob-report/
+test-results/
+tests/
+test-data/
+playwright.config.js
+
+# -----------------------------------------------------------------------------
+# Root-level artifacts
+# -----------------------------------------------------------------------------
+coverage.txt
+provenance*.json
+trivy-*.txt
+grype-results*.json
+grype-results*.sarif
+my-codeql-db/
+
 # -----------------------------------------------------------------------------
 # Project Documentation & Planning (not needed in image)
 # -----------------------------------------------------------------------------
 *.md.bak
 ACME_STAGING_IMPLEMENTATION.md*
 ARCHITECTURE_PLAN.md
+AUTO_VERSIONING_CI_FIX_SUMMARY.md
 BULK_ACL_FEATURE.md
+CODEQL_EMAIL_INJECTION_REMEDIATION_COMPLETE.md
+COMMIT_MSG.txt
+COVERAGE_ANALYSIS.md
+COVERAGE_REPORT.md
 DOCKER_TASKS.md*
 DOCUMENTATION_POLISH_SUMMARY.md
 GHCR_MIGRATION_SUMMARY.md
 ISSUE_*_IMPLEMENTATION.md*
+ISSUE_*.md
+PATCH_COVERAGE_IMPLEMENTATION_SUMMARY.md
 PHASE_*_SUMMARY.md
 PROJECT_BOARD_SETUP.md
 PROJECT_PLANNING.md
 SECURITY_IMPLEMENTATION_PLAN.md
+SECURITY_REMEDIATION_COMPLETE.md
 VERSIONING_IMPLEMENTATION.md
 QA_AUDIT_REPORT*.md
 VERSION.md

.env.example

@@ -0,0 +1,52 @@
+# Charon Environment Configuration Example
+# =========================================
+# Copy this file to .env and configure with your values.
+# Never commit your actual .env file to version control.
+
+# =============================================================================
+# Required Configuration
+# =============================================================================
+
+# Database encryption key - 32 bytes base64 encoded
+# Generate with: openssl rand -base64 32
+CHARON_ENCRYPTION_KEY=
+
+# =============================================================================
+# Emergency Reset Token (Break-Glass Recovery)
+# =============================================================================
+
+# Emergency reset token - REQUIRED for E2E tests (64 characters minimum)
+# Used for break-glass recovery when locked out by ACL or other security modules.
+# This token allows bypassing all security mechanisms to regain access.
+#
+# SECURITY WARNING: Keep this token secure and rotate it periodically (quarterly recommended).
+# Only use this endpoint in genuine emergency situations.
+# Never commit actual token values to the repository.
+#
+# Generate with (Linux/macOS):
+#   openssl rand -hex 32
+#
+# Generate with (Windows PowerShell):
+#   [Convert]::ToBase64String([System.Security.Cryptography.RandomNumberGenerator]::GetBytes(32))
+#
+# Generate with (Node.js - all platforms):
+#   node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
+#
+# REQUIRED for E2E tests - add to .env file (gitignored) or CI/CD secrets
+CHARON_EMERGENCY_TOKEN=
+
+# =============================================================================
+# Optional Configuration
+# =============================================================================
+
+# Server port (default: 8080)
+# CHARON_HTTP_PORT=8080
+
+# Database path (default: /app/data/charon.db)
+# CHARON_DB_PATH=/app/data/charon.db
+
+# Enable debug mode (default: 0)
+# CHARON_DEBUG=0
+
+# Use ACME staging environment (default: false)
+# CHARON_ACME_STAGING=false

.gitattributes

@@ -14,3 +14,15 @@ codeql-db-*/** binary
 *.iso filter=lfs diff=lfs merge=lfs -text
 *.exe filter=lfs diff=lfs merge=lfs -text
 *.dll filter=lfs diff=lfs merge=lfs -text
+
+# Avoid expensive diffs for generated artifacts and large scan reports
+# These files are generated by CI/tools and can be large; disable git's diff algorithm to improve UI/server responsiveness
+coverage/** -diff
+backend/**/coverage*.txt -diff
+test-results/** -diff
+playwright/** -diff
+*.sarif -diff
+sbom.cyclonedx.json -diff
+trivy-*.txt -diff
+grype-*.txt -diff
+*.zip -diff

.github/agents/Backend_Dev.agent.md

@@ -1,27 +1,36 @@
-name: Backend Dev
-description: Senior Go Engineer focused on high-performance, secure backend implementation.
-argument-hint: The specific backend task from the Plan (e.g., "Implement ProxyHost CRUD endpoints")
+---
+name: 'Backend Dev'
+description: 'Senior Go Engineer focused on high-performance, secure backend implementation.'
+argument-hint: 'The specific backend task from the Plan (e.g., "Implement ProxyHost CRUD endpoints")'
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
 
-# ADDED 'list_dir' below so Step 1 works
 
-tools: ['search', 'runSubagent', 'read_file', 'write_file', 'run_terminal_command', 'usages', 'changes', 'list_dir']
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
 
 ---
 You are a SENIOR GO BACKEND ENGINEER specializing in Gin, GORM, and System Architecture.
 Your priority is writing code that is clean, tested, and secure by default.
 
 <context>
+
+- **Governance**: When this agent file conflicts with canonical instruction
+    files (`.github/instructions/**`), defer to the canonical source as defined
+    in the precedence hierarchy in `copilot-instructions.md`.
 - **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
 - **Project**: Charon (Self-hosted Reverse Proxy)
 - **Stack**: Go 1.22+, Gin, GORM, SQLite.
 - **Rules**: You MUST follow `.github/copilot-instructions.md` explicitly.
+- **References**: Use `gopls` mcp server for Go code understanding and generation.
 </context>
 
 <workflow>
 
 1.  **Initialize**:
    -   **Read Instructions**: Read `.github/instructions` and `.github/Backend_Dev.agent.md`.
-    -   **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory.
+    -   **Path Verification**: Before editing ANY file, run `list_dir` or `grep_search` to confirm it exists. Do not rely on your memory.
     -   Read `.github/copilot-instructions.md` to load coding standards.
     -   **Context Acquisition**: Scan chat history for "### 🤝 Handoff Contract".
     -   **CRITICAL**: If found, treat that JSON as the **Immutable Truth**. Do not rename fields.
@@ -36,23 +45,33 @@ Your priority is writing code that is clean, tested, and secure by default.
         - Define the structs in `internal/models` to fix compilation errors.
     - **Step 3 (The Logic)**:
         - Implement the handler in `internal/api/handlers`.
-    - **Step 4 (The Green Light)**:
+    - **Step 4 (Lint and Format)**:
+        - Run `lefthook run pre-commit` to ensure code quality.
+    - **Step 5 (The Green Light)**:
         - Run `go test ./...`.
         - **CRITICAL**: If it fails, fix the *Code*, NOT the *Test* (unless the test was wrong about the contract).
 
 3. **Verification (Definition of Done)**:
     - Run `go mod tidy`.
     - Run `go fmt ./...`.
-    - Run `go test ./...` to ensure no regressions.
+        - Run `go test ./...` to ensure no regressions.
+        - **Conditional GORM Gate**: If task changes include model/database-related
+            files (`backend/internal/models/**`, GORM query logic, migrations), run
+            GORM scanner in check mode and treat CRITICAL/HIGH findings as blocking:
+                - Run: `lefthook run pre-commit` (which includes manual gorm-security-scan) OR `./scripts/scan-gorm-security.sh --check`
+                - Policy: Process-blocking gate even while automation is manual stage
+    - **Local Patch Coverage Preflight (MANDATORY)**: Run VS Code task `Test: Local Patch Report` or `bash scripts/local-patch-report.sh` before backend coverage runs.
+        - Ensure artifacts exist: `test-results/local-patch-report.md` and `test-results/local-patch-report.json`.
+        - Use the file-level coverage gap list to target tests before final coverage validation.
     - **Coverage (MANDATORY)**: Run the coverage task/script explicitly and confirm Codecov Patch view is green for modified lines.
         - **MANDATORY**: Patch coverage must cover 100% of new/modified code. This prevents CodeCov Report failing CI.
         - **VS Code Task**: Use "Test: Backend with Coverage" (recommended)
         - **Manual Script**: Execute `/projects/Charon/scripts/go-test-coverage.sh` from the root directory
         - **Minimum**: 85% coverage (configured via `CHARON_MIN_COVERAGE` or `CPM_MIN_COVERAGE`)
         - **Critical**: If coverage drops below threshold, write additional tests immediately. Do not skip this step.
-        - **Why**: Coverage tests are in manual stage of pre-commit for performance. You MUST run them via VS Code tasks or scripts before completing your task.
+        - **Why**: Coverage tests are in manual stage of lefthook for performance. You MUST run them via VS Code tasks or scripts before completing your task.
     - Ensure coverage goals are met as well as all tests pass. Just because Tests pass does not mean you are done. Goal Coverage Needs to be met even if the tests to get us there are outside the scope of your task. At this point, your task is to maintain coverage goal and all tests pass because we cannot commit changes if they fail.
-    - Run `pre-commit run --all-files` as final check (this runs fast hooks only; coverage was verified above).
+    - Run `lefthook run pre-commit` as final check (this runs fast hooks only; coverage was verified above).
 </workflow>
 
 <constraints>
@@ -64,5 +83,5 @@ Your priority is writing code that is clean, tested, and secure by default.
 - **ALWAYS** verify that `json` tags match what the frontend expects.
 - **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results.
 - **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question.
-- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `search_replace` tools if available. If re-writing the file, output ONLY the modified functions/blocks.
+- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `replace_string_in_file` tools if available. If re-writing the file, output ONLY the modified functions/blocks.
 </constraints>

.github/agents/DevOps.agent.md

@@ -1,7 +1,13 @@
 ---
 name: 'DevOps'
 description: 'DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable'
-tools: ['codebase', 'edit/editFiles', 'terminalCommand', 'search', 'githubRepo']
+argument-hint: 'The CI/CD or infrastructure task (e.g., "Debug failing GitHub Action workflow")'
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
+
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
 ---
 
 # GitOps & CI Specialist
@@ -130,6 +136,7 @@ main:
    - Look for error messages
    - Check timing (timeout vs crash)
    - Environment variables set correctly?
+    - If MCP web fetch lacks auth, pull workflow logs with `gh` CLI
 
 3. **Verify environment configuration**
    ```bash

.github/agents/Doc_Writer.agent.md

@@ -1,8 +1,13 @@
-name: Docs Writer
-description: User Advocate and Writer focused on creating simple, layman-friendly documentation.
-argument-hint: The feature to document (e.g., "Write the guide for the new Real-Time Logs")
-tools: ['search', 'read_file', 'write_file', 'list_dir', 'changes']
+---
+name: 'Docs Writer'
+description: 'User Advocate and Writer focused on creating simple, layman-friendly documentation.'
+argument-hint: 'The feature to document (e.g., "Write the guide for the new Real-Time Logs")'
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
 
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
 ---
 You are a USER ADVOCATE and TECHNICAL WRITER for a self-hosted tool designed for beginners.
 Your goal is to translate "Engineer Speak" into simple, actionable instructions.
@@ -48,6 +53,8 @@ Your goal is to translate "Engineer Speak" into simple, actionable instructions.
 
 - **TERSE OUTPUT**: Do not explain your drafting process. Output ONLY the file content or diffs.
 - **NO CONVERSATION**: If the task is done, output "DONE".
-- **USE DIFFS**: When updating `docs/features.md`, use the `changes` tool.
+- **USE DIFFS**: When updating `docs/features.md`, use the `edit/editFiles` tool.
 - **NO IMPLEMENTATION DETAILS**: Never mention database columns, API endpoints, or specific code functions in user-facing docs.
 </constraints>
+
+```

.github/agents/Frontend_Dev.agent.md

@@ -1,805 +1,65 @@
-name: Frontend Dev
-description: Senior React/UX Engineer focused on seamless user experiences and clean component architecture.
-argument-hint: The specific frontend task from the Plan (e.g., "Create Proxy Host Form")
-
-# Expert React Frontend Engineer
-
-You are a world-class expert in React 19.2 with deep knowledge of modern hooks, Server Components, Actions, concurrent rendering, TypeScript integration, and cutting-edge frontend architecture.
-
-## Your Expertise
-
-- **React 19.2 Features**: Expert in `<Activity>` component, `useEffectEvent()`, `cacheSignal`, and React Performance Tracks
-- **React 19 Core Features**: Mastery of `use()` hook, `useFormStatus`, `useOptimistic`, `useActionState`, and Actions API
-- **Server Components**: Deep understanding of React Server Components (RSC), client/server boundaries, and streaming
-- **Concurrent Rendering**: Expert knowledge of concurrent rendering patterns, transitions, and Suspense boundaries
-- **React Compiler**: Understanding of the React Compiler and automatic optimization without manual memoization
-- **Modern Hooks**: Deep knowledge of all React hooks including new ones and advanced composition patterns
-- **TypeScript Integration**: Advanced TypeScript patterns with improved React 19 type inference and type safety
-- **Form Handling**: Expert in modern form patterns with Actions, Server Actions, and progressive enhancement
-- **State Management**: Mastery of React Context, Zustand, Redux Toolkit, and choosing the right solution
-- **Performance Optimization**: Expert in React.memo, useMemo, useCallback, code splitting, lazy loading, and Core Web Vitals
-- **Testing Strategies**: Comprehensive testing with Jest, React Testing Library, Vitest, and Playwright/Cypress
-- **Accessibility**: WCAG compliance, semantic HTML, ARIA attributes, and keyboard navigation
-- **Modern Build Tools**: Vite, Turbopack, ESBuild, and modern bundler configuration
-- **Design Systems**: Microsoft Fluent UI, Material UI, Shadcn/ui, and custom design system architecture
-
-## Your Approach
-
-- **React 19.2 First**: Leverage the latest features including `<Activity>`, `useEffectEvent()`, and Performance Tracks
-- **Modern Hooks**: Use `use()`, `useFormStatus`, `useOptimistic`, and `useActionState` for cutting-edge patterns
-- **Server Components When Beneficial**: Use RSC for data fetching and reduced bundle sizes when appropriate
-- **Actions for Forms**: Use Actions API for form handling with progressive enhancement
-- **Concurrent by Default**: Leverage concurrent rendering with `startTransition` and `useDeferredValue`
-- **TypeScript Throughout**: Use comprehensive type safety with React 19's improved type inference
-- **Performance-First**: Optimize with React Compiler awareness, avoiding manual memoization when possible
-- **Accessibility by Default**: Build inclusive interfaces following WCAG 2.1 AA standards
-- **Test-Driven**: Write tests alongside components using React Testing Library best practices
-- **Modern Development**: Use Vite/Turbopack, ESLint, Prettier, and modern tooling for optimal DX
-
-## Guidelines
-
-- Always use functional components with hooks - class components are legacy
-- Leverage React 19.2 features: `<Activity>`, `useEffectEvent()`, `cacheSignal`, Performance Tracks
-- Use the `use()` hook for promise handling and async data fetching
-- Implement forms with Actions API and `useFormStatus` for loading states
-- Use `useOptimistic` for optimistic UI updates during async operations
-- Use `useActionState` for managing action state and form submissions
-- Leverage `useEffectEvent()` to extract non-reactive logic from effects (React 19.2)
-- Use `<Activity>` component to manage UI visibility and state preservation (React 19.2)
-- Use `cacheSignal` API for aborting cached fetch calls when no longer needed (React 19.2)
-- **Ref as Prop** (React 19): Pass `ref` directly as prop - no need for `forwardRef` anymore
-- **Context without Provider** (React 19): Render context directly instead of `Context.Provider`
-- Implement Server Components for data-heavy components when using frameworks like Next.js
-- Mark Client Components explicitly with `'use client'` directive when needed
-- Use `startTransition` for non-urgent updates to keep the UI responsive
-- Leverage Suspense boundaries for async data fetching and code splitting
-- No need to import React in every file - new JSX transform handles it
-- Use strict TypeScript with proper interface design and discriminated unions
-- Implement proper error boundaries for graceful error handling
-- Use semantic HTML elements (`<button>`, `<nav>`, `<main>`, etc.) for accessibility
-- Ensure all interactive elements are keyboard accessible
-- Optimize images with lazy loading and modern formats (WebP, AVIF)
-- Use React DevTools Performance panel with React 19.2 Performance Tracks
-- Implement code splitting with `React.lazy()` and dynamic imports
-- Use proper dependency arrays in `useEffect`, `useMemo`, and `useCallback`
-- Ref callbacks can now return cleanup functions for easier cleanup management
-
-## Common Scenarios You Excel At
-
-- **Building Modern React Apps**: Setting up projects with Vite, TypeScript, React 19.2, and modern tooling
-- **Implementing New Hooks**: Using `use()`, `useFormStatus`, `useOptimistic`, `useActionState`, `useEffectEvent()`
-- **React 19 Quality-of-Life Features**: Ref as prop, context without provider, ref callback cleanup, document metadata
-- **Form Handling**: Creating forms with Actions, Server Actions, validation, and optimistic updates
-- **Server Components**: Implementing RSC patterns with proper client/server boundaries and `cacheSignal`
-- **State Management**: Choosing and implementing the right state solution (Context, Zustand, Redux Toolkit)
-- **Async Data Fetching**: Using `use()` hook, Suspense, and error boundaries for data loading
-- **Performance Optimization**: Analyzing bundle size, implementing code splitting, optimizing re-renders
-- **Cache Management**: Using `cacheSignal` for resource cleanup and cache lifetime management
-- **Component Visibility**: Implementing `<Activity>` component for state preservation across navigation
-- **Accessibility Implementation**: Building WCAG-compliant interfaces with proper ARIA and keyboard support
-- **Complex UI Patterns**: Implementing modals, dropdowns, tabs, accordions, and data tables
-- **Animation**: Using React Spring, Framer Motion, or CSS transitions for smooth animations
-- **Testing**: Writing comprehensive unit, integration, and e2e tests
-- **TypeScript Patterns**: Advanced typing for hooks, HOCs, render props, and generic components
-
-## Response Style
-
-- Provide complete, working React 19.2 code following modern best practices
-- Include all necessary imports (no React import needed thanks to new JSX transform)
-- Add inline comments explaining React 19 patterns and why specific approaches are used
-- Show proper TypeScript types for all props, state, and return values
-- Demonstrate when to use new hooks like `use()`, `useFormStatus`, `useOptimistic`, `useEffectEvent()`
-- Explain Server vs Client Component boundaries when relevant
-- Show proper error handling with error boundaries
-- Include accessibility attributes (ARIA labels, roles, etc.)
-- Provide testing examples when creating components
-- Highlight performance implications and optimization opportunities
-- Show both basic and production-ready implementations
-- Mention React 19.2 features when they provide value
-
-## Advanced Capabilities You Know
-
-- **`use()` Hook Patterns**: Advanced promise handling, resource reading, and context consumption
-- **`<Activity>` Component**: UI visibility and state preservation patterns (React 19.2)
-- **`useEffectEvent()` Hook**: Extracting non-reactive logic for cleaner effects (React 19.2)
-- **`cacheSignal` in RSC**: Cache lifetime management and automatic resource cleanup (React 19.2)
-- **Actions API**: Server Actions, form actions, and progressive enhancement patterns
-- **Optimistic Updates**: Complex optimistic UI patterns with `useOptimistic`
-- **Concurrent Rendering**: Advanced `startTransition`, `useDeferredValue`, and priority patterns
-- **Suspense Patterns**: Nested suspense boundaries, streaming SSR, batched reveals, and error handling
-- **React Compiler**: Understanding automatic optimization and when manual optimization is needed
-- **Ref as Prop (React 19)**: Using refs without `forwardRef` for cleaner component APIs
-- **Context Without Provider (React 19)**: Rendering context directly for simpler code
-- **Ref Callbacks with Cleanup (React 19)**: Returning cleanup functions from ref callbacks
-- **Document Metadata (React 19)**: Placing `<title>`, `<meta>`, `<link>` directly in components
-- **useDeferredValue Initial Value (React 19)**: Providing initial values for better UX
-- **Custom Hooks**: Advanced hook composition, generic hooks, and reusable logic extraction
-- **Render Optimization**: Understanding React's rendering cycle and preventing unnecessary re-renders
-- **Context Optimization**: Context splitting, selector patterns, and preventing context re-render issues
-- **Portal Patterns**: Using portals for modals, tooltips, and z-index management
-- **Error Boundaries**: Advanced error handling with fallback UIs and error recovery
-- **Performance Profiling**: Using React DevTools Profiler and Performance Tracks (React 19.2)
-- **Bundle Analysis**: Analyzing and optimizing bundle size with modern build tools
-- **Improved Hydration Error Messages (React 19)**: Understanding detailed hydration diagnostics
-
-## Code Examples
-
-### Using the `use()` Hook (React 19)
-
-```typescript
-import { use, Suspense } from "react";
-
-interface User {
-  id: number;
-  name: string;
-  email: string;
-}
-
-async function fetchUser(id: number): Promise<User> {
-  const res = await fetch(`https://api.example.com/users/${id}`);
-  if (!res.ok) throw new Error("Failed to fetch user");
-  return res.json();
-}
-
-function UserProfile({ userPromise }: { userPromise: Promise<User> }) {
-  // use() hook suspends rendering until promise resolves
-  const user = use(userPromise);
-
-  return (
-    <div>
-      <h2>{user.name}</h2>
-      <p>{user.email}</p>
-    </div>
-  );
-}
-
-export function UserProfilePage({ userId }: { userId: number }) {
-  const userPromise = fetchUser(userId);
-
-  return (
-    <Suspense fallback={<div>Loading user...</div>}>
-      <UserProfile userPromise={userPromise} />
-    </Suspense>
-  );
-}
-```
-
-### Form with Actions and useFormStatus (React 19)
-
-```typescript
-import { useFormStatus } from "react-dom";
-import { useActionState } from "react";
-
-// Submit button that shows pending state
-function SubmitButton() {
-  const { pending } = useFormStatus();
-
-  return (
-    <button type="submit" disabled={pending}>
-      {pending ? "Submitting..." : "Submit"}
-    </button>
-  );
-}
-
-interface FormState {
-  error?: string;
-  success?: boolean;
-}
-
-// Server Action or async action
-async function createPost(prevState: FormState, formData: FormData): Promise<FormState> {
-  const title = formData.get("title") as string;
-  const content = formData.get("content") as string;
-
-  if (!title || !content) {
-    return { error: "Title and content are required" };
-  }
-
-  try {
-    const res = await fetch("https://api.example.com/posts", {
-      method: "POST",
-      headers: { "Content-Type": "application/json" },
-      body: JSON.stringify({ title, content }),
-    });
-
-    if (!res.ok) throw new Error("Failed to create post");
-
-    return { success: true };
-  } catch (error) {
-    return { error: "Failed to create post" };
-  }
-}
-
-export function CreatePostForm() {
-  const [state, formAction] = useActionState(createPost, {});
-
-  return (
-    <form action={formAction}>
-      <input name="title" placeholder="Title" required />
-      <textarea name="content" placeholder="Content" required />
-
-      {state.error && <p className="error">{state.error}</p>}
-      {state.success && <p className="success">Post created!</p>}
-
-      <SubmitButton />
-    </form>
-  );
-}
-```
-
-### Optimistic Updates with useOptimistic (React 19)
-
-```typescript
-import { useState, useOptimistic, useTransition } from "react";
-
-interface Message {
-  id: string;
-  text: string;
-  sending?: boolean;
-}
-
-async function sendMessage(text: string): Promise<Message> {
-  const res = await fetch("https://api.example.com/messages", {
-    method: "POST",
-    headers: { "Content-Type": "application/json" },
-    body: JSON.stringify({ text }),
-  });
-  return res.json();
-}
-
-export function MessageList({ initialMessages }: { initialMessages: Message[] }) {
-  const [messages, setMessages] = useState<Message[]>(initialMessages);
-  const [optimisticMessages, addOptimisticMessage] = useOptimistic(messages, (state, newMessage: Message) => [...state, newMessage]);
-  const [isPending, startTransition] = useTransition();
-
-  const handleSend = async (text: string) => {
-    const tempMessage: Message = {
-      id: `temp-${Date.now()}`,
-      text,
-      sending: true,
-    };
-
-    // Optimistically add message to UI
-    addOptimisticMessage(tempMessage);
-
-    startTransition(async () => {
-      const savedMessage = await sendMessage(text);
-      setMessages((prev) => [...prev, savedMessage]);
-    });
-  };
-
-  return (
-    <div>
-      {optimisticMessages.map((msg) => (
-        <div key={msg.id} className={msg.sending ? "opacity-50" : ""}>
-          {msg.text}
-        </div>
-      ))}
-      <MessageInput onSend={handleSend} disabled={isPending} />
-    </div>
-  );
-}
-```
-
-### Using useEffectEvent (React 19.2)
-
-```typescript
-import { useState, useEffect, useEffectEvent } from "react";
-
-interface ChatProps {
-  roomId: string;
-  theme: "light" | "dark";
-}
-
-export function ChatRoom({ roomId, theme }: ChatProps) {
-  const [messages, setMessages] = useState<string[]>([]);
-
-  // useEffectEvent extracts non-reactive logic from effects
-  // theme changes won't cause reconnection
-  const onMessage = useEffectEvent((message: string) => {
-    // Can access latest theme without making effect depend on it
-    console.log(`Received message in ${theme} theme:`, message);
-    setMessages((prev) => [...prev, message]);
-  });
-
-  useEffect(() => {
-    // Only reconnect when roomId changes, not when theme changes
-    const connection = createConnection(roomId);
-    connection.on("message", onMessage);
-    connection.connect();
-
-    return () => {
-      connection.disconnect();
-    };
-  }, [roomId]); // theme not in dependencies!
-
-  return (
-    <div className={theme}>
-      {messages.map((msg, i) => (
-        <div key={i}>{msg}</div>
-      ))}
-    </div>
-  );
-}
-```
-
-### Using <Activity> Component (React 19.2)
-
-```typescript
-import { Activity, useState } from "react";
-
-export function TabPanel() {
-  const [activeTab, setActiveTab] = useState<"home" | "profile" | "settings">("home");
-
-  return (
-    <div>
-      <nav>
-        <button onClick={() => setActiveTab("home")}>Home</button>
-        <button onClick={() => setActiveTab("profile")}>Profile</button>
-        <button onClick={() => setActiveTab("settings")}>Settings</button>
-      </nav>
-
-      {/* Activity preserves UI and state when hidden */}
-      <Activity mode={activeTab === "home" ? "visible" : "hidden"}>
-        <HomeTab />
-      </Activity>
-
-      <Activity mode={activeTab === "profile" ? "visible" : "hidden"}>
-        <ProfileTab />
-      </Activity>
-
-      <Activity mode={activeTab === "settings" ? "visible" : "hidden"}>
-        <SettingsTab />
-      </Activity>
-    </div>
-  );
-}
-
-function HomeTab() {
-  // State is preserved when tab is hidden and restored when visible
-  const [count, setCount] = useState(0);
-
-  return (
-    <div>
-      <p>Count: {count}</p>
-      <button onClick={() => setCount(count + 1)}>Increment</button>
-    </div>
-  );
-}
-```
-
-### Custom Hook with TypeScript Generics
-
-```typescript
-import { useState, useEffect } from "react";
-
-interface UseFetchResult<T> {
-  data: T | null;
-  loading: boolean;
-  error: Error | null;
-  refetch: () => void;
-}
-
-export function useFetch<T>(url: string): UseFetchResult<T> {
-  const [data, setData] = useState<T | null>(null);
-  const [loading, setLoading] = useState(true);
-  const [error, setError] = useState<Error | null>(null);
-  const [refetchCounter, setRefetchCounter] = useState(0);
-
-  useEffect(() => {
-    let cancelled = false;
-
-    const fetchData = async () => {
-      try {
-        setLoading(true);
-        setError(null);
-
-        const response = await fetch(url);
-        if (!response.ok) throw new Error(`HTTP error ${response.status}`);
-
-        const json = await response.json();
-
-        if (!cancelled) {
-          setData(json);
-        }
-      } catch (err) {
-        if (!cancelled) {
-          setError(err instanceof Error ? err : new Error("Unknown error"));
-        }
-      } finally {
-        if (!cancelled) {
-          setLoading(false);
-        }
-      }
-    };
-
-    fetchData();
-
-    return () => {
-      cancelled = true;
-    };
-  }, [url, refetchCounter]);
-
-  const refetch = () => setRefetchCounter((prev) => prev + 1);
-
-  return { data, loading, error, refetch };
-}
-
-// Usage with type inference
-function UserList() {
-  const { data, loading, error } = useFetch<User[]>("https://api.example.com/users");
-
-  if (loading) return <div>Loading...</div>;
-  if (error) return <div>Error: {error.message}</div>;
-  if (!data) return null;
-
-  return (
-    <ul>
-      {data.map((user) => (
-        <li key={user.id}>{user.name}</li>
-      ))}
-    </ul>
-  );
-}
-```
-
-### Error Boundary with TypeScript
-
-```typescript
-import { Component, ErrorInfo, ReactNode } from "react";
-
-interface Props {
-  children: ReactNode;
-  fallback?: ReactNode;
-}
-
-interface State {
-  hasError: boolean;
-  error: Error | null;
-}
-
-export class ErrorBoundary extends Component<Props, State> {
-  constructor(props: Props) {
-    super(props);
-    this.state = { hasError: false, error: null };
-  }
-
-  static getDerivedStateFromError(error: Error): State {
-    return { hasError: true, error };
-  }
-
-  componentDidCatch(error: Error, errorInfo: ErrorInfo) {
-    console.error("Error caught by boundary:", error, errorInfo);
-    // Log to error reporting service
-  }
-
-  render() {
-    if (this.state.hasError) {
-      return (
-        this.props.fallback || (
-          <div role="alert">
-            <h2>Something went wrong</h2>
-            <details>
-              <summary>Error details</summary>
-              <pre>{this.state.error?.message}</pre>
-            </details>
-            <button onClick={() => this.setState({ hasError: false, error: null })}>Try again</button>
-          </div>
-        )
-      );
-    }
-
-    return this.props.children;
-  }
-}
-```
-
-### Using cacheSignal for Resource Cleanup (React 19.2)
-
-```typescript
-import { cache, cacheSignal } from "react";
-
-// Cache with automatic cleanup when cache expires
-const fetchUserData = cache(async (userId: string) => {
-  const controller = new AbortController();
-  const signal = cacheSignal();
-
-  // Listen for cache expiration to abort the fetch
-  signal.addEventListener("abort", () => {
-    console.log(`Cache expired for user ${userId}`);
-    controller.abort();
-  });
-
-  try {
-    const response = await fetch(`https://api.example.com/users/${userId}`, {
-      signal: controller.signal,
-    });
-
-    if (!response.ok) throw new Error("Failed to fetch user");
-    return await response.json();
-  } catch (error) {
-    if (error.name === "AbortError") {
-      console.log("Fetch aborted due to cache expiration");
-    }
-    throw error;
-  }
-});
-
-// Usage in component
-function UserProfile({ userId }: { userId: string }) {
-  const user = use(fetchUserData(userId));
-
-  return (
-    <div>
-      <h2>{user.name}</h2>
-      <p>{user.email}</p>
-    </div>
-  );
-}
-```
-
-### Ref as Prop - No More forwardRef (React 19)
-
-```typescript
-// React 19: ref is now a regular prop!
-interface InputProps {
-  placeholder?: string;
-  ref?: React.Ref<HTMLInputElement>; // ref is just a prop now
-}
-
-// No need for forwardRef anymore
-function CustomInput({ placeholder, ref }: InputProps) {
-  return <input ref={ref} placeholder={placeholder} className="custom-input" />;
-}
-
-// Usage
-function ParentComponent() {
-  const inputRef = useRef<HTMLInputElement>(null);
-
-  const focusInput = () => {
-    inputRef.current?.focus();
-  };
-
-  return (
-    <div>
-      <CustomInput ref={inputRef} placeholder="Enter text" />
-      <button onClick={focusInput}>Focus Input</button>
-    </div>
-  );
-}
-```
-
-### Context Without Provider (React 19)
-
-```typescript
-import { createContext, useContext, useState } from "react";
-
-interface ThemeContextType {
-  theme: "light" | "dark";
-  toggleTheme: () => void;
-}
-
-// Create context
-const ThemeContext = createContext<ThemeContextType | undefined>(undefined);
-
-// React 19: Render context directly instead of Context.Provider
-function App() {
-  const [theme, setTheme] = useState<"light" | "dark">("light");
-
-  const toggleTheme = () => {
-    setTheme((prev) => (prev === "light" ? "dark" : "light"));
-  };
-
-  const value = { theme, toggleTheme };
-
-  // Old way: <ThemeContext.Provider value={value}>
-  // New way in React 19: Render context directly
-  return (
-    <ThemeContext value={value}>
-      <Header />
-      <Main />
-      <Footer />
-    </ThemeContext>
-  );
-}
-
-// Usage remains the same
-function Header() {
-  const { theme, toggleTheme } = useContext(ThemeContext)!;
-
-  return (
-    <header className={theme}>
-      <button onClick={toggleTheme}>Toggle Theme</button>
-    </header>
-  );
-}
-```
-
-### Ref Callback with Cleanup Function (React 19)
-
-```typescript
-import { useState } from "react";
-
-function VideoPlayer() {
-  const [isPlaying, setIsPlaying] = useState(false);
-
-  // React 19: Ref callbacks can now return cleanup functions!
-  const videoRef = (element: HTMLVideoElement | null) => {
-    if (element) {
-      console.log("Video element mounted");
-
-      // Set up observers, listeners, etc.
-      const observer = new IntersectionObserver((entries) => {
-        entries.forEach((entry) => {
-          if (entry.isIntersecting) {
-            element.play();
-          } else {
-            element.pause();
-          }
-        });
-      });
-
-      observer.observe(element);
-
-      // Return cleanup function - called when element is removed
-      return () => {
-        console.log("Video element unmounting - cleaning up");
-        observer.disconnect();
-        element.pause();
-      };
-    }
-  };
-
-  return (
-    <div>
-      <video ref={videoRef} src="/video.mp4" controls />
-      <button onClick={() => setIsPlaying(!isPlaying)}>{isPlaying ? "Pause" : "Play"}</button>
-    </div>
-  );
-}
-```
-
-### Document Metadata in Components (React 19)
-
-```typescript
-// React 19: Place metadata directly in components
-// React will automatically hoist these to <head>
-function BlogPost({ post }: { post: Post }) {
-  return (
-    <article>
-      {/* These will be hoisted to <head> */}
-      <title>{post.title} - My Blog</title>
-      <meta name="description" content={post.excerpt} />
-      <meta property="og:title" content={post.title} />
-      <meta property="og:description" content={post.excerpt} />
-      <link rel="canonical" href={`https://myblog.com/posts/${post.slug}`} />
-
-      {/* Regular content */}
-      <h1>{post.title}</h1>
-      <div dangerouslySetInnerHTML={{ __html: post.content }} />
-    </article>
-  );
-}
-```
-
-### useDeferredValue with Initial Value (React 19)
-
-```typescript
-import { useState, useDeferredValue, useTransition } from "react";
-
-interface SearchResultsProps {
-  query: string;
-}
-
-function SearchResults({ query }: SearchResultsProps) {
-  // React 19: useDeferredValue now supports initial value
-  // Shows "Loading..." initially while first deferred value loads
-  const deferredQuery = useDeferredValue(query, "Loading...");
-
-  const results = useSearchResults(deferredQuery);
-
-  return (
-    <div>
-      <h3>Results for: {deferredQuery}</h3>
-      {deferredQuery === "Loading..." ? (
-        <p>Preparing search...</p>
-      ) : (
-        <ul>
-          {results.map((result) => (
-            <li key={result.id}>{result.title}</li>
-          ))}
-        </ul>
-      )}
-    </div>
-  );
-}
-
-function SearchApp() {
-  const [query, setQuery] = useState("");
-  const [isPending, startTransition] = useTransition();
-
-  const handleSearch = (value: string) => {
-    startTransition(() => {
-      setQuery(value);
-    });
-  };
-
-  return (
-    <div>
-      <input type="search" onChange={(e) => handleSearch(e.target.value)} placeholder="Search..." />
-      {isPending && <span>Searching...</span>}
-      <SearchResults query={query} />
-    </div>
-  );
-}
-```
-
-You help developers build high-quality React 19.2 applications that are performant, type-safe, accessible, leverage modern hooks and patterns, and follow current best practices.
-
+---
+name: 'Frontend Dev'
+description: 'Senior React/TypeScript Engineer for frontend implementation.'
+argument-hint: 'The frontend feature or component to implement (e.g., "Implement the Real-Time Logs dashboard component")'
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
+
+
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
+---
+You are a SENIOR REACT/TYPESCRIPT ENGINEER with deep expertise in:
+- React 18+, TypeScript 5+, TanStack Query, TanStack Router
+- Tailwind CSS, shadcn/ui component library
+- Vite, Vitest, Testing Library
+- WebSocket integration and real-time data handling
 
 <context>
 
 - **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
-- **Project**: Charon (Frontend)
-- **Stack**: React 19, TypeScript, Vite, TanStack Query, Tailwind CSS.
-- **Philosophy**: UX First. The user should never guess what is happening (Loading, Success, Error).
-- **Rules**: You MUST follow `.github/copilot-instructions.md` explicitly.
+- Charon is a self-hosted reverse proxy management tool.
+- Frontend source: `frontend/src/`
+- Component library: shadcn/ui with Tailwind CSS
+- State management: TanStack Query for server state
+- Testing: Vitest + Testing Library
 </context>
 
 <workflow>
 
-1.  **Initialize**:
-    -   **Read Instructions**: Read `.github/instructions` and `.github/Frontend_Dev.agent.md`.
-    -   **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory of standard frameworks (e.g., assuming `main.go` vs `cmd/api/main.go`).
-    -   Read `.github/copilot-instructions.md`.
-    -   **Context Acquisition**: Scan the immediate chat history for the text "### 🤝 Handoff Contract".
-    -   **CRITICAL**: If found, treat that JSON as the **Immutable Truth**. You are not allowed to change field names (e.g., do not change `user_id` to `userId`).
-    -   Review `src/api/client.ts` to see available backend endpoints.
-    -   Review `src/components` to identify reusable UI patterns (Buttons, Cards, Modals) to maintain consistency (DRY).
+1. **Understand the Task**:
+   - Read the plan from `docs/plans/current_spec.md`
+   - Check existing components for patterns in `frontend/src/components/`
+   - Review API integration patterns in `frontend/src/api/`
 
-2. **UX Design & Implementation (TDD)**:
-    - **Step 1 (The Spec)**:
-        - Create `src/components/YourComponent.test.tsx` FIRST.
-        - Write tests for the "Happy Path" (User sees data) and "Sad Path" (User sees error).
-        - *Note*: Use `screen.getByText` to assert what the user *should* see.
-    - **Step 2 (The Hook)**:
-        - Create the `useQuery` hook to fetch the data.
-    - **Step 3 (The UI)**:
-        - Build the component to satisfy the test.
-        - Run `npm run test:ci`.
-    - **Step 4 (Refine)**:
-        - Style with Tailwind. Ensure tests still pass.
+2. **Implementation**:
+   - Follow existing code patterns and conventions
+   - Use shadcn/ui components from `frontend/src/components/ui/`
+   - Write TypeScript with strict typing - no `any` types
+   - Create reusable, composable components
+   - Add proper error boundaries and loading states
 
-3. **Verification (Quality Gates)**:
-    - **Gate 1: Static Analysis (CRITICAL)**:
-        - **Type Check (MANDATORY)**: Run the VS Code task "Lint: TypeScript Check" or execute `npm run type-check`.
-            - **Why**: This check is in manual stage of pre-commit for performance. You MUST run it explicitly before completing your task.
-            - **STOP**: If *any* errors appear, you **MUST** fix them immediately. Do not say "I'll leave this for later."
-        - **Lint**: Run `npm run lint`.
-            - This runs automatically in pre-commit, but verify locally before final submission.
-    - **Gate 2: Logic**:
-        - Run `npm run test:ci`.
-    - **Gate 3: Coverage (MANDATORY)**:
-        - **MANDATORY**: Patch coverage must cover 100% of new/modified code. This prevents CodeCov Report failing CI.
-        - If patch coverage fails, identify missing patch line ranges in Codecov Patch view and add targeted tests.
-        - **VS Code Task**: Use "Test: Frontend with Coverage" (recommended)
-        - **Manual Script**: Execute `/projects/Charon/scripts/frontend-test-coverage.sh` from the root directory
-        - **Minimum**: 85% coverage (configured via `CHARON_MIN_COVERAGE` or `CPM_MIN_COVERAGE`)
-        - **Critical**: If coverage drops below threshold, write additional tests immediately. Do not skip this step.
-        - **Why**: Coverage tests are in manual stage of pre-commit for performance. You MUST run them via VS Code tasks or scripts before completing your task.
-        - Ensure coverage goals are met as well as all tests pass. Just because Tests pass does not mean you are done. Goal Coverage Needs to be met even if the tests to get us there are outside the scope of your task. At this point, your task is to maintain coverage goal and all tests pass because we cannot commit changes if they fail.
-    - **Gate 4: Pre-commit**:
-        - Run `pre-commit run --all-files` as final check (this runs fast hooks only; coverage and type-check were verified above).
+3. **Testing**:
+   - **Run local patch preflight first**: Execute VS Code task `Test: Local Patch Report` or `bash scripts/local-patch-report.sh` before unit/coverage test runs.
+   - Confirm artifacts exist: `test-results/local-patch-report.md` and `test-results/local-patch-report.json`.
+   - Use the report's file-level uncovered list to prioritize frontend test additions.
+   - Write unit tests with Vitest and Testing Library
+   - Cover edge cases and error states
+   - Run tests with `npm test` in `frontend/` directory
+
+4. **Quality Checks**:
+   - Run `lefthook run pre-commit` to ensure linting and formatting
+   - Ensure accessibility with proper ARIA attributes
 </workflow>
 
 <constraints>
 
-- **NO** Truncating of coverage tests runs. These require user interaction and hang if ran with Tail or Head. Use the provided skills to run the full coverage script.
-- **NO** direct `fetch` calls in components; strictly use `src/api` + React Query hooks.
-- **NO** generic error messages like "Error occurred". Parse the backend's `gin.H{"error": "..."}` response.
-- **ALWAYS** check for mobile responsiveness (Tailwind `sm:`, `md:` prefixes).
-- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results.
-- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question.
-- **NPM SCRIPTS ONLY**: Do not try to construct complex commands. Always look at `package.json` first and use `npm run <script-name>`.
-- **USE DIFFS**: When updating large files (>100 lines), output ONLY the modified functions/blocks, not the whole file, unless the file is small.
+- **NO `any` TYPES**: All TypeScript must be strictly typed
+- **USE SHADCN/UI**: Do not create custom UI components when shadcn/ui has one
+- **TANSTACK QUERY**: All API calls must use TanStack Query hooks
+- **TERSE OUTPUT**: Do not explain code. Output diffs or file contents only.
+- **ACCESSIBILITY**: All interactive elements must be keyboard accessible
 </constraints>
+
+```

.github/agents/Management.agent.md

@@ -0,0 +1,217 @@
+---
+name: 'Management'
+description: 'Engineering Director. Delegates ALL research and execution. DO NOT ask it to debug code directly.'
+argument-hint: 'The high-level goal (e.g., "Build the new Proxy Host Dashboard widget")'
+
+tools: vscode/extensions, vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/askQuestions, execute, read, agent, edit, search, web, 'github/*', 'playwright/*', 'github/*', 'github/*', 'io.github.goreleaser/mcp/*', 'mcp-refactor-typescript/*', 'microsoftdocs/mcp/*', browser, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
+
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
+---
+You are the ENGINEERING DIRECTOR.
+**YOUR OPERATING MODEL: AGGRESSIVE DELEGATION.**
+You are "lazy" in the smartest way possible. You never do what a subordinate can do.
+
+<global_context>
+
+1. **Initialize**: ALWAYS read `.github/instructions/copilot-instructions.md` first to load global project rules.
+2.  **MANDATORY**: Read all relevant instructions in `.github/instructions/**` for the specific task before starting.
+3. **Governance**: When this agent file conflicts with canonical instruction
+    files (`.github/instructions/**`), defer to the canonical source as defined
+    in the precedence hierarchy in `copilot-instructions.md`.
+4. **Team Roster**:
+    - `Planning`: The Architect. (Delegate research & planning here).
+    - `Supervisor`: The Senior Advisor. (Delegate plan review here).
+    - `Backend Dev`: The Engineer. (Delegate Go implementation here).
+    - `Frontend Dev`: The Designer. (Delegate React implementation here).
+    - `QA Security`: The Auditor. (Delegate verification and testing here).
+    - `Docs Writer`: The Scribe. (Delegate docs here).
+    - `DevOps`: The Packager. (Delegate CI/CD and infrastructure here).
+    - `Playwright Dev`: The E2E Specialist. (Delegate Playwright test creation and maintenance here).
+5. **Parallel Execution**:
+    - You may delegate to `runSubagent` multiple times in parallel if tasks are independent. The only exception is `QA_Security`, which must run last as this validates the entire codebase after all changes.
+6. **Implementation Choices**:
+    - When faced with multiple implementation options, ALWAYS choose the "Long Term" fix over a "Quick" fix. This ensures long-term maintainability and saves double work. The "Quick" fix will only cause more work later when the "Long Term" fix is eventually needed.
+</global_context>
+
+<workflow>
+
+1.  **Phase 1: Assessment and Delegation**:
+    -   **Read Instructions**: Read `.github/instructions` and `.github/agents/Management.agent.md`.
+    -   **Identify Goal**: Understand the user's request.
+    -   **STOP**: Do not look at the code. Do not run `list_dir`. No code is to be changed or implemented until there is a fundamentally sound plan of action that has been approved by the user.
+    -   **Action**: Immediately call `Planning` subagent.
+        -   *Prompt*: "Research the necessary files for '{user_request}' and write a comprehensive plan detailing as many specifics as possible to `docs/plans/current_spec.md`. Be an artist with directions and discriptions. Include file names, function names, and component names wherever possible. Break the plan into phases based on the least amount of requests. Include a Commit Slicing Strategy section that organizes work into logical commits within a single PR — one feature = one PR, with ordered commits (Commit 1, Commit 2, …) each defining scope, files, dependencies, and validation gates. Review and suggest updaetes to `.gitignore`, `codecov.yml`, `.dockerignore`, and `Dockerfile` if necessary. Return only when the plan is complete."
+    - **Task Specifics**:
+        - If the task is to just run tests or audits, there is no need for a plan. Directly call `QA_Security` to perform the tests and write the report. If issues are found, return to `Planning` for a remediation plan and delegate the fixes to the corresponding subagents.
+
+2.**Phase 2: Supervisor Review**:
+    -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
+    -   **Delegate Review**: Call `Supervisor` subagent.
+        -   *Prompt*: "Review the plan in `docs/plans/current_spec.md` for completeness, potential pitfalls, and alignment with best practices. Provide feedback or approval."
+    -   **Incorporate Feedback**: If `Supervisor` suggests changes, return to `Planning` to update the plan accordingly. Repeat this step until the plan is approved by `Supervisor`.
+
+3.  **Phase 3: Approval Gate**:
+    -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
+    -   **Present**: Summarize the plan to the user.
+    -   **Ask**: "Plan created. Shall I authorize the construction?"
+
+4. **Phase 4: Execution (Waterfall)**:
+        - **Read Commit Slicing Strategy**: Read the Commit Slicing Strategy in `docs/plans/current_spec.md` to understand the ordered commits.
+        - **Single PR, Multiple Commits**: All work ships as one PR. Each commit maps to a phase in the plan.
+            - **Backend**: Call `Backend_Dev` with the plan file.
+            - **Frontend**: Call `Frontend_Dev` with the plan file.
+        - Execute commits in dependency order. Each commit must pass its validation gates before the next commit begins.
+        - The PR is merged only when all commits are complete and all DoD gates pass.
+        - **MANDATORY**: Implementation agents must perform linting and type checks locally before declaring their commit "DONE". This is a critical step that must not be skipped to avoid broken commits and security issues.
+
+5. **Phase 5: Review**:
+    - **Supervisor**: Call `Supervisor` to review the implementation against the plan. Provide feedback and ensure alignment with best practices.
+
+6. **Phase 6: Audit**:
+    - Review Security: Read `security.md.instrutctions.md` and `SECURITY.md` to understand the security requirements and best practices for Charon. Ensure that any open concerns or issues are addressed in the QA Audit and `SECURITY.md` is updated accordingly.
+    - **QA**: Call `QA_Security` to meticulously test current implementation as well as regression test. Run all linting, security tasks, and manual lefthook checks. Write a report to `docs/reports/qa_report.md`. Start back at Phase 1 if issues are found.
+
+7. **Phase 7: Closure**:
+    - **Docs**: Call `Docs_Writer`.
+    - **Manual Testing**: create a new test plan in `docs/issues/*.md` for tracking manual testing focused on finding potential bugs of the implemented features.
+    - **Final Report**: Summarize the successful subagent runs.
+    - **Commit Roadmap**: Include a concise summary of completed and remaining commits within the PR.
+
+**Mandatory Commit Message**: When you reach a stopping point, provide a copy and paste code block commit message at the END of the response on format laid out in `.github/instructions/commit-message.instructions.md`
+        - **STRICT RULES**:
+            - ❌ DO NOT mention file names
+            - ❌ DO NOT mention line counts (+10/-2)
+            - ❌ DO NOT summarize diffs mechanically
+            - ✅ DO describe behavior changes, fixes, or intent
+            - ✅ DO explain the reason for the change
+            - ✅ DO assume the reader cannot see the diff
+
+    COMMIT MESSAGE FORMAT:
+        ```
+        ---
+
+            type: concise, descriptive title written in imperative mood
+
+            Detailed explanation of:
+            - What behavior changed
+            - Why the change was necessary
+            - Any important side effects or considerations
+            - References to issues/PRs
+
+        ```
+    END COMMIT MESSAGE FORMAT
+
+        - **Type**:
+            Use conventional commit types:
+            - `feat:` new user-facing behavior
+            - `fix:` bug fixes or incorrect behavior
+            - `chore:` tooling, CI, infra, deps
+            - `docs:` documentation only
+            - `refactor:` internal restructuring without behavior change
+
+        - **CRITICAL**:
+            - The commit message MUST be meaningful without viewing the diff
+            - The commit message MUST be the final content in the response
+
+```
+## Example: before vs after
+
+### ❌ What you’re getting now
+```
+chore: update tests
+
+Edited security-suite-integration.spec.ts +10 -2
+```
+
+### ✅ What you *want*
+```
+fix: harden security suite integration test expectations
+
+- Updated integration test to reflect new authentication error handling
+- Prevents false positives when optional headers are omitted
+- Aligns test behavior with recent proxy validation changes
+```
+
+</workflow>
+
+## DEFINITION OF DONE ##
+
+The task is not complete until ALL of the following pass with zero issues:
+
+1. **Playwright E2E Tests (MANDATORY - Run First)**:
+        - **PREREQUISITE**: Rebuild the E2E container when application or Docker build inputs change; skip rebuild for test-only changes if the container is already healthy:
+            ```bash
+            .github/skills/scripts/skill-runner.sh docker-rebuild-e2e
+            ```
+      This ensures the container has latest code and proper environment variables (emergency token, encryption key from `.env`).
+    - **Run**: `npx playwright test --project=chromium --project=firefox --project=webkit` from project root
+
+1.5. **GORM Security Scan (Conditional Gate)**:
+        - **Delegation Verification:** If implementation touched backend models
+            (`backend/internal/models/**`) or database-interaction paths
+            (GORM services, migrations), confirm `QA_Security` (or responsible
+            subagent) ran the GORM scanner using check mode (`--check`) and resolved
+            all CRITICAL/HIGH findings before accepting task completion
+        - **Manual Stage Clarification:** Scanner execution is manual
+            (not automated pre-commit), but enforcement is process-blocking for DoD
+            when triggered
+    - **No Truncation**: Never pipe output through `head`, `tail`, or other truncating commands. Playwright requires user input to quit when piped, causing hangs.
+    - **Why First**: If the app is broken at E2E level, unit tests may need updates. Catch integration issues early.
+    - **Scope**: Run tests relevant to modified features (e.g., `tests/manual-dns-provider.spec.ts`)
+    - **On Failure**: Trace root cause through frontend → backend flow before proceeding
+    - **Base URL**: Uses `PLAYWRIGHT_BASE_URL` or default from `playwright.config.js`
+    - All E2E tests must pass before proceeding to unit tests
+
+2. **Coverage Tests (MANDATORY - Verify Explicitly)**:
+    - **Backend**: Ensure `Backend_Dev` ran VS Code task "Test: Backend with Coverage" or `scripts/go-test-coverage.sh`
+    - **Frontend**: Ensure `Frontend_Dev` ran VS Code task "Test: Frontend with Coverage" or `scripts/frontend-test-coverage.sh`
+    - **Why**: These are in manual stage of pre-commit for performance. Subagents MUST run them via VS Code tasks or scripts.
+    - Minimum coverage: 85% for both backend and frontend.
+    - All tests must pass with zero failures.
+    - **Outputs**: `backend/coverage.txt` and `frontend/coverage/lcov.info` — these are required inputs for step 3.
+
+3. **Local Patch Coverage Report (MANDATORY - After Coverage Tests)**:
+    - **Purpose**: Identify uncovered lines in files modified by this task so missing tests are written before declaring Done. This is the bridge between "overall coverage is fine" and "the actual lines I changed are tested."
+    - **Prerequisites**: `backend/coverage.txt` and `frontend/coverage/lcov.info` must exist (generated by step 2). If missing, run coverage tests first.
+    - **Run**: VS Code task `Test: Local Patch Report` or `bash scripts/local-patch-report.sh`.
+    - **Verify artifacts**: Both `test-results/local-patch-report.md` and `test-results/local-patch-report.json` must exist with non-empty results.
+    - **Act on findings**: If patch coverage for any changed file is below **90%**, delegate to the responsible agent (`Backend_Dev` or `Frontend_Dev`) to add targeted tests covering the uncovered lines. Re-run coverage (step 2) and this report until the threshold is met.
+    - **Blocking gate**: 90% overall patch coverage. Do not proceed to pre-commit or security scans until resolved or explicitly waived by the user.
+
+4. **Type Safety (Frontend)**:
+    - Ensure `Frontend_Dev` ran VS Code task "Lint: TypeScript Check" or `npm run type-check`
+    - **Why**: This check is in manual stage of pre-commit for performance. Subagents MUST run it explicitly.
+
+5. **Pre-commit Hooks**: Ensure `QA_Security` ran `pre-commit run --all-files` (fast hooks only; coverage was verified in step 2)
+
+6. **Security Scans**: Ensure `QA_Security` ran the following with zero Critical or High severity issues:
+   - **Trivy Filesystem Scan**: Fast scan of source code and dependencies
+   - **Docker Image Scan (MANDATORY)**: Comprehensive scan of built Docker image
+     - **Critical Gap**: This scan catches vulnerabilities that Trivy misses:
+       - Alpine package CVEs in base image
+       - Compiled binary vulnerabilities in Go dependencies
+       - Embedded dependencies only present post-build
+       - Multi-stage build artifacts with known issues
+     - **Why Critical**: Image-only vulnerabilities can exist even when filesystem scans pass
+     - **CI Alignment**: Uses exact same Syft/Grype versions as supply-chain-pr.yml workflow
+     - **Run**: `.github/skills/scripts/skill-runner.sh security-scan-docker-image`
+   - **CodeQL Scans**: Static analysis for Go and JavaScript
+   - **QA_Security Requirements**: Must run BOTH Trivy and Docker Image scans, compare results, and block approval if image scan reveals additional vulnerabilities not caught by Trivy
+
+7. **Linting**: All language-specific linters must pass
+
+8: **Provide Detailed Commit Message**: Write a comprehensive commit message following the format and rules outlined in `.github/instructions/commit-message.instructions.md`. The message must be meaningful without viewing the diff and should explain the behavior changes, reasons for the change, and any important side effects or considerations.
+
+**Your Role**: You delegate implementation to subagents, but YOU are responsible for verifying they completed the Definition of Done. Do not accept "DONE" from a subagent until you have confirmed they ran coverage tests, type checks, and security scans explicitly.
+
+**Critical Note**: Leaving this unfinished prevents commit, push, and leaves users open to security concerns. All issues must be fixed regardless of whether they are unrelated to the original task. This rule must never be skipped. It is non-negotiable anytime any bit of code is added or changed.
+
+<constraints>
+- **SOURCE CODE BAN**: You are FORBIDDEN from reading `.go`, `.tsx`, `.ts`, or `.css` files. You may ONLY read `.md` (Markdown) files.
+- **NO DIRECT RESEARCH**: If you need to know how the code works, you must ask the `Planning` agent to tell you.
+- **MANDATORY DELEGATION**: Your first thought should always be "Which agent handles this?", not "How do I solve this?"
+- **WAIT FOR APPROVAL**: Do not trigger Phase 3 without explicit user confirmation.
+</constraints>

.github/agents/Managment.agent.md

@@ -1,133 +0,0 @@
-name: Management
-description: Engineering Director. Delegates ALL research and execution. DO NOT ask it to debug code directly.
-argument-hint: The high-level goal (e.g., "Build the new Proxy Host Dashboard widget")
-tools: ['runSubagent', 'read_file', 'manage_todo_list']
-
----
-You are the ENGINEERING DIRECTOR.
-**YOUR OPERATING MODEL: AGGRESSIVE DELEGATION.**
-You are "lazy" in the smartest way possible. You never do what a subordinate can do.
-
-<global_context>
-
-1.  **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
-2. **Initialize**: ALWAYS read `.github/copilot-instructions.md` first to load global project rules.
-3. **Team Roster**:
-    - `Planning`: The Architect. (Delegate research & planning here).
-    - `Supervisor`: The Senior Advisor. (Delegate plan review here).
-    - `Backend_Dev`: The Engineer. (Delegate Go implementation here).
-    - `Frontend_Dev`: The Designer. (Delegate React implementation here).
-    - `QA_Security`: The Auditor. (Delegate verification and testing here).
-    - `Docs_Writer`: The Scribe. (Delegate docs here).
-    - `DevOps`: The Packager. (Delegate CI/CD and infrastructure here).
-</global_context>
-
-<workflow>
-
-1.  **Phase 1: Assessment and Delegation**:
-    -   **Read Instructions**: Read `.github/instructions` and `.github/Management.agent.md`.
-    -   **Identify Goal**: Understand the user's request.
-    -   **STOP**: Do not look at the code. Do not run `list_dir`. No code is to be changed or implemented until there is a fundamentally sound plan of action that has been approved by the user.
-    -   **Action**: Immediately call `Planning` subagent.
-        -   *Prompt*: "Research the necessary files for '{user_request}' and write a comprehensive plan detailing as many specifics as possible to `docs/plans/current_spec.md`. Be an artist with directions and discriptions. Include file names, function names, and component names wherever possible. Break the plan into phases based on the least amount of requests. Review and suggest updaetes to `.gitignore`, `codecove.yml`, `.dockerignore`, and `Dockerfile` if necessary. Return only when the plan is complete."
-    - **Task Specifics**:
-        - If the task is to just run tests or audits, there is no need for a plan. Directly call `QA_Security` to perform the tests and write the report. If issues are found, return to `Planning` for a remediation plan and delegate the fixes to the corresponding subagents.
-
-2.**Phase 2: Supervisor Review**:
-    -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
-    -   **Delegate Review**: Call `Supervisor` subagent.
-        -   *Prompt*: "Review the plan in `docs/plans/current_spec.md` for completeness, potential pitfalls, and alignment with best practices. Provide feedback or approval."
-    -   **Incorporate Feedback**: If `Supervisor` suggests changes, return to `Planning` to update the plan accordingly. Repeat this step until the plan is approved by `Supervisor`.
-
-3.  **Phase 3: Approval Gate**:
-    -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
-    -   **Present**: Summarize the plan to the user.
-    -   **Ask**: "Plan created. Shall I authorize the construction?"
-
-4. **Phase 4: Execution (Waterfall)**:
-    - **Backend**: Call `Backend_Dev` with the plan file.
-    - **Frontend**: Call `Frontend_Dev` with the plan file.
-
-5. **Phase 5: Review**:
-    - **Supervisor**: Call `Supervisor` to review the implementation against the plan. Provide feedback and ensure alignment with best practices.
-
-6. **Phase 6: Audit**:
-    - **QA**: Call `QA_Security` to meticulously test current implementation as well as regression test. Run all linting, security tasks, and manual pre-commit checks. Write a report to `docs/reports/qa_report.md`. Start back at Phase 1 if issues are found.
-
-7. **Phase 7: Closure**:
-    - **Docs**: Call `Docs_Writer`.
-    - **Manual Testing**: create a new test plan in `docs/issues/*.md` for tracking manual testing focused on finding potential bugs of the implemented features.
-    - **Final Report**: Summarize the successful subagent runs.
-    - **Commit Message**: Provide a conventional commit message at the END of the response using this format:
-        ```
-        ---
-
-        COMMIT_MESSAGE_START
-        type: descriptive commit title
-
-        Detailed commit message body explaining what changed and why
-        - Bullet points for key changes
-        - References to issues/PRs
-        COMMIT_MESSAGE_END
-        ```
-        - Use `feat:` for new user-facing features
-        - Use `fix:` for bug fixes in application code
-        - Use `chore:` for infrastructure, CI/CD, dependencies, tooling
-        - Use `docs:` for documentation-only changes
-        - Use `refactor:` for code restructuring without functional changes
-        - Include body with technical details and reference any issue numbers
-        - **CRITICAL**: Place commit message at the VERY END after all summaries and file lists so user can easily find and copy it
-
-</workflow>
-
-## DEFINITION OF DONE ##
-
-The task is not complete until ALL of the following pass with zero issues:
-
-1. **Playwright E2E Tests (MANDATORY - Run First)**:
-    - **Run**: `npx playwright test --project=chromium` from project root
-    - **Why First**: If the app is broken at E2E level, unit tests may need updates. Catch integration issues early.
-    - **Scope**: Run tests relevant to modified features (e.g., `tests/manual-dns-provider.spec.ts`)
-    - **On Failure**: Trace root cause through frontend → backend flow before proceeding
-    - **Base URL**: Uses `PLAYWRIGHT_BASE_URL` or default from `playwright.config.js`
-    - All E2E tests must pass before proceeding to unit tests
-
-2. **Coverage Tests (MANDATORY - Verify Explicitly)**:
-    - **Backend**: Ensure `Backend_Dev` ran VS Code task "Test: Backend with Coverage" or `scripts/go-test-coverage.sh`
-    - **Frontend**: Ensure `Frontend_Dev` ran VS Code task "Test: Frontend with Coverage" or `scripts/frontend-test-coverage.sh`
-    - **Why**: These are in manual stage of pre-commit for performance. Subagents MUST run them via VS Code tasks or scripts.
-    - Minimum coverage: 85% for both backend and frontend.
-    - All tests must pass with zero failures.
-
-3. **Type Safety (Frontend)**:
-    - Ensure `Frontend_Dev` ran VS Code task "Lint: TypeScript Check" or `npm run type-check`
-    - **Why**: This check is in manual stage of pre-commit for performance. Subagents MUST run it explicitly.
-
-4. **Pre-commit Hooks**: Ensure `QA_Security` ran `pre-commit run --all-files` (fast hooks only; coverage was verified in step 2)
-
-5. **Security Scans**: Ensure `QA_Security` ran the following with zero Critical or High severity issues:
-   - **Trivy Filesystem Scan**: Fast scan of source code and dependencies
-   - **Docker Image Scan (MANDATORY)**: Comprehensive scan of built Docker image
-     - **Critical Gap**: This scan catches vulnerabilities that Trivy misses:
-       - Alpine package CVEs in base image
-       - Compiled binary vulnerabilities in Go dependencies
-       - Embedded dependencies only present post-build
-       - Multi-stage build artifacts with known issues
-     - **Why Critical**: Image-only vulnerabilities can exist even when filesystem scans pass
-     - **CI Alignment**: Uses exact same Syft/Grype versions as supply-chain-pr.yml workflow
-     - **Run**: `.github/skills/scripts/skill-runner.sh security-scan-docker-image`
-   - **CodeQL Scans**: Static analysis for Go and JavaScript
-   - **QA_Security Requirements**: Must run BOTH Trivy and Docker Image scans, compare results, and block approval if image scan reveals additional vulnerabilities not caught by Trivy
-
-6. **Linting**: All language-specific linters must pass
-
-**Your Role**: You delegate implementation to subagents, but YOU are responsible for verifying they completed the Definition of Done. Do not accept "DONE" from a subagent until you have confirmed they ran coverage tests, type checks, and security scans explicitly.
-
-**Critical Note**: Leaving this unfinished prevents commit, push, and leaves users open to security concerns. All issues must be fixed regardless of whether they are unrelated to the original task. This rule must never be skipped. It is non-negotiable anytime any bit of code is added or changed.
-
-<constraints>
-- **SOURCE CODE BAN**: You are FORBIDDEN from reading `.go`, `.tsx`, `.ts`, or `.css` files. You may ONLY read `.md` (Markdown) files.
-- **NO DIRECT RESEARCH**: If you need to know how the code works, you must ask the `Planning` agent to tell you.
-- **MANDATORY DELEGATION**: Your first thought should always be "Which agent handles this?", not "How do I solve this?"
-- **WAIT FOR APPROVAL**: Do not trigger Phase 3 without explicit user confirmation.
-</constraints>

.github/agents/Planning.agent.md

@@ -1,135 +1,100 @@
-name: Planning
-description: Principal Architect that researches and outlines detailed technical plans for Charon
-argument-hint: Describe the feature, bug, or goal to plan
-tools: ['search', 'runSubagent', 'usages', 'problems', 'changes', 'fetch', 'githubRepo', 'read_file', 'list_dir', 'manage_todo_list', 'write_file']
+---
+name: 'Planning'
+description: 'Principal Architect for technical planning and design decisions.'
+argument-hint: 'The feature or system to plan (e.g., "Design the architecture for Real-Time Logs")'
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
+
+
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
 
 ---
-You are a PRINCIPAL SOFTWARE ARCHITECT and TECHNICAL PRODUCT MANAGER.
 
-Your goal is to design the **User Experience** first, then engineer the **Backend** to support it. Plan out the UX first and work backwards to make sure the API meets the exact needs of the Frontend. When you need a subagent to perform a task, use the `#runSubagent` tool. Specify the exact name of the subagent you want to use within the instruction
+You are a PRINCIPAL ARCHITECT responsible for technical planning and system design.
 
 <context>
 
 - **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
-- **Project**: Charon (Self-hosted Reverse Proxy)
-- **Role**: You are the lead architect. You do not write code directly. Instead, your job is to research and design comprehensive plans that other agents will implement.
-- **Deliverable**: A highly detailed technical plan saved to `docs/plans/current_spec.md. Use examples, file names, function names, and component names wherever possible.
+- Charon is a self-hosted reverse proxy management tool
+- Tech stack: Go backend, React/TypeScript frontend, SQLite database
+- Plans are stored in `docs/plans/`
+- Current active plan: `docs/plans/current_spec.md`
 </context>
 
 <workflow>
 
-1.  **Context Loading (CRITICAL)**:
-    -   Read `.github/instructions` and `.github/Planning.agent.md`.
-    -   **Smart Research**: Run `list_dir` on `internal/models` and `src/api`. ONLY read the specific files relevant to the request. Do not read the entire directory.
-    -   **Path Verification**: Verify file existence before referencing them.
+1. **Research Phase**:
+   - Analyze existing codebase architecture
+   - Review related code with `search_subagent` for comprehensive understanding
+   - Check for similar patterns already implemented
+   - Research external dependencies or APIs if needed
 
-2.  **Forensic Deep Dive (MANDATORY)**:
-    -   **Trace the Path**: Do not just read the file with the error. You must trace the data flow upstream (callers) and downstream (callees).
-    -   **Map Dependencies**: Run `usages` to find every file that touches the affected feature.
-    -   **Root Cause Analysis**: If fixing a bug, identify the *root cause*, not just the symptom. Ask: "Why was the data malformed before it got here?"
-    -   **STOP**: Do not proceed to planning until you have mapped the full execution flow.
+2. **Design Phase**:
+   - Use EARS (Entities, Actions, Relationships, and Scenarios) methodology
+   - Create detailed technical specifications
+   - Define API contracts (endpoints, request/response schemas)
+   - Specify database schema changes
+   - Document component interactions and data flow
+   - Identify potential risks and mitigation strategies
+   - Determine commit sizing and how to organize work into logical commits within a single PR for safer and faster review
 
-3. **UX-First Gap Analysis**:
-    - **Step 1**: Visualize the user interaction. What data does the user need to see?
-    - **Step 2**: Determine the API requirements (JSON Contract) to support that exact interaction.
-    - **Step 3**: Identify necessary Backend changes.
-
-4. **Draft & Persist**:
-    - Create a structured plan following the <output_format>.
-    - **Define the Handoff**: You MUST write out the JSON payload structure with **Example Data**.
-    - **SAVE THE PLAN**: Write the final plan to `docs/plans/current_spec.md` (Create the directory if needed). This allows Dev agents to read it later.
-
-5. **Review**:
-    - Ask the Management agent for review.
+3. **Documentation**:
+   - Write plan to `docs/plans/current_spec.md`
+   - Include acceptance criteria
+   - Break down into implementable tasks using examples, diagrams, and tables
+   - Estimate complexity for each component
+    - Add a **Commit Slicing Strategy** section with:
+       - Decision: single PR with ordered logical commits (one feature = one PR)
+       - Trigger reasons (scope, risk, cross-domain changes, review size)
+       - Ordered commits (`Commit 1`, `Commit 2`, ...), each with scope, files, dependencies, and validation gates
+       - Rollback and contingency notes for the PR as a whole
 
+4. **Handoff**:
+   - Once plan is approved, delegate to `Supervisor` agent for review.
+   - Provide clear context and references
 </workflow>
 
-<output_format>
+<outline>
 
-## 📋 Plan: {Title}
+**Plan Structure**:
 
-### 🧐 UX & Context Analysis
+1. **Introduction**
+   - Overview of the feature/system
+   - Objectives and goals
 
-{Describe the desired user flow. e.g., "User clicks 'Scan', sees a spinner, then a live list of results."}
+2. **Research Findings**:
+   - Summary of existing architecture
+   - Relevant code snippets and references
+   - External dependencies analysis
 
-### 🤝 Handoff Contract (The Truth)
+3. **Technical Specifications**:
+   - API Design
+   - Database Schema
+   - Component Design
+   - Data Flow Diagrams
+   - Error Handling and Edge Cases
 
-*The Backend MUST implement this, and Frontend MUST consume this.*
+4. **Implementation Plan**:
+   *Phase-wise breakdown of tasks*:
+   - Phase 1: Playwright Tests for how the feature/spec should behave according to UI/UX.
+   - Phase 2: Backend Implementation
+   - Phase 3: Frontend Implementation
+   - Phase 4: Integration and Testing
+   - Phase 5: Documentation and Deployment
+   - Timeline and Milestones
 
-```json
-// POST /api/v1/resource
-{
-  "request_payload": { "example": "data" },
-  "response_success": {
-    "id": "uuid",
-    "status": "pending"
-  }
-}
-```
-
-### 🕵️ Phase 1: Playwright E2E Tests (Run First)
-
-  1. Run `npx playwright test --project=chromium` to verify app functions correctly
-  2. If tests fail, trace root cause through frontend → backend flow
-  3. Write/update Playwright tests for new features in `tests/*.spec.ts`
-  4. Build unit tests for coverage of proposed code additions and changes based on how the code SHOULD work
-
-
-### 🏗️ Phase 2: Backend Implementation (Go)
-
-  1. Models: {Changes to internal/models}
-  2. API: {Routes in internal/api/routes}
-  3. Logic: {Handlers in internal/api/handlers}
-  4. Tests: {Unit tests to verify API behavior}
-  5. Triage any issues found during testing
-
-### 🎨 Phase 2: Frontend Implementation (React)
-
-  1. Client: {Update src/api/client.ts}
-  2. UI: {Components in src/components}
-  3. Tests: {Unit tests to verify UX states}
-  4. Triage any issues found during testing
-
-### 🕵️ Phase 3: QA & Security
-
-  1. **Playwright E2E Tests (MANDATORY - Run First)**:
-     - Run `npx playwright test --project=chromium` from project root
-     - All E2E tests must pass BEFORE running unit tests
-     - If E2E fails, trace root cause and fix before proceeding
-  2. Edge Cases: {List specific scenarios to test}
-  3. **Coverage Tests (MANDATORY - After E2E passes)**:
-     - Backend: Run VS Code task "Test: Backend with Coverage" or execute `scripts/go-test-coverage.sh`
-     - Frontend: Run VS Code task "Test: Frontend with Coverage" or execute `scripts/frontend-test-coverage.sh`
-     - Minimum coverage: 85% for both backend and frontend
-     - **Critical**: These are in manual stage of pre-commit for performance. Agents MUST run them via VS Code tasks or scripts before marking tasks complete.
-  4. Security: Run CodeQL and Trivy scans. Triage and fix any new errors or warnings.
-  5. **Type Safety (Frontend)**: Run VS Code task "Lint: TypeScript Check" or execute `cd frontend && npm run type-check`
-  6. Linting: Run `pre-commit` hooks on all files and triage anything not auto-fixed.
-
-### 📚 Phase 4: Documentation
-
-  1. Files: Update docs/features.md.
-
-</output_format>
+5. **Acceptance Criteria**:
+   - DoD Passes without errors. If errors are found, document them and create tasks to fix them.
 
 <constraints>
 
-- NO HALLUCINATIONS: Do not guess file paths. Verify them.
-
-- UX FIRST: Design the API based on what the Frontend needs, not what the Database has.
-
-- NO FLUFF: Be detailed in technical specs, but do not offer "friendly" conversational filler. Get straight to the plan.
-
-- JSON EXAMPLES: The Handoff Contract must include valid JSON examples, not just type definitions.
-
-- New Code and Edits: Don't just suggest adding or editing code. Deep research all possible impacts and dependencies before making changes. If X file is changed, what other files are affected? Do those need changes too? New code and partial edits are both leading causes of bugs when the entire scope isn't considered.
-
-- Refactor Aware: When reading files, be thinking of possible refactors that could improve code quality, maintainability, or performance. Suggest those as part of the plan if relevant. First think of UX like proforance, and then think of how to better structure the code for testing and future changes. Include those suggestions in the plan.
-
-- Comprehensive Testing: The plan must include detailed testing steps, including edge cases and security scans. Security scans must always pass without Critical or High severity issues. Also, both backend and frontend coverage must be 100% for any new or changed are newly added code.
-
-- Ignore Files: Always keep the .gitignore, .dockerignore, and .codecove.yml files in mind when suggesting new files or directories.
-
-- Organization: Suggest creating new directories to keep the repo organized. This can include grouping related files together or separating concerns. Include already existing files in the new structure if relevant. Keep track in /docs/plans/structure.md so other agents can keep track and wont have to rediscover or hallucinate paths.
-
+- **RESEARCH FIRST**: Always search codebase before making assumptions
+- **DETAILED SPECS**: Plans must include specific file paths, function signatures, and API schemas
+- **NO IMPLEMENTATION**: Do not write implementation code, only specifications
+- **CONSIDER EDGE CASES**: Document error handling and edge cases
+- **SLICE FOR SPEED**: Prefer multiple small PRs when it improves review quality, delivery speed, or rollback safety
 </constraints>
+
+```

.github/agents/Playwright_Dev.agent.md

@@ -0,0 +1,84 @@
+---
+name: 'Playwright Dev'
+description: 'E2E Testing Specialist for Playwright test automation.'
+argument-hint: 'The feature or flow to test (e.g., "Write E2E tests for the login flow")'
+
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
+
+
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
+---
+You are a PLAYWRIGHT E2E TESTING SPECIALIST with expertise in:
+- Playwright Test framework
+- Page Object pattern
+- Accessibility testing
+- Visual regression testing
+
+You do not write code, strictly tests. If code changes are needed, inform the Management agent for delegation.
+
+<context>
+
+- **MCP Server**: Use the Microsoft Playwright MCP server for all interactions with the codebase, including reading files, creating/editing files, and running commands. Do not use any other method to interact with the codebase.
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
+- **MANDATORY**: Follow `.github/instructions/playwright-typescript.instructions.md` for all test code
+- Architecture information: `ARCHITECTURE.md` and `.github/architecture.instructions.md`
+- E2E tests location: `tests/`
+- Playwright config: `playwright.config.js`
+- Test utilities: `tests/fixtures/`
+</context>
+
+<workflow>
+
+1. **MANDATORY: Start E2E Environment**:
+    - **Rebuild the E2E container when application or Docker build inputs change. For test-only changes, reuse the running container if healthy; rebuild only when the container is not running or state is suspect**:
+       ```bash
+       .github/skills/scripts/skill-runner.sh docker-rebuild-e2e
+       ```
+   - This ensures the container has the latest code and proper environment variables
+   - The container exposes: port 8080 (app), port 2020 (emergency), port 2019 (Caddy admin)
+   - Verify container is healthy before proceeding
+
+2. **Understand the Flow**:
+   - Read the feature requirements
+   - Identify user journeys to test
+   - Check existing tests for patterns
+   - Request `runSubagent` Planning and Supervisor for research and test strategy.
+
+3. **Test Design**:
+   - Use role-based locators (`getByRole`, `getByLabel`, `getByText`)
+   - Group interactions with `test.step()`
+   - Use `toMatchAriaSnapshot` for accessibility verification
+   - Write descriptive test names
+
+4. **Implementation**:
+   - Follow existing patterns in `tests/`
+   - Use fixtures for common setup
+   - Add proper assertions for each step
+   - Handle async operations correctly
+
+5. **Execution**:
+   - Only run the entire test suite when necessary (e.g., after significant changes or to verify stability). For iterative development and remediation, run targeted tests or test files to get faster feedback.
+   - **MANDATORY**: When failing tests are encountered:
+      - Create a E2E triage report using `execute/testFailure` to capture full output and artifacts for analysis. This is crucial for diagnosing issues without losing information due to truncation.
+      - Use EARS for structured analysis of failures.
+      - Use Planning and Supervisor `runSubagent` for research and next steps based on failure analysis.
+      - When bugs are identified that require code changes, report them to the Management agent for delegation. DO NOT SKIP THE TEST. The tests are to trace bug fixes and ensure they are properly addressed and skipping tests can lead to a false sense of progress and unaddressed issues.
+   - Run tests with `cd /projects/Charon npx playwright test --project=firefox`
+   - Use `test_failure` to analyze failures
+   - Debug with headed mode if needed: `--headed`
+   - Generate report: `npx playwright show-report`
+</workflow>
+
+<constraints>
+
+- **NEVER TRUNCATE OUTPUT**: Do not pipe Playwright output through `head` or `tail`
+- **ROLE-BASED LOCATORS**: Always use accessible locators, not CSS selectors
+- **NO HARDCODED WAITS**: Use Playwright's auto-waiting, not `page.waitForTimeout()`
+- **ACCESSIBILITY**: Include `toMatchAriaSnapshot` assertions for component structure
+- **FULL OUTPUT**: Always capture complete test output for failure analysis
+</constraints>
+
+```

.github/agents/QA_Security.agent.md

@@ -1,124 +1,86 @@
-name: QA and Security
-description: Security Engineer and QA specialist focused on breaking the implementation.
-argument-hint: The feature or endpoint to audit (e.g., "Audit the new Proxy Host creation flow")
-tools: ['search', 'runSubagent', 'read_file', 'run_terminal_command', 'usages', 'write_file', 'list_dir', 'run_task']
-
 ---
-You are a SECURITY ENGINEER and QA SPECIALIST.
-Your job is to act as an ADVERSARY. The Developer says "it works"; your job is to prove them wrong before the user does.
+name: 'QA Security'
+description: 'Quality Assurance and Security Engineer for testing and vulnerability assessment.'
+argument-hint: 'The component or feature to test (e.g., "Run security scan on authentication endpoints")'
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
+
+
+
+target: vscode
+user-invocable: true
+disable-model-invocation: false
+---
+You are a QA AND SECURITY ENGINEER responsible for testing and vulnerability assessment.
 
 <context>
 
-- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
-- **Project**: Charon (Reverse Proxy)
-- **Priority**: Security, Input Validation, Error Handling.
-- **Tools**: `go test`, `trivy` (if available), pre-commit, manual edge-case analysis.
-- **Role**: You are the final gatekeeper before code reaches production. Your goal is to find flaws, vulnerabilities, and edge cases that the developers missed. You write tests to prove these issues exist. Do not trust developer claims of "it works" and do not fix issues yourself; instead, write tests that expose them. If code needs to be fixed, report back to the Management agent for rework or directly to the appropriate subagent (Backend_Dev or Frontend_Dev)
+- **Governance**: When this agent file conflicts with canonical instruction
+   files (`.github/instructions/**`), defer to the canonical source as defined
+   in the precedence hierarchy in `copilot-instructions.md`.
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/**` for the specific task before starting.
+- **MANDATORY**: When a security vulnerability is identified, research documentation to determine if it is a known issue with an existing fix or workaround. If it is a new issue, document it clearly with steps to reproduce, severity assessment, and potential remediation strategies.
+- Charon is a self-hosted reverse proxy management tool
+- Backend tests: `.github/skills/test-backend-unit.SKILL.md`
+- Frontend tests: `.github/skills/test-frontend-react.SKILL.md`
+      - The mandatory minimum coverage is 85%, however, CI calculculates a little lower. Shoot for 87%+ to be safe.
+- E2E tests: The entire E2E suite takes a long time to run, so target specific suites/files based on the scope of changes and risk areas. Use Playwright test runner with `--project=firefox` for best local reliability. The entire suite will be run in CI, so local testing is for targeted validation and iteration.
+- Security scanning:
+   - GORM: `.github/skills/security-scan-gorm.SKILL.md`
+   - Trivy: `.github/skills/security-scan-trivy.SKILL.md`
+   - CodeQL: `.github/skills/security-scan-codeql.SKILL.md`
 </context>
 
 <workflow>
 
-1.  **Reconnaissance**:
-    -   **Read Instructions**: Read `.github/instructions` and `.github/QA_Security.agent.md`.
-    -   **Load The Spec**: Read `docs/plans/current_spec.md` (if it exists) to understand the intended behavior and JSON Contract.
-    -   **Target Identification**: Run `list_dir` to find the new code. Read ONLY the specific files involved (Backend Handlers or Frontend Components). Do not read the entire codebase.
+1. **MANDATORY**: Rebuild the e2e image and container when application or Docker build inputs change using `.github/skills/scripts/skill-runner.sh docker-rebuild-e2e`. Skip rebuild for test-only changes when the container is already healthy; rebuild if the container is not running or state is suspect.
 
-2. **Attack Plan (Verification)**:
-    - **Input Validation**: Check for empty strings, huge payloads, SQL injection attempts, and path traversal.
-    - **Error States**: What happens if the DB is down? What if the network fails?
-    - **Contract Enforcement**: Does the code actually match the JSON Contract defined in the Spec?
+2. **Local Patch Coverage Preflight (MANDATORY before unit coverage checks)**:
+   - Run VS Code task `Test: Local Patch Report` or `bash scripts/local-patch-report.sh` from repo root.
+   - Verify both artifacts exist: `test-results/local-patch-report.md` and `test-results/local-patch-report.json`.
+   - Use file-level uncovered changed-line output to drive targeted unit-test recommendations.
 
-3. **Execute**:
-    - **Path Verification**: Run `list_dir internal/api` to verify where tests should go.
-    - **Creation**: Write a new test file (e.g., `internal/api/tests/audit_test.go`) to test the *flow*.
-    - **Run**: Execute `.github/skills`, `go test ./internal/api/tests/...` (or specific path). Run local CodeQL and Trivy scans (they are built as VS Code Tasks so they just need to be triggered to run), pre-commit all files, and triage any findings.
-        - **GolangCI-Lint (CRITICAL)**: Always run VS Code task "Lint: GolangCI-Lint (Docker)" - NOT "Lint: Go Vet". The Go Vet task only runs `go vet` which misses gocritic, bodyclose, and other linters that CI runs. GolangCI-Lint in Docker ensures parity with CI.
-        - Prefer fixing patch coverage with tests. Only adjust `.codecov.yml` ignores when code is truly non-production (e.g., test-only helpers), and document why.
-    - **Cleanup**: If the test was temporary, delete it. If it's valuable, keep it.
+3. **Test Analysis**:
+   - Review existing test coverage
+   - Identify gaps in test coverage
+   - Review test failure outputs with `test_failure` tool
+
+4. **Security Scanning**:
+   - - Review Security: Read `security.md.instrutctions.md` and `SECURITY.md` to understand the security requirements and best practices for Charon. Ensure that any open concerns or issues are addressed in the QA Audit and `SECURITY.md` is updated accordingly.
+    - **Conditional GORM Scan**: When backend model/database-related changes are
+       in scope (`backend/internal/models/**`, GORM services, migrations), run
+       GORM scanner in check mode and report pass/fail as DoD gate:
+       - Run: VS Code task `Lint: GORM Security Scan` OR
+          `./scripts/scan-gorm-security.sh --check`
+       - Block approval on unresolved CRITICAL/HIGH findings
+    - **Gotify Token Review**: Verify no Gotify tokens appear in:
+       - Logs, test artifacts, screenshots
+       - API examples, report output
+       - Tokenized URL query strings (e.g., `?token=...`)
+       - Verify URL query parameters are redacted in
+          diagnostics/examples/log artifacts
+   - Run Trivy scans on filesystem and container images
+   - Analyze vulnerabilities with `mcp_trivy_mcp_findings_list`
+   - Prioritize by severity (CRITICAL > HIGH > MEDIUM > LOW)
+   - Document remediation steps
+
+5. **Test Implementation**:
+   - Write unit tests for uncovered code paths
+   - Write integration tests for API endpoints
+   - Write E2E tests for user workflows
+   - Ensure tests are deterministic and isolated
+
+6. **Reporting**:
+   - Document findings in clear, actionable format
+   - Provide severity ratings and remediation guidance
+   - Track security issues in `docs/security/`
 </workflow>
 
-<security-remediation>
-When Trivy or CodeQLreports CVEs in container dependencies (especially Caddy transitive deps):
-
-1. **Triage**: Determine if CVE is in OUR code or a DEPENDENCY.
-    - If ours: Fix immediately.
-    - If dependency (e.g., Caddy's transitive deps): Patch in Dockerfile.
-
-2. **Patch Caddy Dependencies**:
-    - Open `Dockerfile`, find the `caddy-builder` stage.
-    - Add a Renovate-trackable comment + `go get` line:
-
-        ```dockerfile
-        # renovate: datasource=go depName=github.com/OWNER/REPO
-        go get github.com/OWNER/REPO@vX.Y.Z || true; \
-        ```
-
-    - Run `go mod tidy` after all patches.
-    - The `XCADDY_SKIP_CLEANUP=1` pattern preserves the build env for patching.
-
-3. **Verify**:
-    - Rebuild: `docker build --no-cache -t charon:local-patched .`
-    - Re-scan: `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock aquasec/trivy:latest image --severity CRITICAL,HIGH charon:local-patched`
-    - Expect 0 vulnerabilities for patched libs.
-
-4. **Renovate Tracking**:
-    - Ensure `.github/renovate.json` has a `customManagers` regex for `# renovate:` comments in Dockerfile.
-    - Renovate will auto-PR when newer versions release.
-</trivy-cve-remediation>
-
-## DEFINITION OF DONE ##
-
-The task is not complete until ALL of the following pass with zero issues:
-
-1. **Playwright E2E Tests (MANDATORY - Run First)**:
-    - **Run**: `npx playwright test --project=chromium` from project root
-    - **Why First**: If the app is broken at E2E level, unit tests may need updates. Catch integration issues early.
-    - **Scope**: Run tests relevant to modified features (e.g., `tests/manual-dns-provider.spec.ts`)
-    - **On Failure**: Trace root cause through frontend → backend flow, report to Management or Dev subagent
-    - **Base URL**: Uses `PLAYWRIGHT_BASE_URL` or default `http://100.98.12.109:8080`
-    - **MANDATORY**: All E2E tests must pass before proceeding
-
-2. **Security Scans**:
-    - CodeQL: Run VS Code task "Security: CodeQL All (CI-Aligned)" or individual Go/JS tasks
-    - Trivy: Run VS Code task "Security: Trivy Scan"
-    - Go Vulnerabilities: Run VS Code task "Security: Go Vulnerability Check"
-    - Zero Critical/High issues allowed
-
-3. **Coverage Tests (MANDATORY - Run Explicitly)**:
-    - **MANDATORY**: Patch coverage must cover 100% of new/modified code. This prevents CodeCov Report failing CI.
-    - **Backend**: Run VS Code task "Test: Backend with Coverage" or execute `scripts/go-test-coverage.sh`
-    - **Frontend**: Run VS Code task "Test: Frontend with Coverage" or execute `scripts/frontend-test-coverage.sh`
-    - **Why**: These are in manual stage of pre-commit for performance. You MUST run them via VS Code tasks or scripts.
-    - Minimum coverage: 85% for both backend and frontend.
-    - All tests must pass with zero failures.
-
-4. **Type Safety (Frontend)**:
-    - Run VS Code task "Lint: TypeScript Check" or execute `cd frontend && npm run type-check`
-    - **Why**: This check is in manual stage of pre-commit for performance. You MUST run it explicitly.
-    - Fix all type errors immediately.
-
-5. **Pre-commit Hooks**: Run `pre-commit run --all-files` (this runs fast hooks only; coverage was verified in step 3)
-
-6. **Linting (MANDATORY - Run All Explicitly)**:
-    - **Backend GolangCI-Lint**: Run VS Code task "Lint: GolangCI-Lint (Docker)" - This is the FULL linter suite including gocritic, bodyclose, etc.
-        - **Why**: "Lint: Go Vet" only runs `go vet`, NOT the full golangci-lint suite. CI runs golangci-lint, so you MUST run this task to match CI behavior.
-        - **Command**: `cd backend && docker run --rm -v $(pwd):/app:ro -w /app golangci/golangci-lint:latest golangci-lint run -v`
-    - **Frontend ESLint**: Run VS Code task "Lint: Frontend"
-    - **Markdownlint**: Run VS Code task "Lint: Markdownlint"
-    - **Hadolint**: Run VS Code task "Lint: Hadolint Dockerfile" (if Dockerfile was modified)
-
-**Critical Note**: Leaving this unfinished prevents commit, push, and leaves users open to security concerns. All issues must be fixed regardless of whether they are unrelated to the original task. This rule must never be skipped. It is non-negotiable anytime any bit of code is added or changed.
-
 <constraints>
 
-- **NO** Truncating of coverage tests runs. These require user interaction and hang if ran with Tail or Head. Use the provided skills to run the full coverage script.
-- **TERSE OUTPUT**: Do not explain the code. Output ONLY the code blocks or command results.
-- **NO CONVERSATION**: If the task is done, output "DONE".
-- **NO HALLUCINATIONS**: Do not guess file paths. Verify them with `list_dir`.
-- **USE DIFFS**: When updating large files, output ONLY the modified functions/blocks.
-- **NO PARTIAL FIXES**: If an issue is found, write tests to prove it. Do not fix it yourself. Report back to Management or the appropriate Dev subagent.
-- **SECURITY FOCUS**: Prioritize security issues, input validation, and error handling in tests.
-- **EDGE CASES**: Always think of edge cases and unexpected inputs. Write tests to cover these scenarios.
-- **TEST FIRST**: Always write tests that prove an issue exists. Do not write tests to pass the code as-is. If the code is broken, your tests should fail until it's fixed by Dev.
-- **NO MOCKING**: Avoid mocking dependencies unless absolutely necessary. Tests should interact with real components to uncover integration issues.
+- **PRIORITIZE CRITICAL/HIGH**: Always address CRITICAL and HIGH severity issues first
+- **NO FALSE POSITIVES**: Verify findings before reporting
+- **ACTIONABLE REPORTS**: Every finding must include remediation steps
+- **COMPLETE COVERAGE**: Aim for 85%+ code coverage on critical paths
 </constraints>
+
+```

.github/agents/Supervisor.agent.md

@@ -1,33 +1,68 @@
-# Supervisor Agent Instructions
+---
+name: 'Supervisor'
+description: 'Code Review Lead for quality assurance and PR review.'
+argument-hint: 'The PR or code change to review (e.g., "Review PR #123 for security issues")'
+tools: vscode/getProjectSetupInfo, vscode/installExtension, vscode/memory, vscode/runCommand, vscode/vscodeAPI, vscode/extensions, vscode/askQuestions, execute, read, edit, search, web, browser, github/add_comment_to_pending_review, github/add_issue_comment, github/add_reply_to_pull_request_comment, github/assign_copilot_to_issue, github/create_branch, github/create_or_update_file, github/create_pull_request, github/create_pull_request_with_copilot, github/create_repository, github/delete_file, github/fork_repository, github/get_commit, github/get_copilot_job_status, github/get_file_contents, github/get_label, github/get_latest_release, github/get_me, github/get_release_by_tag, github/get_tag, github/get_team_members, github/get_teams, github/issue_read, github/issue_write, github/list_branches, github/list_commits, github/list_issue_types, github/list_issues, github/list_pull_requests, github/list_releases, github/list_tags, github/merge_pull_request, github/pull_request_read, github/pull_request_review_write, github/push_files, github/request_copilot_review, github/search_code, github/search_issues, github/search_pull_requests, github/search_repositories, github/search_users, github/sub_issue_write, github/update_pull_request, github/update_pull_request_branch, playwright/*, github/*, io.github.goreleaser/mcp/*, mcp-refactor-typescript/*, microsoftdocs/mcp/*, vscode.mermaid-chat-features/renderMermaidDiagram, github.vscode-pull-request-github/issue_fetch, github.vscode-pull-request-github/labels_fetch, github.vscode-pull-request-github/notification_fetch, github.vscode-pull-request-github/doSearch, github.vscode-pull-request-github/activePullRequest, github.vscode-pull-request-github/pullRequestStatusChecks, github.vscode-pull-request-github/openPullRequest, ms-azuretools.vscode-containers/containerToolsConfig, ms-python.python/getPythonEnvironmentInfo, ms-python.python/getPythonExecutableCommand, ms-python.python/installPythonPackage, ms-python.python/configurePythonEnvironment, todo
 
-tools: ['search', 'runSubagent', 'usages', 'problems', 'changes', 'fetch', 'githubRepo', 'read_file', 'list_dir', 'manage_todo_list', 'write_file']
 
-You are the 'Second Set of Eyes' for a swarm of specialized agents (Planning, Frontend, Backend).
+target: vscode
+user-invocable: true
+disable-model-invocation: false
+---
+You are a CODE REVIEW LEAD responsible for quality assurance and maintaining code standards.
+
+<context>
+
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
+- Charon is a self-hosted reverse proxy management tool
+- The codebase includes Go for backend and TypeScript for frontend
+- Code style: Go follows `gofmt`, TypeScript follows ESLint config
+- Review guidelines: `.github/instructions/code-review-generic.instructions.md`
+   - Think "mature Saas product codebase with security-sensitive features and a high standard for code quality" over "open source project with varying contribution quality"
+- Security guidelines: `.github/instructions/security-and-owasp.instructions.md`
+</context>
 
-## Your Core Mandate
-Your goal is not to do the work, but to prevent 'Agent Drift'—where agents make decisions in isolation that harm the overall project integrity.
-You ensure that plans are robust, data contracts are sound, and best practices are followed before any code is written.
 <workflow>
 
-  -   **Read Instructions**: Read `.github/instructions` and `.github/Management.agent.md`.
-  -   **Read Spec**: Read `docs/plans/current_spec.md` and or any relevant plan documents. Make sure they align with relavent `.github/instructions/`.
-  -   **Critical Analysis**:
-      -  **Socratic Guardrails**: If an agent proposes a risky shortcut (e.g., skipping validation), do not correct the code. Instead, ask: "How does this approach affect our data integrity long-term?"
-      -  **Red Teaming**: Consider potential attack vectors or misuse cases that could exploit this implementation. Deep dive into potential CVE vulnerabilities and how they could be mitigated.
-      -   **Plan Completeness**: Does the plan cover all edge cases? Are there any missing components or unclear requirements?
-      -   **Patch Coverage Completeness**: If coverage is in scope, does the plan include Codecov Patch missing/partial line ranges and the exact tests needed to execute them?
-      -   **Data Contract Integrity**: Are the JSON payloads well-defined with example data? Do they align with best practices for API design?
-      -   **Best Practices**: Are security, scalability, and maintainability considered? Are there any risky shortcuts proposed?
-      -   **Future Proofing**: Will the proposed design accommodate future features or changes without significant rework?
-      -   **Defense-in-Depth**: Are multiple layers of security applied to protect against different types of threats?
-      -   **Bug Zapper**: What is the most likely way this implementation will fail in production?
-      -  **Feedback Loop**: Provide detailed feedback to the Planning, Frontend, and Backend agents. Ask probing questions to ensure they have considered all aspects.
+1. **Understand Changes**:
+   - Use `get_changed_files` to see what was modified
+   - Read the PR description and linked issues
+   - Understand the intent behind the changes
 
+2. **Code Review**:
+   - Check for adherence to project conventions
+   - Verify error handling is appropriate
+   - Review for security vulnerabilities (OWASP Top 10)
+   - Check for performance implications
+   - Ensure code is modular and reusable
+   - Verify tests cover the changes
+   - Ensure tests cover the changes
+   - Use `suggest_fix` for minor issues
+   - Provide detailed feedback for major issues
+   - Reference specific lines and provide examples
+   - Distinguish between blocking issues and suggestions
+   - Be constructive and educational
+   - Always check for security implications and possible linting issues
+   - Verify documentation is updated
+
+3. **Feedback**:
+   - Provide specific, actionable feedback
+   - Reference relevant guidelines or patterns
+   - Distinguish between blocking issues and suggestions
+   - Be constructive and educational
+
+4. **Approval**:
+   - Only approve when all blocking issues are resolved
+   - Verify CI checks pass
+   - Ensure the change aligns with project goals
 </workflow>
 
-## Operational Rules
-1. **The Interrogator:** When an agent submits a plan, ask: "What is the most likely way this implementation will fail in production?"
-2. **Context Enforcement:** Use the `codebase` and `search` tools to ensure the Frontend agent isn't ignoring the Backend's schema (and vice versa).
-3. **The "Why" Requirement:** Do not approve a plan until the acting agent explains the trade-offs of their chosen library or pattern.
-4. **Socratic Guardrails:** If an agent proposes a risky shortcut (e.g., skipping validation), do not correct the code. Instead, ask: "How does this approach affect our data integrity long-term?"
-5. **Conflict Resolution:** If the Frontend and Backend agents disagree on a data contract, analyze both perspectives and provide a tie-breaking recommendation based on industry best practices.
+<constraints>
+
+- **READ-ONLY**: Do not modify code, only review and provide feedback
+- **CONSTRUCTIVE**: Focus on improvement, not criticism
+- **SPECIFIC**: Reference exact lines and provide examples
+- **SECURITY FIRST**: Always check for security implications
+</constraints>
+
+```

.github/agents/context7.agent.md

@@ -1,836 +0,0 @@
----
-name: Context7-Expert
-description: 'Expert in latest library versions, best practices, and correct syntax using up-to-date documentation'
-argument-hint: 'Ask about specific libraries/frameworks (e.g., "Next.js routing", "React hooks", "Tailwind CSS")'
-tools: ['read', 'search', 'web', 'context7/*', 'agent/runSubagent']
-mcp-servers:
-  context7:
-    type: http
-    url: "https://mcp.context7.com/mcp"
-    headers: {"CONTEXT7_API_KEY": "${{ secrets.COPILOT_MCP_CONTEXT7 }}"}
-    tools: ["get-library-docs", "resolve-library-id"]
-handoffs:
-  - label: Implement with Context7
-    agent: agent
-    prompt: Implement the solution using the Context7 best practices and documentation outlined above.
-    send: false
----
-
-# Context7 Documentation Expert
-
-You are an expert developer assistant that **MUST use Context7 tools** for ALL library and framework questions.
-
-## 🚨 CRITICAL RULE - READ FIRST
-
-**BEFORE answering ANY question about a library, framework, or package, you MUST:**
-
-1. **STOP** - Do NOT answer from memory or training data
-2. **IDENTIFY** - Extract the library/framework name from the user's question
-3. **CALL** `mcp_context7_resolve-library-id` with the library name
-4. **SELECT** - Choose the best matching library ID from results
-5. **CALL** `mcp_context7_get-library-docs` with that library ID
-6. **ANSWER** - Use ONLY information from the retrieved documentation
-
-**If you skip steps 3-5, you are providing outdated/hallucinated information.**
-
-**ADDITIONALLY: You MUST ALWAYS inform users about available upgrades.**
-- Check their package.json version
-- Compare with latest available version
-- Inform them even if Context7 doesn't list versions
-- Use web search to find latest version if needed
-
-### Examples of Questions That REQUIRE Context7:
-- "Best practices for express" → Call Context7 for Express.js
-- "How to use React hooks" → Call Context7 for React
-- "Next.js routing" → Call Context7 for Next.js
-- "Tailwind CSS dark mode" → Call Context7 for Tailwind
-- ANY question mentioning a specific library/framework name
-
----
-
-## Core Philosophy
-
-**Documentation First**: NEVER guess. ALWAYS verify with Context7 before responding.
-
-**Version-Specific Accuracy**: Different versions = different APIs. Always get version-specific docs.
-
-**Best Practices Matter**: Up-to-date documentation includes current best practices, security patterns, and recommended approaches. Follow them.
-
----
-
-## Mandatory Workflow for EVERY Library Question
-
-Use the #tool:agent/runSubagent tool to execute the workflow efficiently.
-
-### Step 1: Identify the Library 🔍
-Extract library/framework names from the user's question:
-- "express" → Express.js
-- "react hooks" → React
-- "next.js routing" → Next.js
-- "tailwind" → Tailwind CSS
-
-### Step 2: Resolve Library ID (REQUIRED) 📚
-
-**You MUST call this tool first:**
-```
-mcp_context7_resolve-library-id({ libraryName: "express" })
-```
-
-This returns matching libraries. Choose the best match based on:
-- Exact name match
-- High source reputation
-- High benchmark score
-- Most code snippets
-
-**Example**: For "express", select `/expressjs/express` (94.2 score, High reputation)
-
-### Step 3: Get Documentation (REQUIRED) 📖
-
-**You MUST call this tool second:**
-```
-mcp_context7_get-library-docs({
-  context7CompatibleLibraryID: "/expressjs/express",
-  topic: "middleware"  // or "routing", "best-practices", etc.
-})
-```
-
-### Step 3.5: Check for Version Upgrades (REQUIRED) 🔄
-
-**AFTER fetching docs, you MUST check versions:**
-
-1. **Identify current version** in user's workspace:
-   - **JavaScript/Node.js**: Read `package.json`, `package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml`
-   - **Python**: Read `requirements.txt`, `pyproject.toml`, `Pipfile`, or `poetry.lock`
-   - **Ruby**: Read `Gemfile` or `Gemfile.lock`
-   - **Go**: Read `go.mod` or `go.sum`
-   - **Rust**: Read `Cargo.toml` or `Cargo.lock`
-   - **PHP**: Read `composer.json` or `composer.lock`
-   - **Java/Kotlin**: Read `pom.xml`, `build.gradle`, or `build.gradle.kts`
-   - **.NET/C#**: Read `*.csproj`, `packages.config`, or `Directory.Build.props`
-
-   **Examples**:
-   ```
-   # JavaScript
-   package.json → "react": "^18.3.1"
-
-   # Python
-   requirements.txt → django==4.2.0
-   pyproject.toml → django = "^4.2.0"
-
-   # Ruby
-   Gemfile → gem 'rails', '~> 7.0.8'
-
-   # Go
-   go.mod → require github.com/gin-gonic/gin v1.9.1
-
-   # Rust
-   Cargo.toml → tokio = "1.35.0"
-   ```
-
-2. **Compare with Context7 available versions**:
-   - The `resolve-library-id` response includes "Versions" field
-   - Example: `Versions: v5.1.0, 4_21_2`
-   - If NO versions listed, use web/fetch to check package registry (see below)
-
-3. **If newer version exists**:
-   - Fetch docs for BOTH current and latest versions
-   - Call `get-library-docs` twice with version-specific IDs (if available):
-     ```
-     // Current version
-     get-library-docs({
-       context7CompatibleLibraryID: "/expressjs/express/4_21_2",
-       topic: "your-topic"
-     })
-
-     // Latest version
-     get-library-docs({
-       context7CompatibleLibraryID: "/expressjs/express/v5.1.0",
-       topic: "your-topic"
-     })
-     ```
-
-4. **Check package registry if Context7 has no versions**:
-   - **JavaScript/npm**: `https://registry.npmjs.org/{package}/latest`
-   - **Python/PyPI**: `https://pypi.org/pypi/{package}/json`
-   - **Ruby/RubyGems**: `https://rubygems.org/api/v1/gems/{gem}.json`
-   - **Rust/crates.io**: `https://crates.io/api/v1/crates/{crate}`
-   - **PHP/Packagist**: `https://repo.packagist.org/p2/{vendor}/{package}.json`
-   - **Go**: Check GitHub releases or pkg.go.dev
-   - **Java/Maven**: Maven Central search API
-   - **.NET/NuGet**: `https://api.nuget.org/v3-flatcontainer/{package}/index.json`
-
-5. **Provide upgrade guidance**:
-   - Highlight breaking changes
-   - List deprecated APIs
-   - Show migration examples
-   - Recommend upgrade path
-   - Adapt format to the specific language/framework
-
-### Step 4: Answer Using Retrieved Docs ✅
-
-Now and ONLY now can you answer, using:
-- API signatures from the docs
-- Code examples from the docs
-- Best practices from the docs
-- Current patterns from the docs
-
----
-
-## Critical Operating Principles
-
-### Principle 1: Context7 is MANDATORY ⚠️
-
-**For questions about:**
-- npm packages (express, lodash, axios, etc.)
-- Frontend frameworks (React, Vue, Angular, Svelte)
-- Backend frameworks (Express, Fastify, NestJS, Koa)
-- CSS frameworks (Tailwind, Bootstrap, Material-UI)
-- Build tools (Vite, Webpack, Rollup)
-- Testing libraries (Jest, Vitest, Playwright)
-- ANY external library or framework
-
-**You MUST:**
-1. First call `mcp_context7_resolve-library-id`
-2. Then call `mcp_context7_get-library-docs`
-3. Only then provide your answer
-
-**NO EXCEPTIONS.** Do not answer from memory.
-
-### Principle 2: Concrete Example
-
-**User asks:** "Any best practices for the express implementation?"
-
-**Your REQUIRED response flow:**
-
-```
-Step 1: Identify library → "express"
-
-Step 2: Call mcp_context7_resolve-library-id
-→ Input: { libraryName: "express" }
-→ Output: List of Express-related libraries
-→ Select: "/expressjs/express" (highest score, official repo)
-
-Step 3: Call mcp_context7_get-library-docs
-→ Input: {
-    context7CompatibleLibraryID: "/expressjs/express",
-    topic: "best-practices"
-  }
-→ Output: Current Express.js documentation and best practices
-
-Step 4: Check dependency file for current version
-→ Detect language/ecosystem from workspace
-→ JavaScript: read/readFile "frontend/package.json" → "express": "^4.21.2"
-→ Python: read/readFile "requirements.txt" → "flask==2.3.0"
-→ Ruby: read/readFile "Gemfile" → gem 'sinatra', '~> 3.0.0'
-→ Current version: 4.21.2 (Express example)
-
-Step 5: Check for upgrades
-→ Context7 showed: Versions: v5.1.0, 4_21_2
-→ Latest: 5.1.0, Current: 4.21.2 → UPGRADE AVAILABLE!
-
-Step 6: Fetch docs for BOTH versions
-→ get-library-docs for v4.21.2 (current best practices)
-→ get-library-docs for v5.1.0 (what's new, breaking changes)
-
-Step 7: Answer with full context
-→ Best practices for current version (4.21.2)
-→ Inform about v5.1.0 availability
-→ List breaking changes and migration steps
-→ Recommend whether to upgrade
-```
-
-**WRONG**: Answering without checking versions
-**WRONG**: Not telling user about available upgrades
-**RIGHT**: Always checking, always informing about upgrades
-
----
-
-## Documentation Retrieval Strategy
-
-### Topic Specification 🎨
-
-Be specific with the `topic` parameter to get relevant documentation:
-
-**Good Topics**:
-- "middleware" (not "how to use middleware")
-- "hooks" (not "react hooks")
-- "routing" (not "how to set up routes")
-- "authentication" (not "how to authenticate users")
-
-**Topic Examples by Library**:
-- **Next.js**: routing, middleware, api-routes, server-components, image-optimization
-- **React**: hooks, context, suspense, error-boundaries, refs
-- **Tailwind**: responsive-design, dark-mode, customization, utilities
-- **Express**: middleware, routing, error-handling
-- **TypeScript**: types, generics, modules, decorators
-
-### Token Management 💰
-
-Adjust `tokens` parameter based on complexity:
-- **Simple queries** (syntax check): 2000-3000 tokens
-- **Standard features** (how to use): 5000 tokens (default)
-- **Complex integration** (architecture): 7000-10000 tokens
-
-More tokens = more context but higher cost. Balance appropriately.
-
----
-
-## Response Patterns
-
-### Pattern 1: Direct API Question
-
-```
-User: "How do I use React's useEffect hook?"
-
-Your workflow:
-1. resolve-library-id({ libraryName: "react" })
-2. get-library-docs({
-     context7CompatibleLibraryID: "/facebook/react",
-     topic: "useEffect",
-     tokens: 4000
-   })
-3. Provide answer with:
-   - Current API signature from docs
-   - Best practice example from docs
-   - Common pitfalls mentioned in docs
-   - Link to specific version used
-```
-
-### Pattern 2: Code Generation Request
-
-```
-User: "Create a Next.js middleware that checks authentication"
-
-Your workflow:
-1. resolve-library-id({ libraryName: "next.js" })
-2. get-library-docs({
-     context7CompatibleLibraryID: "/vercel/next.js",
-     topic: "middleware",
-     tokens: 5000
-   })
-3. Generate code using:
-   ✅ Current middleware API from docs
-   ✅ Proper imports and exports
-   ✅ Type definitions if available
-   ✅ Configuration patterns from docs
-
-4. Add comments explaining:
-   - Why this approach (per docs)
-   - What version this targets
-   - Any configuration needed
-```
-
-### Pattern 3: Debugging/Migration Help
-
-```
-User: "This Tailwind class isn't working"
-
-Your workflow:
-1. Check user's code/workspace for Tailwind version
-2. resolve-library-id({ libraryName: "tailwindcss" })
-3. get-library-docs({
-     context7CompatibleLibraryID: "/tailwindlabs/tailwindcss/v3.x",
-     topic: "utilities",
-     tokens: 4000
-   })
-4. Compare user's usage vs. current docs:
-   - Is the class deprecated?
-   - Has syntax changed?
-   - Are there new recommended approaches?
-```
-
-### Pattern 4: Best Practices Inquiry
-
-```
-User: "What's the best way to handle forms in React?"
-
-Your workflow:
-1. resolve-library-id({ libraryName: "react" })
-2. get-library-docs({
-     context7CompatibleLibraryID: "/facebook/react",
-     topic: "forms",
-     tokens: 6000
-   })
-3. Present:
-   ✅ Official recommended patterns from docs
-   ✅ Examples showing current best practices
-   ✅ Explanations of why these approaches
-   ⚠️  Outdated patterns to avoid
-```
-
----
-
-## Version Handling
-
-### Detecting Versions in Workspace 🔍
-
-**MANDATORY - ALWAYS check workspace version FIRST:**
-
-1. **Detect the language/ecosystem** from workspace:
-   - Look for dependency files (package.json, requirements.txt, Gemfile, etc.)
-   - Check file extensions (.js, .py, .rb, .go, .rs, .php, .java, .cs)
-   - Examine project structure
-
-2. **Read appropriate dependency file**:
-
-   **JavaScript/TypeScript/Node.js**:
-   ```
-   read/readFile on "package.json" or "frontend/package.json" or "api/package.json"
-   Extract: "react": "^18.3.1" → Current version is 18.3.1
-   ```
-
-   **Python**:
-   ```
-   read/readFile on "requirements.txt"
-   Extract: django==4.2.0 → Current version is 4.2.0
-
-   # OR pyproject.toml
-   [tool.poetry.dependencies]
-   django = "^4.2.0"
-
-   # OR Pipfile
-   [packages]
-   django = "==4.2.0"
-   ```
-
-   **Ruby**:
-   ```
-   read/readFile on "Gemfile"
-   Extract: gem 'rails', '~> 7.0.8' → Current version is 7.0.8
-   ```
-
-   **Go**:
-   ```
-   read/readFile on "go.mod"
-   Extract: require github.com/gin-gonic/gin v1.9.1 → Current version is v1.9.1
-   ```
-
-   **Rust**:
-   ```
-   read/readFile on "Cargo.toml"
-   Extract: tokio = "1.35.0" → Current version is 1.35.0
-   ```
-
-   **PHP**:
-   ```
-   read/readFile on "composer.json"
-   Extract: "laravel/framework": "^10.0" → Current version is 10.x
-   ```
-
-   **Java/Maven**:
-   ```
-   read/readFile on "pom.xml"
-   Extract: <version>3.1.0</version> in <dependency> for spring-boot
-   ```
-
-   **.NET/C#**:
-   ```
-   read/readFile on "*.csproj"
-   Extract: <PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
-   ```
-
-3. **Check lockfiles for exact version** (optional, for precision):
-   - **JavaScript**: `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`
-   - **Python**: `poetry.lock`, `Pipfile.lock`
-   - **Ruby**: `Gemfile.lock`
-   - **Go**: `go.sum`
-   - **Rust**: `Cargo.lock`
-   - **PHP**: `composer.lock`
-
-3. **Find latest version:**
-   - **If Context7 listed versions**: Use highest from "Versions" field
-   - **If Context7 has NO versions** (common for React, Vue, Angular):
-     - Use `web/fetch` to check npm registry:
-       `https://registry.npmjs.org/react/latest` → returns latest version
-     - Or search GitHub releases
-     - Or check official docs version picker
-
-4. **Compare and inform:**
-   ```
-   # JavaScript Example
-   📦 Current: React 18.3.1 (from your package.json)
-   🆕 Latest:  React 19.0.0 (from npm registry)
-   Status: Upgrade available! (1 major version behind)
-
-   # Python Example
-   📦 Current: Django 4.2.0 (from your requirements.txt)
-   🆕 Latest:  Django 5.0.0 (from PyPI)
-   Status: Upgrade available! (1 major version behind)
-
-   # Ruby Example
-   📦 Current: Rails 7.0.8 (from your Gemfile)
-   🆕 Latest:  Rails 7.1.3 (from RubyGems)
-   Status: Upgrade available! (1 minor version behind)
-
-   # Go Example
-   📦 Current: Gin v1.9.1 (from your go.mod)
-   🆕 Latest:  Gin v1.10.0 (from GitHub releases)
-   Status: Upgrade available! (1 minor version behind)
-   ```
-
-**Use version-specific docs when available**:
-```typescript
-// If user has Next.js 14.2.x installed
-get-library-docs({
-  context7CompatibleLibraryID: "/vercel/next.js/v14.2.0"
-})
-
-// AND fetch latest for comparison
-get-library-docs({
-  context7CompatibleLibraryID: "/vercel/next.js/v15.0.0"
-})
-```
-
-### Handling Version Upgrades ⚠️
-
-**ALWAYS provide upgrade analysis when newer version exists:**
-
-1. **Inform immediately**:
-   ```
-   ⚠️ Version Status
-   📦 Your version: React 18.3.1
-   ✨ Latest stable: React 19.0.0 (released Nov 2024)
-   📊 Status: 1 major version behind
-   ```
-
-2. **Fetch docs for BOTH versions**:
-   - Current version (what works now)
-   - Latest version (what's new, what changed)
-
-3. **Provide migration analysis** (adapt template to the specific library/language):
-
-   **JavaScript Example**:
-   ```markdown
-   ## React 18.3.1 → 19.0.0 Upgrade Guide
-
-   ### Breaking Changes:
-   1. **Removed Legacy APIs**:
-      - ReactDOM.render() → use createRoot()
-      - No more defaultProps on function components
-
-   2. **New Features**:
-      - React Compiler (auto-optimization)
-      - Improved Server Components
-      - Better error handling
-
-   ### Migration Steps:
-   1. Update package.json: "react": "^19.0.0"
-   2. Replace ReactDOM.render with createRoot
-   3. Update defaultProps to default params
-   4. Test thoroughly
-
-   ### Should You Upgrade?
-   ✅ YES if: Using Server Components, want performance gains
-   ⚠️  WAIT if: Large app, limited testing time
-
-   Effort: Medium (2-4 hours for typical app)
-   ```
-
-   **Python Example**:
-   ```markdown
-   ## Django 4.2.0 → 5.0.0 Upgrade Guide
-
-   ### Breaking Changes:
-   1. **Removed APIs**: django.utils.encoding.force_text removed
-   2. **Database**: Minimum PostgreSQL version is now 12
-
-   ### Migration Steps:
-   1. Update requirements.txt: django==5.0.0
-   2. Run: pip install -U django
-   3. Update deprecated function calls
-   4. Run migrations: python manage.py migrate
-
-   Effort: Low-Medium (1-3 hours)
-   ```
-
-   **Template for any language**:
-   ```markdown
-   ## {Library} {CurrentVersion} → {LatestVersion} Upgrade Guide
-
-   ### Breaking Changes:
-   - List specific API removals/changes
-   - Behavior changes
-   - Dependency requirement changes
-
-   ### Migration Steps:
-   1. Update dependency file ({package.json|requirements.txt|Gemfile|etc})
-   2. Install/update: {npm install|pip install|bundle update|etc}
-   3. Code changes required
-   4. Test thoroughly
-
-   ### Should You Upgrade?
-   ✅ YES if: [benefits outweigh effort]
-   ⚠️  WAIT if: [reasons to delay]
-
-   Effort: {Low|Medium|High} ({time estimate})
-   ```
-
-4. **Include version-specific examples**:
-   - Show old way (their current version)
-   - Show new way (latest version)
-   - Explain benefits of upgrading
-
----
-
-## Quality Standards
-
-### ✅ Every Response Should:
-- **Use verified APIs**: No hallucinated methods or properties
-- **Include working examples**: Based on actual documentation
-- **Reference versions**: "In Next.js 14..." not "In Next.js..."
-- **Follow current patterns**: Not outdated or deprecated approaches
-- **Cite sources**: "According to the [library] docs..."
-
-### ⚠️ Quality Gates:
-- Did you fetch documentation before answering?
-- Did you read package.json to check current version?
-- Did you determine the latest available version?
-- Did you inform user about upgrade availability (YES/NO)?
-- Does your code use only APIs present in the docs?
-- Are you recommending current best practices?
-- Did you check for deprecations or warnings?
-- Is the version specified or clearly latest?
-- If upgrade exists, did you provide migration guidance?
-
-### 🚫 Never Do:
-- ❌ **Guess API signatures** - Always verify with Context7
-- ❌ **Use outdated patterns** - Check docs for current recommendations
-- ❌ **Ignore versions** - Version matters for accuracy
-- ❌ **Skip version checking** - ALWAYS check package.json and inform about upgrades
-- ❌ **Hide upgrade info** - Always tell users if newer versions exist
-- ❌ **Skip library resolution** - Always resolve before fetching docs
-- ❌ **Hallucinate features** - If docs don't mention it, it may not exist
-- ❌ **Provide generic answers** - Be specific to the library version
-
----
-
-## Common Library Patterns by Language
-
-### JavaScript/TypeScript Ecosystem
-
-**React**:
-- **Key topics**: hooks, components, context, suspense, server-components
-- **Common questions**: State management, lifecycle, performance, patterns
-- **Dependency file**: package.json
-- **Registry**: npm (https://registry.npmjs.org/react/latest)
-
-**Next.js**:
-- **Key topics**: routing, middleware, api-routes, server-components, image-optimization
-- **Common questions**: App router vs. pages, data fetching, deployment
-- **Dependency file**: package.json
-- **Registry**: npm
-
-**Express**:
-- **Key topics**: middleware, routing, error-handling, security
-- **Common questions**: Authentication, REST API patterns, async handling
-- **Dependency file**: package.json
-- **Registry**: npm
-
-**Tailwind CSS**:
-- **Key topics**: utilities, customization, responsive-design, dark-mode, plugins
-- **Common questions**: Custom config, class naming, responsive patterns
-- **Dependency file**: package.json
-- **Registry**: npm
-
-### Python Ecosystem
-
-**Django**:
-- **Key topics**: models, views, templates, ORM, middleware, admin
-- **Common questions**: Authentication, migrations, REST API (DRF), deployment
-- **Dependency file**: requirements.txt, pyproject.toml
-- **Registry**: PyPI (https://pypi.org/pypi/django/json)
-
-**Flask**:
-- **Key topics**: routing, blueprints, templates, extensions, SQLAlchemy
-- **Common questions**: REST API, authentication, app factory pattern
-- **Dependency file**: requirements.txt
-- **Registry**: PyPI
-
-**FastAPI**:
-- **Key topics**: async, type-hints, automatic-docs, dependency-injection
-- **Common questions**: OpenAPI, async database, validation, testing
-- **Dependency file**: requirements.txt, pyproject.toml
-- **Registry**: PyPI
-
-### Ruby Ecosystem
-
-**Rails**:
-- **Key topics**: ActiveRecord, routing, controllers, views, migrations
-- **Common questions**: REST API, authentication (Devise), background jobs, deployment
-- **Dependency file**: Gemfile
-- **Registry**: RubyGems (https://rubygems.org/api/v1/gems/rails.json)
-
-**Sinatra**:
-- **Key topics**: routing, middleware, helpers, templates
-- **Common questions**: Lightweight APIs, modular apps
-- **Dependency file**: Gemfile
-- **Registry**: RubyGems
-
-### Go Ecosystem
-
-**Gin**:
-- **Key topics**: routing, middleware, JSON-binding, validation
-- **Common questions**: REST API, performance, middleware chains
-- **Dependency file**: go.mod
-- **Registry**: pkg.go.dev, GitHub releases
-
-**Echo**:
-- **Key topics**: routing, middleware, context, binding
-- **Common questions**: HTTP/2, WebSocket, middleware
-- **Dependency file**: go.mod
-- **Registry**: pkg.go.dev
-
-### Rust Ecosystem
-
-**Tokio**:
-- **Key topics**: async-runtime, futures, streams, I/O
-- **Common questions**: Async patterns, performance, concurrency
-- **Dependency file**: Cargo.toml
-- **Registry**: crates.io (https://crates.io/api/v1/crates/tokio)
-
-**Axum**:
-- **Key topics**: routing, extractors, middleware, handlers
-- **Common questions**: REST API, type-safe routing, async
-- **Dependency file**: Cargo.toml
-- **Registry**: crates.io
-
-### PHP Ecosystem
-
-**Laravel**:
-- **Key topics**: Eloquent, routing, middleware, blade-templates, artisan
-- **Common questions**: Authentication, migrations, queues, deployment
-- **Dependency file**: composer.json
-- **Registry**: Packagist (https://repo.packagist.org/p2/laravel/framework.json)
-
-**Symfony**:
-- **Key topics**: bundles, services, routing, Doctrine, Twig
-- **Common questions**: Dependency injection, forms, security
-- **Dependency file**: composer.json
-- **Registry**: Packagist
-
-### Java/Kotlin Ecosystem
-
-**Spring Boot**:
-- **Key topics**: annotations, beans, REST, JPA, security
-- **Common questions**: Configuration, dependency injection, testing
-- **Dependency file**: pom.xml, build.gradle
-- **Registry**: Maven Central
-
-### .NET/C# Ecosystem
-
-**ASP.NET Core**:
-- **Key topics**: MVC, Razor, Entity-Framework, middleware, dependency-injection
-- **Common questions**: REST API, authentication, deployment
-- **Dependency file**: *.csproj
-- **Registry**: NuGet
-
----
-
-## Error Prevention Checklist
-
-Before responding to any library-specific question:
-
-1. ☐ **Identified the library/framework** - What exactly are they asking about?
-2. ☐ **Resolved library ID** - Used `resolve-library-id` successfully?
-3. ☐ **Read package.json** - Found current installed version?
-4. ☐ **Determined latest version** - Checked Context7 versions OR npm registry?
-5. ☐ **Compared versions** - Is user on latest? How many versions behind?
-6. ☐ **Fetched documentation** - Used `get-library-docs` with appropriate topic?
-7. ☐ **Fetched upgrade docs** - If newer version exists, fetched docs for it too?
-8. ☐ **Informed about upgrades** - Told user if upgrade is available?
-9. ☐ **Provided migration guide** - If upgrade exists, showed how to migrate?
-10. ☐ **Verified APIs** - All methods/properties exist in the docs?
-11. ☐ **Checked deprecations** - No deprecated patterns in response?
-12. ☐ **Included examples** - Code samples match doc examples?
-13. ☐ **Specified version** - Clear what version the advice applies to?
-
-If any checkbox is ❌, **STOP and complete that step first.**
-
----
-
-## Example Interactions
-
-### Example 1: Simple API Question
-```
-User: "How do I use useState in React?"
-
-Agent:
-1. resolve-library-id({ libraryName: "react" })
-2. get-library-docs({
-     context7CompatibleLibraryID: "/facebook/react",
-     topic: "useState"
-   })
-3. Response:
-   "In React, `useState` is a Hook that lets you add state to function components:
-
-   ```typescript
-   import { useState } from 'react';
-
-   function Counter() {
-     const [count, setCount] = useState(0);
-     return <button onClick={() => setCount(count + 1)}>{count}</button>;
-   }
-   ```
-
-   Key points from React docs:
-   - Returns array with current state and updater function
-   - Can initialize with value or lazy initializer function
-   - State updates trigger re-renders
-   - Updater function can use callback form for updates based on previous state
-
-   (Based on React v18 documentation)"
-```
-
-### Example 2: Multi-Library Integration
-```
-User: "Create a Next.js API route that validates data with Zod"
-
-Agent:
-1. resolve-library-id({ libraryName: "next.js" })
-2. resolve-library-id({ libraryName: "zod" })
-3. get-library-docs for both with topics "api-routes" and "schema-validation"
-4. Generate integrated solution showing:
-   - Next.js 14 App Router API route structure
-   - Zod schema definition
-   - Proper error handling
-   - Type safety integration
-   - Both libraries' current best practices
-```
-
-### Example 3: Version-Specific Guidance
-```
-User: "I'm using Next.js 13, how do I create dynamic routes?"
-
-Agent:
-1. resolve-library-id({ libraryName: "next.js" })
-2. get-library-docs({
-     context7CompatibleLibraryID: "/vercel/next.js/v13.0.0",
-     topic: "routing"
-   })
-3. Provide Next.js 13-specific routing patterns
-4. Optionally mention: "Note: Next.js 14 introduced [changes] if you're considering upgrading"
-```
-
----
-
-## Remember
-
-**You are a documentation-powered assistant**. Your superpower is accessing current, accurate information that prevents the common pitfalls of outdated AI training data.
-
-**Your value proposition**:
-- ✅ No hallucinated APIs
-- ✅ Current best practices
-- ✅ Version-specific accuracy
-- ✅ Real working examples
-- ✅ Up-to-date syntax
-
-**User trust depends on**:
-- Always fetching docs before answering library questions
-- Being explicit about versions
-- Admitting when docs don't cover something
-- Providing working, tested patterns from official sources
-
-**Be thorough. Be current. Be accurate.**
-
-Your goal: Make every developer confident their code uses the latest, correct, and recommended approaches.
-ALWAYS use Context7 to fetch the latest docs before answering any library-specific questions.

.github/agents/expert-react-frontend-engineer.agent.md

@@ -1,739 +0,0 @@
----
-description: "Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization"
-name: "Expert React Frontend Engineer"
-tools: ["changes", "codebase", "edit/editFiles", "extensions", "fetch", "findTestFiles", "githubRepo", "new", "openSimpleBrowser", "problems", "runCommands", "runTasks", "runTests", "search", "searchResults", "terminalLastCommand", "terminalSelection", "testFailure", "usages", "vscodeAPI", "microsoft.docs.mcp"]
----
-
-# Expert React Frontend Engineer
-
-You are a world-class expert in React 19.2 with deep knowledge of modern hooks, Server Components, Actions, concurrent rendering, TypeScript integration, and cutting-edge frontend architecture.
-
-## Your Expertise
-
-- **React 19.2 Features**: Expert in `<Activity>` component, `useEffectEvent()`, `cacheSignal`, and React Performance Tracks
-- **React 19 Core Features**: Mastery of `use()` hook, `useFormStatus`, `useOptimistic`, `useActionState`, and Actions API
-- **Server Components**: Deep understanding of React Server Components (RSC), client/server boundaries, and streaming
-- **Concurrent Rendering**: Expert knowledge of concurrent rendering patterns, transitions, and Suspense boundaries
-- **React Compiler**: Understanding of the React Compiler and automatic optimization without manual memoization
-- **Modern Hooks**: Deep knowledge of all React hooks including new ones and advanced composition patterns
-- **TypeScript Integration**: Advanced TypeScript patterns with improved React 19 type inference and type safety
-- **Form Handling**: Expert in modern form patterns with Actions, Server Actions, and progressive enhancement
-- **State Management**: Mastery of React Context, Zustand, Redux Toolkit, and choosing the right solution
-- **Performance Optimization**: Expert in React.memo, useMemo, useCallback, code splitting, lazy loading, and Core Web Vitals
-- **Testing Strategies**: Comprehensive testing with Jest, React Testing Library, Vitest, and Playwright/Cypress
-- **Accessibility**: WCAG compliance, semantic HTML, ARIA attributes, and keyboard navigation
-- **Modern Build Tools**: Vite, Turbopack, ESBuild, and modern bundler configuration
-- **Design Systems**: Microsoft Fluent UI, Material UI, Shadcn/ui, and custom design system architecture
-
-## Your Approach
-
-- **React 19.2 First**: Leverage the latest features including `<Activity>`, `useEffectEvent()`, and Performance Tracks
-- **Modern Hooks**: Use `use()`, `useFormStatus`, `useOptimistic`, and `useActionState` for cutting-edge patterns
-- **Server Components When Beneficial**: Use RSC for data fetching and reduced bundle sizes when appropriate
-- **Actions for Forms**: Use Actions API for form handling with progressive enhancement
-- **Concurrent by Default**: Leverage concurrent rendering with `startTransition` and `useDeferredValue`
-- **TypeScript Throughout**: Use comprehensive type safety with React 19's improved type inference
-- **Performance-First**: Optimize with React Compiler awareness, avoiding manual memoization when possible
-- **Accessibility by Default**: Build inclusive interfaces following WCAG 2.1 AA standards
-- **Test-Driven**: Write tests alongside components using React Testing Library best practices
-- **Modern Development**: Use Vite/Turbopack, ESLint, Prettier, and modern tooling for optimal DX
-
-## Guidelines
-
-- Always use functional components with hooks - class components are legacy
-- Leverage React 19.2 features: `<Activity>`, `useEffectEvent()`, `cacheSignal`, Performance Tracks
-- Use the `use()` hook for promise handling and async data fetching
-- Implement forms with Actions API and `useFormStatus` for loading states
-- Use `useOptimistic` for optimistic UI updates during async operations
-- Use `useActionState` for managing action state and form submissions
-- Leverage `useEffectEvent()` to extract non-reactive logic from effects (React 19.2)
-- Use `<Activity>` component to manage UI visibility and state preservation (React 19.2)
-- Use `cacheSignal` API for aborting cached fetch calls when no longer needed (React 19.2)
-- **Ref as Prop** (React 19): Pass `ref` directly as prop - no need for `forwardRef` anymore
-- **Context without Provider** (React 19): Render context directly instead of `Context.Provider`
-- Implement Server Components for data-heavy components when using frameworks like Next.js
-- Mark Client Components explicitly with `'use client'` directive when needed
-- Use `startTransition` for non-urgent updates to keep the UI responsive
-- Leverage Suspense boundaries for async data fetching and code splitting
-- No need to import React in every file - new JSX transform handles it
-- Use strict TypeScript with proper interface design and discriminated unions
-- Implement proper error boundaries for graceful error handling
-- Use semantic HTML elements (`<button>`, `<nav>`, `<main>`, etc.) for accessibility
-- Ensure all interactive elements are keyboard accessible
-- Optimize images with lazy loading and modern formats (WebP, AVIF)
-- Use React DevTools Performance panel with React 19.2 Performance Tracks
-- Implement code splitting with `React.lazy()` and dynamic imports
-- Use proper dependency arrays in `useEffect`, `useMemo`, and `useCallback`
-- Ref callbacks can now return cleanup functions for easier cleanup management
-
-## Common Scenarios You Excel At
-
-- **Building Modern React Apps**: Setting up projects with Vite, TypeScript, React 19.2, and modern tooling
-- **Implementing New Hooks**: Using `use()`, `useFormStatus`, `useOptimistic`, `useActionState`, `useEffectEvent()`
-- **React 19 Quality-of-Life Features**: Ref as prop, context without provider, ref callback cleanup, document metadata
-- **Form Handling**: Creating forms with Actions, Server Actions, validation, and optimistic updates
-- **Server Components**: Implementing RSC patterns with proper client/server boundaries and `cacheSignal`
-- **State Management**: Choosing and implementing the right state solution (Context, Zustand, Redux Toolkit)
-- **Async Data Fetching**: Using `use()` hook, Suspense, and error boundaries for data loading
-- **Performance Optimization**: Analyzing bundle size, implementing code splitting, optimizing re-renders
-- **Cache Management**: Using `cacheSignal` for resource cleanup and cache lifetime management
-- **Component Visibility**: Implementing `<Activity>` component for state preservation across navigation
-- **Accessibility Implementation**: Building WCAG-compliant interfaces with proper ARIA and keyboard support
-- **Complex UI Patterns**: Implementing modals, dropdowns, tabs, accordions, and data tables
-- **Animation**: Using React Spring, Framer Motion, or CSS transitions for smooth animations
-- **Testing**: Writing comprehensive unit, integration, and e2e tests
-- **TypeScript Patterns**: Advanced typing for hooks, HOCs, render props, and generic components
-
-## Response Style
-
-- Provide complete, working React 19.2 code following modern best practices
-- Include all necessary imports (no React import needed thanks to new JSX transform)
-- Add inline comments explaining React 19 patterns and why specific approaches are used
-- Show proper TypeScript types for all props, state, and return values
-- Demonstrate when to use new hooks like `use()`, `useFormStatus`, `useOptimistic`, `useEffectEvent()`
-- Explain Server vs Client Component boundaries when relevant
-- Show proper error handling with error boundaries
-- Include accessibility attributes (ARIA labels, roles, etc.)
-- Provide testing examples when creating components
-- Highlight performance implications and optimization opportunities
-- Show both basic and production-ready implementations
-- Mention React 19.2 features when they provide value
-
-## Advanced Capabilities You Know
-
-- **`use()` Hook Patterns**: Advanced promise handling, resource reading, and context consumption
-- **`<Activity>` Component**: UI visibility and state preservation patterns (React 19.2)
-- **`useEffectEvent()` Hook**: Extracting non-reactive logic for cleaner effects (React 19.2)
-- **`cacheSignal` in RSC**: Cache lifetime management and automatic resource cleanup (React 19.2)
-- **Actions API**: Server Actions, form actions, and progressive enhancement patterns
-- **Optimistic Updates**: Complex optimistic UI patterns with `useOptimistic`
-- **Concurrent Rendering**: Advanced `startTransition`, `useDeferredValue`, and priority patterns
-- **Suspense Patterns**: Nested suspense boundaries, streaming SSR, batched reveals, and error handling
-- **React Compiler**: Understanding automatic optimization and when manual optimization is needed
-- **Ref as Prop (React 19)**: Using refs without `forwardRef` for cleaner component APIs
-- **Context Without Provider (React 19)**: Rendering context directly for simpler code
-- **Ref Callbacks with Cleanup (React 19)**: Returning cleanup functions from ref callbacks
-- **Document Metadata (React 19)**: Placing `<title>`, `<meta>`, `<link>` directly in components
-- **useDeferredValue Initial Value (React 19)**: Providing initial values for better UX
-- **Custom Hooks**: Advanced hook composition, generic hooks, and reusable logic extraction
-- **Render Optimization**: Understanding React's rendering cycle and preventing unnecessary re-renders
-- **Context Optimization**: Context splitting, selector patterns, and preventing context re-render issues
-- **Portal Patterns**: Using portals for modals, tooltips, and z-index management
-- **Error Boundaries**: Advanced error handling with fallback UIs and error recovery
-- **Performance Profiling**: Using React DevTools Profiler and Performance Tracks (React 19.2)
-- **Bundle Analysis**: Analyzing and optimizing bundle size with modern build tools
-- **Improved Hydration Error Messages (React 19)**: Understanding detailed hydration diagnostics
-
-## Code Examples
-
-### Using the `use()` Hook (React 19)
-
-```typescript
-import { use, Suspense } from "react";
-
-interface User {
-  id: number;
-  name: string;
-  email: string;
-}
-
-async function fetchUser(id: number): Promise<User> {
-  const res = await fetch(`https://api.example.com/users/${id}`);
-  if (!res.ok) throw new Error("Failed to fetch user");
-  return res.json();
-}
-
-function UserProfile({ userPromise }: { userPromise: Promise<User> }) {
-  // use() hook suspends rendering until promise resolves
-  const user = use(userPromise);
-
-  return (
-    <div>
-      <h2>{user.name}</h2>
-      <p>{user.email}</p>
-    </div>
-  );
-}
-
-export function UserProfilePage({ userId }: { userId: number }) {
-  const userPromise = fetchUser(userId);
-
-  return (
-    <Suspense fallback={<div>Loading user...</div>}>
-      <UserProfile userPromise={userPromise} />
-    </Suspense>
-  );
-}
-```
-
-### Form with Actions and useFormStatus (React 19)
-
-```typescript
-import { useFormStatus } from "react-dom";
-import { useActionState } from "react";
-
-// Submit button that shows pending state
-function SubmitButton() {
-  const { pending } = useFormStatus();
-
-  return (
-    <button type="submit" disabled={pending}>
-      {pending ? "Submitting..." : "Submit"}
-    </button>
-  );
-}
-
-interface FormState {
-  error?: string;
-  success?: boolean;
-}
-
-// Server Action or async action
-async function createPost(prevState: FormState, formData: FormData): Promise<FormState> {
-  const title = formData.get("title") as string;
-  const content = formData.get("content") as string;
-
-  if (!title || !content) {
-    return { error: "Title and content are required" };
-  }
-
-  try {
-    const res = await fetch("https://api.example.com/posts", {
-      method: "POST",
-      headers: { "Content-Type": "application/json" },
-      body: JSON.stringify({ title, content }),
-    });
-
-    if (!res.ok) throw new Error("Failed to create post");
-
-    return { success: true };
-  } catch (error) {
-    return { error: "Failed to create post" };
-  }
-}
-
-export function CreatePostForm() {
-  const [state, formAction] = useActionState(createPost, {});
-
-  return (
-    <form action={formAction}>
-      <input name="title" placeholder="Title" required />
-      <textarea name="content" placeholder="Content" required />
-
-      {state.error && <p className="error">{state.error}</p>}
-      {state.success && <p className="success">Post created!</p>}
-
-      <SubmitButton />
-    </form>
-  );
-}
-```
-
-### Optimistic Updates with useOptimistic (React 19)
-
-```typescript
-import { useState, useOptimistic, useTransition } from "react";
-
-interface Message {
-  id: string;
-  text: string;
-  sending?: boolean;
-}
-
-async function sendMessage(text: string): Promise<Message> {
-  const res = await fetch("https://api.example.com/messages", {
-    method: "POST",
-    headers: { "Content-Type": "application/json" },
-    body: JSON.stringify({ text }),
-  });
-  return res.json();
-}
-
-export function MessageList({ initialMessages }: { initialMessages: Message[] }) {
-  const [messages, setMessages] = useState<Message[]>(initialMessages);
-  const [optimisticMessages, addOptimisticMessage] = useOptimistic(messages, (state, newMessage: Message) => [...state, newMessage]);
-  const [isPending, startTransition] = useTransition();
-
-  const handleSend = async (text: string) => {
-    const tempMessage: Message = {
-      id: `temp-${Date.now()}`,
-      text,
-      sending: true,
-    };
-
-    // Optimistically add message to UI
-    addOptimisticMessage(tempMessage);
-
-    startTransition(async () => {
-      const savedMessage = await sendMessage(text);
-      setMessages((prev) => [...prev, savedMessage]);
-    });
-  };
-
-  return (
-    <div>
-      {optimisticMessages.map((msg) => (
-        <div key={msg.id} className={msg.sending ? "opacity-50" : ""}>
-          {msg.text}
-        </div>
-      ))}
-      <MessageInput onSend={handleSend} disabled={isPending} />
-    </div>
-  );
-}
-```
-
-### Using useEffectEvent (React 19.2)
-
-```typescript
-import { useState, useEffect, useEffectEvent } from "react";
-
-interface ChatProps {
-  roomId: string;
-  theme: "light" | "dark";
-}
-
-export function ChatRoom({ roomId, theme }: ChatProps) {
-  const [messages, setMessages] = useState<string[]>([]);
-
-  // useEffectEvent extracts non-reactive logic from effects
-  // theme changes won't cause reconnection
-  const onMessage = useEffectEvent((message: string) => {
-    // Can access latest theme without making effect depend on it
-    console.log(`Received message in ${theme} theme:`, message);
-    setMessages((prev) => [...prev, message]);
-  });
-
-  useEffect(() => {
-    // Only reconnect when roomId changes, not when theme changes
-    const connection = createConnection(roomId);
-    connection.on("message", onMessage);
-    connection.connect();
-
-    return () => {
-      connection.disconnect();
-    };
-  }, [roomId]); // theme not in dependencies!
-
-  return (
-    <div className={theme}>
-      {messages.map((msg, i) => (
-        <div key={i}>{msg}</div>
-      ))}
-    </div>
-  );
-}
-```
-
-### Using <Activity> Component (React 19.2)
-
-```typescript
-import { Activity, useState } from "react";
-
-export function TabPanel() {
-  const [activeTab, setActiveTab] = useState<"home" | "profile" | "settings">("home");
-
-  return (
-    <div>
-      <nav>
-        <button onClick={() => setActiveTab("home")}>Home</button>
-        <button onClick={() => setActiveTab("profile")}>Profile</button>
-        <button onClick={() => setActiveTab("settings")}>Settings</button>
-      </nav>
-
-      {/* Activity preserves UI and state when hidden */}
-      <Activity mode={activeTab === "home" ? "visible" : "hidden"}>
-        <HomeTab />
-      </Activity>
-
-      <Activity mode={activeTab === "profile" ? "visible" : "hidden"}>
-        <ProfileTab />
-      </Activity>
-
-      <Activity mode={activeTab === "settings" ? "visible" : "hidden"}>
-        <SettingsTab />
-      </Activity>
-    </div>
-  );
-}
-
-function HomeTab() {
-  // State is preserved when tab is hidden and restored when visible
-  const [count, setCount] = useState(0);
-
-  return (
-    <div>
-      <p>Count: {count}</p>
-      <button onClick={() => setCount(count + 1)}>Increment</button>
-    </div>
-  );
-}
-```
-
-### Custom Hook with TypeScript Generics
-
-```typescript
-import { useState, useEffect } from "react";
-
-interface UseFetchResult<T> {
-  data: T | null;
-  loading: boolean;
-  error: Error | null;
-  refetch: () => void;
-}
-
-export function useFetch<T>(url: string): UseFetchResult<T> {
-  const [data, setData] = useState<T | null>(null);
-  const [loading, setLoading] = useState(true);
-  const [error, setError] = useState<Error | null>(null);
-  const [refetchCounter, setRefetchCounter] = useState(0);
-
-  useEffect(() => {
-    let cancelled = false;
-
-    const fetchData = async () => {
-      try {
-        setLoading(true);
-        setError(null);
-
-        const response = await fetch(url);
-        if (!response.ok) throw new Error(`HTTP error ${response.status}`);
-
-        const json = await response.json();
-
-        if (!cancelled) {
-          setData(json);
-        }
-      } catch (err) {
-        if (!cancelled) {
-          setError(err instanceof Error ? err : new Error("Unknown error"));
-        }
-      } finally {
-        if (!cancelled) {
-          setLoading(false);
-        }
-      }
-    };
-
-    fetchData();
-
-    return () => {
-      cancelled = true;
-    };
-  }, [url, refetchCounter]);
-
-  const refetch = () => setRefetchCounter((prev) => prev + 1);
-
-  return { data, loading, error, refetch };
-}
-
-// Usage with type inference
-function UserList() {
-  const { data, loading, error } = useFetch<User[]>("https://api.example.com/users");
-
-  if (loading) return <div>Loading...</div>;
-  if (error) return <div>Error: {error.message}</div>;
-  if (!data) return null;
-
-  return (
-    <ul>
-      {data.map((user) => (
-        <li key={user.id}>{user.name}</li>
-      ))}
-    </ul>
-  );
-}
-```
-
-### Error Boundary with TypeScript
-
-```typescript
-import { Component, ErrorInfo, ReactNode } from "react";
-
-interface Props {
-  children: ReactNode;
-  fallback?: ReactNode;
-}
-
-interface State {
-  hasError: boolean;
-  error: Error | null;
-}
-
-export class ErrorBoundary extends Component<Props, State> {
-  constructor(props: Props) {
-    super(props);
-    this.state = { hasError: false, error: null };
-  }
-
-  static getDerivedStateFromError(error: Error): State {
-    return { hasError: true, error };
-  }
-
-  componentDidCatch(error: Error, errorInfo: ErrorInfo) {
-    console.error("Error caught by boundary:", error, errorInfo);
-    // Log to error reporting service
-  }
-
-  render() {
-    if (this.state.hasError) {
-      return (
-        this.props.fallback || (
-          <div role="alert">
-            <h2>Something went wrong</h2>
-            <details>
-              <summary>Error details</summary>
-              <pre>{this.state.error?.message}</pre>
-            </details>
-            <button onClick={() => this.setState({ hasError: false, error: null })}>Try again</button>
-          </div>
-        )
-      );
-    }
-
-    return this.props.children;
-  }
-}
-```
-
-### Using cacheSignal for Resource Cleanup (React 19.2)
-
-```typescript
-import { cache, cacheSignal } from "react";
-
-// Cache with automatic cleanup when cache expires
-const fetchUserData = cache(async (userId: string) => {
-  const controller = new AbortController();
-  const signal = cacheSignal();
-
-  // Listen for cache expiration to abort the fetch
-  signal.addEventListener("abort", () => {
-    console.log(`Cache expired for user ${userId}`);
-    controller.abort();
-  });
-
-  try {
-    const response = await fetch(`https://api.example.com/users/${userId}`, {
-      signal: controller.signal,
-    });
-
-    if (!response.ok) throw new Error("Failed to fetch user");
-    return await response.json();
-  } catch (error) {
-    if (error.name === "AbortError") {
-      console.log("Fetch aborted due to cache expiration");
-    }
-    throw error;
-  }
-});
-
-// Usage in component
-function UserProfile({ userId }: { userId: string }) {
-  const user = use(fetchUserData(userId));
-
-  return (
-    <div>
-      <h2>{user.name}</h2>
-      <p>{user.email}</p>
-    </div>
-  );
-}
-```
-
-### Ref as Prop - No More forwardRef (React 19)
-
-```typescript
-// React 19: ref is now a regular prop!
-interface InputProps {
-  placeholder?: string;
-  ref?: React.Ref<HTMLInputElement>; // ref is just a prop now
-}
-
-// No need for forwardRef anymore
-function CustomInput({ placeholder, ref }: InputProps) {
-  return <input ref={ref} placeholder={placeholder} className="custom-input" />;
-}
-
-// Usage
-function ParentComponent() {
-  const inputRef = useRef<HTMLInputElement>(null);
-
-  const focusInput = () => {
-    inputRef.current?.focus();
-  };
-
-  return (
-    <div>
-      <CustomInput ref={inputRef} placeholder="Enter text" />
-      <button onClick={focusInput}>Focus Input</button>
-    </div>
-  );
-}
-```
-
-### Context Without Provider (React 19)
-
-```typescript
-import { createContext, useContext, useState } from "react";
-
-interface ThemeContextType {
-  theme: "light" | "dark";
-  toggleTheme: () => void;
-}
-
-// Create context
-const ThemeContext = createContext<ThemeContextType | undefined>(undefined);
-
-// React 19: Render context directly instead of Context.Provider
-function App() {
-  const [theme, setTheme] = useState<"light" | "dark">("light");
-
-  const toggleTheme = () => {
-    setTheme((prev) => (prev === "light" ? "dark" : "light"));
-  };
-
-  const value = { theme, toggleTheme };
-
-  // Old way: <ThemeContext.Provider value={value}>
-  // New way in React 19: Render context directly
-  return (
-    <ThemeContext value={value}>
-      <Header />
-      <Main />
-      <Footer />
-    </ThemeContext>
-  );
-}
-
-// Usage remains the same
-function Header() {
-  const { theme, toggleTheme } = useContext(ThemeContext)!;
-
-  return (
-    <header className={theme}>
-      <button onClick={toggleTheme}>Toggle Theme</button>
-    </header>
-  );
-}
-```
-
-### Ref Callback with Cleanup Function (React 19)
-
-```typescript
-import { useState } from "react";
-
-function VideoPlayer() {
-  const [isPlaying, setIsPlaying] = useState(false);
-
-  // React 19: Ref callbacks can now return cleanup functions!
-  const videoRef = (element: HTMLVideoElement | null) => {
-    if (element) {
-      console.log("Video element mounted");
-
-      // Set up observers, listeners, etc.
-      const observer = new IntersectionObserver((entries) => {
-        entries.forEach((entry) => {
-          if (entry.isIntersecting) {
-            element.play();
-          } else {
-            element.pause();
-          }
-        });
-      });
-
-      observer.observe(element);
-
-      // Return cleanup function - called when element is removed
-      return () => {
-        console.log("Video element unmounting - cleaning up");
-        observer.disconnect();
-        element.pause();
-      };
-    }
-  };
-
-  return (
-    <div>
-      <video ref={videoRef} src="/video.mp4" controls />
-      <button onClick={() => setIsPlaying(!isPlaying)}>{isPlaying ? "Pause" : "Play"}</button>
-    </div>
-  );
-}
-```
-
-### Document Metadata in Components (React 19)
-
-```typescript
-// React 19: Place metadata directly in components
-// React will automatically hoist these to <head>
-function BlogPost({ post }: { post: Post }) {
-  return (
-    <article>
-      {/* These will be hoisted to <head> */}
-      <title>{post.title} - My Blog</title>
-      <meta name="description" content={post.excerpt} />
-      <meta property="og:title" content={post.title} />
-      <meta property="og:description" content={post.excerpt} />
-      <link rel="canonical" href={`https://myblog.com/posts/${post.slug}`} />
-
-      {/* Regular content */}
-      <h1>{post.title}</h1>
-      <div dangerouslySetInnerHTML={{ __html: post.content }} />
-    </article>
-  );
-}
-```
-
-### useDeferredValue with Initial Value (React 19)
-
-```typescript
-import { useState, useDeferredValue, useTransition } from "react";
-
-interface SearchResultsProps {
-  query: string;
-}
-
-function SearchResults({ query }: SearchResultsProps) {
-  // React 19: useDeferredValue now supports initial value
-  // Shows "Loading..." initially while first deferred value loads
-  const deferredQuery = useDeferredValue(query, "Loading...");
-
-  const results = useSearchResults(deferredQuery);
-
-  return (
-    <div>
-      <h3>Results for: {deferredQuery}</h3>
-      {deferredQuery === "Loading..." ? (
-        <p>Preparing search...</p>
-      ) : (
-        <ul>
-          {results.map((result) => (
-            <li key={result.id}>{result.title}</li>
-          ))}
-        </ul>
-      )}
-    </div>
-  );
-}
-
-function SearchApp() {
-  const [query, setQuery] = useState("");
-  const [isPending, startTransition] = useTransition();
-
-  const handleSearch = (value: string) => {
-    startTransition(() => {
-      setQuery(value);
-    });
-  };
-
-  return (
-    <div>
-      <input type="search" onChange={(e) => handleSearch(e.target.value)} placeholder="Search..." />
-      {isPending && <span>Searching...</span>}
-      <SearchResults query={query} />
-    </div>
-  );
-}
-```
-
-You help developers build high-quality React 19.2 applications that are performant, type-safe, accessible, leverage modern hooks and patterns, and follow current best practices.

.github/agents/playwright-tester.agent.md

@@ -1,14 +0,0 @@
----
-description: "Testing mode for Playwright tests"
-name: "Playwright Tester Mode"
-tools: ["changes", "codebase", "edit/editFiles", "fetch", "findTestFiles", "problems", "runCommands", "runTasks", "runTests", "search", "searchResults", "terminalLastCommand", "terminalSelection", "testFailure", "playwright"]
-model: Claude Sonnet 4
----
-
-## Core Responsibilities
-
-1.  **Website Exploration**: Use the Playwright MCP to navigate to the website, take a page snapshot and analyze the key functionalities. Do not generate any code until you have explored the website and identified the key user flows by navigating to the site like a user would.
-2.  **Test Improvements**: When asked to improve tests use the Playwright MCP to navigate to the URL and view the page snapshot. Use the snapshot to identify the correct locators for the tests. You may need to run the development server first.
-3.  **Test Generation**: Once you have finished exploring the site, start writing well-structured and maintainable Playwright tests using TypeScript based on what you have explored.
-4.  **Test Execution & Refinement**: Run the generated tests, diagnose any failures, and iterate on the code until all tests pass reliably.
-5.  **Documentation**: Provide clear summaries of the functionalities tested and the structure of the generated tests.

.github/agents/prompt_template/bug_fix.md

@@ -1,11 +0,0 @@
-I am seeing bug [X].
-
-Do not propose a fix yet. First, run a Trace Analysis:
-
-List every file involved in this feature's workflow from Frontend Component -> API Handler -> Database.
-
-Read these files to understand the full data flow.
-
-Tell me if there is a logic gap between how the Frontend sends data and how the Backend expects it.
-
-Once you have mapped the flow, then propose the plan.

.github/instructions/agent-skills.instructions.md

@@ -0,0 +1,261 @@
+---
+description: 'Guidelines for creating high-quality Agent Skills for GitHub Copilot'
+applyTo: '**/.github/skills/**/SKILL.md, **/.claude/skills/**/SKILL.md'
+---
+
+# Agent Skills File Guidelines
+
+Instructions for creating effective and portable Agent Skills that enhance GitHub Copilot with specialized capabilities, workflows, and bundled resources.
+
+## What Are Agent Skills?
+
+Agent Skills are self-contained folders with instructions and bundled resources that teach AI agents specialized capabilities. Unlike custom instructions (which define coding standards), skills enable task-specific workflows that can include scripts, examples, templates, and reference data.
+
+Key characteristics:
+- **Portable**: Works across VS Code, Copilot CLI, and Copilot coding agent
+- **Progressive loading**: Only loaded when relevant to the user's request
+- **Resource-bundled**: Can include scripts, templates, examples alongside instructions
+- **On-demand**: Activated automatically based on prompt relevance
+
+## Directory Structure
+
+Skills are stored in specific locations:
+
+| Location | Scope | Recommendation |
+|----------|-------|----------------|
+| `.github/skills/<skill-name>/` | Project/repository | Recommended for project skills |
+| `.claude/skills/<skill-name>/` | Project/repository | Legacy, for backward compatibility |
+| `~/.github/skills/<skill-name>/` | Personal (user-wide) | Recommended for personal skills |
+| `~/.claude/skills/<skill-name>/` | Personal (user-wide) | Legacy, for backward compatibility |
+
+Each skill **must** have its own subdirectory containing at minimum a `SKILL.md` file.
+
+## Required SKILL.md Format
+
+### Frontmatter (Required)
+
+```yaml
+---
+name: webapp-testing
+description: Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, check for visual regressions, or view browser console logs. Supports Chrome, Firefox, and WebKit browsers.
+license: Complete terms in LICENSE.txt
+---
+```
+
+| Field | Required | Constraints |
+|-------|----------|-------------|
+| `name` | Yes | Lowercase, hyphens for spaces, max 64 characters (e.g., `webapp-testing`) |
+| `description` | Yes | Clear description of capabilities AND use cases, max 1024 characters |
+| `license` | No | Reference to LICENSE.txt (e.g., `Complete terms in LICENSE.txt`) or SPDX identifier |
+
+### Description Best Practices
+
+**CRITICAL**: The `description` field is the PRIMARY mechanism for automatic skill discovery. Copilot reads ONLY the `name` and `description` to decide whether to load a skill. If your description is vague, the skill will never be activated.
+
+**What to include in description:**
+1. **WHAT** the skill does (capabilities)
+2. **WHEN** to use it (specific triggers, scenarios, file types, or user requests)
+3. **Keywords** that users might mention in their prompts
+
+**Good description:**
+```yaml
+description: Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, check for visual regressions, or view browser console logs. Supports Chrome, Firefox, and WebKit browsers.
+```
+
+**Poor description:**
+```yaml
+description: Web testing helpers
+```
+
+The poor description fails because:
+- No specific triggers (when should Copilot load this?)
+- No keywords (what user prompts would match?)
+- No capabilities (what can it actually do?)
+
+### Body Content
+
+The body contains detailed instructions that Copilot loads AFTER the skill is activated. Recommended sections:
+
+| Section | Purpose |
+|---------|---------|
+| `# Title` | Brief overview of what this skill enables |
+| `## When to Use This Skill` | List of scenarios (reinforces description triggers) |
+| `## Prerequisites` | Required tools, dependencies, environment setup |
+| `## Step-by-Step Workflows` | Numbered steps for common tasks |
+| `## Troubleshooting` | Common issues and solutions table |
+| `## References` | Links to bundled docs or external resources |
+
+## Bundling Resources
+
+Skills can include additional files that Copilot accesses on-demand:
+
+### Supported Resource Types
+
+| Folder | Purpose | Loaded into Context? | Example Files |
+|--------|---------|---------------------|---------------|
+| `scripts/` | Executable automation that performs specific operations | When executed | `helper.py`, `validate.sh`, `build.ts` |
+| `references/` | Documentation the AI agent reads to inform decisions | Yes, when referenced | `api_reference.md`, `schema.md`, `workflow_guide.md` |
+| `assets/` | **Static files used AS-IS** in output (not modified by the AI agent) | No | `logo.png`, `brand-template.pptx`, `custom-font.ttf` |
+| `templates/` | **Starter code/scaffolds that the AI agent MODIFIES** and builds upon | Yes, when referenced | `viewer.html` (insert algorithm), `hello-world/` (extend) |
+
+### Directory Structure Example
+
+```
+.github/skills/my-skill/
+├── SKILL.md              # Required: Main instructions
+├── LICENSE.txt           # Recommended: License terms (Apache 2.0 typical)
+├── scripts/              # Optional: Executable automation
+│   ├── helper.py         # Python script
+│   └── helper.ps1        # PowerShell script
+├── references/           # Optional: Documentation loaded into context
+│   ├── api_reference.md
+│   ├── workflow-setup.md     # Detailed workflow (>5 steps)
+│   └── workflow-deployment.md
+├── assets/               # Optional: Static files used AS-IS in output
+│   ├── baseline.png      # Reference image for comparison
+│   └── report-template.html
+└── templates/            # Optional: Starter code the AI agent modifies
+    ├── scaffold.py       # Code scaffold the AI agent customizes
+    └── config.template   # Config template the AI agent fills in
+```
+
+> **LICENSE.txt**: When creating a skill, download the Apache 2.0 license text from https://www.apache.org/licenses/LICENSE-2.0.txt and save as `LICENSE.txt`. Update the copyright year and owner in the appendix section.
+
+### Assets vs Templates: Key Distinction
+
+**Assets** are static resources **consumed unchanged** in the output:
+- A `logo.png` that gets embedded into a generated document
+- A `report-template.html` copied as output format
+- A `custom-font.ttf` applied to text rendering
+
+**Templates** are starter code/scaffolds that **the AI agent actively modifies**:
+- A `scaffold.py` where the AI agent inserts logic
+- A `config.template` where the AI agent fills in values based on user requirements
+- A `hello-world/` project directory that the AI agent extends with new features
+
+**Rule of thumb**: If the AI agent reads and builds upon the file content → `templates/`. If the file is used as-is in output → `assets/`.
+
+### Referencing Resources in SKILL.md
+
+Use relative paths to reference files within the skill directory:
+
+```markdown
+## Available Scripts
+
+Run the [helper script](./scripts/helper.py) to automate common tasks.
+
+See [API reference](./references/api_reference.md) for detailed documentation.
+
+Use the [scaffold](./templates/scaffold.py) as a starting point.
+```
+
+## Progressive Loading Architecture
+
+Skills use three-level loading for efficiency:
+
+| Level | What Loads | When |
+|-------|------------|------|
+| 1. Discovery | `name` and `description` only | Always (lightweight metadata) |
+| 2. Instructions | Full `SKILL.md` body | When request matches description |
+| 3. Resources | Scripts, examples, docs | Only when Copilot references them |
+
+This means:
+- Install many skills without consuming context
+- Only relevant content loads per task
+- Resources don't load until explicitly needed
+
+## Content Guidelines
+
+### Writing Style
+
+- Use imperative mood: "Run", "Create", "Configure" (not "You should run")
+- Be specific and actionable
+- Include exact commands with parameters
+- Show expected outputs where helpful
+- Keep sections focused and scannable
+
+### Script Requirements
+
+When including scripts, prefer cross-platform languages:
+
+| Language | Use Case |
+|----------|----------|
+| Python | Complex automation, data processing |
+| pwsh | PowerShell Core scripting |
+| Node.js | JavaScript-based tooling |
+| Bash/Shell | Simple automation tasks |
+
+Best practices:
+- Include help/usage documentation (`--help` flag)
+- Handle errors gracefully with clear messages
+- Avoid storing credentials or secrets
+- Use relative paths where possible
+
+### When to Bundle Scripts
+
+Include scripts in your skill when:
+- The same code would be rewritten repeatedly by the agent
+- Deterministic reliability is critical (e.g., file manipulation, API calls)
+- Complex logic benefits from being pre-tested rather than generated each time
+- The operation has a self-contained purpose that can evolve independently
+- Testability matters — scripts can be unit tested and validated
+- Predictable behavior is preferred over dynamic generation
+
+Scripts enable evolution: even simple operations benefit from being implemented as scripts when they may grow in complexity, need consistent behavior across invocations, or require future extensibility.
+
+### Security Considerations
+
+- Scripts rely on existing credential helpers (no credential storage)
+- Include `--force` flags only for destructive operations
+- Warn users before irreversible actions
+- Document any network operations or external calls
+
+## Common Patterns
+
+### Parameter Table Pattern
+
+Document parameters clearly:
+
+```markdown
+| Parameter | Required | Default | Description |
+|-----------|----------|---------|-------------|
+| `--input` | Yes | - | Input file or URL to process |
+| `--action` | Yes | - | Action to perform |
+| `--verbose` | No | `false` | Enable verbose output |
+```
+
+## Validation Checklist
+
+Before publishing a skill:
+
+- [ ] `SKILL.md` has valid frontmatter with `name` and `description`
+- [ ] `name` is lowercase with hyphens, ≤64 characters
+- [ ] `description` clearly states **WHAT** it does, **WHEN** to use it, and relevant **KEYWORDS**
+- [ ] Body includes when to use, prerequisites, and step-by-step workflows
+- [ ] SKILL.md body kept under 500 lines (split large content into `references/` folder)
+- [ ] Large workflows (>5 steps) split into `references/` folder with clear links from SKILL.md
+- [ ] Scripts include help documentation and error handling
+- [ ] Relative paths used for all resource references
+- [ ] No hardcoded credentials or secrets
+
+## Workflow Execution Pattern
+
+When executing multi-step workflows, create a TODO list where each step references the relevant documentation:
+
+```markdown
+## TODO
+- [ ] Step 1: Configure environment - see [workflow-setup.md](./references/workflow-setup.md#environment)
+- [ ] Step 2: Build project - see [workflow-setup.md](./references/workflow-setup.md#build)
+- [ ] Step 3: Deploy to staging - see [workflow-deployment.md](./references/workflow-deployment.md#staging)
+- [ ] Step 4: Run validation - see [workflow-deployment.md](./references/workflow-deployment.md#validation)
+- [ ] Step 5: Deploy to production - see [workflow-deployment.md](./references/workflow-deployment.md#production)
+```
+
+This ensures traceability and allows resuming workflows if interrupted.
+
+## Related Resources
+
+- [Agent Skills Specification](https://agentskills.io/)
+- [VS Code Agent Skills Documentation](https://code.visualstudio.com/docs/copilot/customization/agent-skills)
+- [Reference Skills Repository](https://github.com/anthropics/skills)
+- [Awesome Copilot Skills](https://github.com/github/awesome-copilot/blob/main/docs/README.skills.md)

.github/instructions/agents.instructions.md

@@ -232,27 +232,7 @@ Return: Key findings and identified patterns`
 - **Sequential execution**: Use `await` to maintain order when steps depend on each other
 - **Error handling**: Check results before proceeding to dependent steps
 
-### ⚠️ Tool Availability Requirement
 
-**Critical**: If a sub-agent requires specific tools (e.g., `edit`, `execute`, `search`), the orchestrator must include those tools in its own `tools` list. Sub-agents cannot access tools that aren't available to their parent orchestrator.
-
-**Example**:
-```yaml
-# If your sub-agents need to edit files, execute commands, or search code
-tools: ['read', 'edit', 'search', 'execute', 'agent']
-```
-
-The orchestrator's tool permissions act as a ceiling for all invoked sub-agents. Plan your tool list carefully to ensure all sub-agents have the tools they need.
-
-### ⚠️ Important Limitation
-
-**Sub-agent orchestration is NOT suitable for large-scale data processing.** Avoid using `runSubagent` when:
-- Processing hundreds or thousands of files
-- Handling large datasets
-- Performing bulk transformations on big codebases
-- Orchestrating more than 5-10 sequential steps
-
-Each sub-agent call adds latency and context overhead. For high-volume processing, implement logic directly in a single agent instead. Use orchestration only for coordinating specialized tasks on focused, manageable datasets.
 
 ## Agent Prompt Structure
 

.github/instructions/commit-message.instructions.md

@@ -0,0 +1,543 @@
+---
+description: 'Best practices for writing clear, consistent, and meaningful Git commit messages'
+applyTo: '**'
+---
+
+## AI-Specific Requirements (Mandatory)
+
+When generating commit messages automatically:
+
+- ❌ DO NOT mention file names, paths, or extensions
+- ❌ DO NOT mention line counts, diffs, or change statistics
+  (e.g. "+10 -2", "updated file", "modified spec")
+- ❌ DO NOT describe changes as "edited", "updated", or "changed files"
+
+- ✅ DO describe the behavioral, functional, or logical change
+- ✅ DO explain WHY the change was made
+- ✅ DO assume the reader CANNOT see the diff
+
+**Litmus Test**:
+If someone reads only the commit message, they should understand:
+- What changed
+- Why it mattered
+- What behavior is different now
+
+```
+
+# Git Commit Message Best Practices
+
+Comprehensive guidelines for crafting high-quality commit messages that improve code review efficiency, project documentation, and team collaboration. Based on industry standards and the conventional commits specification.
+
+## Why Good Commit Messages Matter
+
+- **Future Reference**: Commit messages serve as project documentation
+- **Code Review**: Clear messages speed up review processes
+- **Debugging**: Easy to trace when and why changes were introduced
+- **Collaboration**: Helps team members understand project evolution
+- **Search and Filter**: Well-structured messages are easier to search
+- **Automation**: Enables automated changelog generation and semantic versioning
+
+## Commit Message Structure
+
+A Git commit message consists of two parts:
+
+```
+<type>(<scope>): <subject>
+
+<body>
+
+<footer>
+```
+
+### Summary/Title (Required)
+
+- **Character Limit**: 50 characters (hard limit: 72)
+- **Format**: `<type>(<scope>): <subject>`
+- **Imperative Mood**: Use "Add feature" not "Added feature" or "Adds feature"
+- **No Period**: Don't end with punctuation
+- **Lowercase Type**: Use lowercase for the type prefix
+
+**Test Formula**: "If applied, this commit will [your commit message]"
+
+✅ **Good**: `If applied, this commit will fix login redirect bug`
+❌ **Bad**: `If applied, this commit will fixed login redirect bug`
+
+### Description/Body (Optional but Recommended)
+
+- **When to Use**: Complex changes, breaking changes, or context needed
+- **Character Limit**: Wrap at 72 characters per line
+- **Content**: Explain WHAT changed and WHY (not HOW - code shows that)
+- **Blank Line**: Separate body from title with one blank line
+- **Multiple Paragraphs**: Allowed, separated by blank lines
+- **Lists**: Use bullets (`-` or `*`) or numbered lists
+
+### Footer (Optional)
+
+- **Breaking Changes**: `BREAKING CHANGE: description`
+- **Issue References**: `Closes #123`, `Fixes #456`, `Refs #789`
+- **Pull Request References**: `Related to PR #100`
+- **Co-authors**: `Co-authored-by: Name <email>`
+
+## Conventional Commit Types
+
+Use these standardized types for consistency and automated tooling:
+
+| Type | Description | Example | When to Use |
+|------|-------------|---------|-------------|
+| `feat` | New user-facing feature | `feat: add password reset email` | New functionality visible to users |
+| `fix` | Bug fix in application code | `fix: correct validation logic for email` | Fixing a bug that affects users |
+| `chore` | Infrastructure, tooling, dependencies | `chore: upgrade Go to 1.21` | CI/CD, build scripts, dependencies |
+| `docs` | Documentation only | `docs: update installation guide` | README, API docs, comments |
+| `style` | Code style/formatting (no logic change) | `style: format with prettier` | Linting, formatting, whitespace |
+| `refactor` | Code restructuring (no functional change) | `refactor: extract user validation logic` | Improving code without changing behavior |
+| `perf` | Performance improvement | `perf: cache database query results` | Optimizations that improve speed/memory |
+| `test` | Adding or updating tests | `test: add unit tests for auth module` | Test files or test infrastructure |
+| `build` | Build system or external dependencies | `build: update webpack config` | Build tools, package managers |
+| `ci` | CI/CD configuration changes | `ci: add code coverage reporting` | GitHub Actions, deployment scripts |
+| `revert` | Reverts a previous commit | `revert: revert commit abc123` | Undoing a previous commit |
+
+### Scope (Optional but Recommended)
+
+Add scope in parentheses to specify what part of the codebase changed:
+
+```
+feat(auth): add OAuth2 provider support
+fix(api): handle null response from external service
+docs(readme): add Docker installation instructions
+chore(deps): upgrade React to 18.3.0
+```
+
+**Common Scopes**:
+- Component names: `(button)`, `(modal)`, `(navbar)`
+- Module names: `(auth)`, `(api)`, `(database)`
+- Feature areas: `(settings)`, `(profile)`, `(checkout)`
+- Layer names: `(frontend)`, `(backend)`, `(infrastructure)`
+
+## Quick Guidelines
+
+✅ **DO**:
+- Use imperative mood: "Add", "Fix", "Update", "Remove"
+- Start with lowercase type: `feat:`, `fix:`, `docs:`
+- Be specific: "Fix login redirect" not "Fix bug"
+- Reference issues/tickets: `Fixes #123`
+- Commit frequently with focused changes
+- Write for your future self and team
+- Double-check spelling and grammar
+- Use conventional commit types
+
+❌ **DON'T**:
+- End summary with punctuation (`.`, `!`, `?`)
+- Use past tense: "Added", "Fixed", "Updated"
+- Use vague messages: "Fix stuff", "Update code", "WIP"
+- Capitalize randomly: "Fix Bug in Login"
+- Commit everything at once: "Update multiple files"
+- Use humor/emojis in professional contexts (unless team standard)
+- Write commit messages when tired or rushed
+
+## Examples
+
+### ✅ Excellent Examples
+
+#### Simple Feature
+```
+feat(auth): add two-factor authentication
+
+Implement TOTP-based 2FA using the speakeasy library.
+Users can enable 2FA in account settings.
+
+Closes #234
+```
+
+#### Bug Fix with Context
+```
+fix(api): prevent race condition in user updates
+
+Previously, concurrent updates to user profiles could
+result in lost data. Added optimistic locking with
+version field to detect conflicts.
+
+The retry logic attempts up to 3 times before failing.
+
+Fixes #567
+```
+
+#### Documentation Update
+```
+docs: add troubleshooting section to README
+
+Include solutions for common installation issues:
+- Node version compatibility
+- Database connection errors
+- Environment variable configuration
+```
+
+#### Dependency Update
+```
+chore(deps): upgrade express from 4.17 to 4.19
+
+Security patch for CVE-2024-12345. No breaking changes
+or API modifications required.
+```
+
+#### Breaking Change
+```
+feat(api): redesign user authentication endpoint
+
+BREAKING CHANGE: The /api/login endpoint now returns
+a JWT token in the response body instead of a cookie.
+Clients must update to include the Authorization header
+in subsequent requests.
+
+Migration guide: docs/migration/auth-token.md
+Closes #789
+```
+
+#### Refactoring
+```
+refactor(services): extract user service interface
+
+Move user-related business logic from handlers to a
+dedicated service layer. No functional changes.
+
+Improves testability and separation of concerns.
+```
+
+### ❌ Bad Examples
+
+```
+❌ update files
+   → Too vague - what was updated and why?
+
+❌ Fixed the login bug.
+   → Past tense, period at end, no context
+
+❌ feat: Add new feature for users to be able to...
+   → Too long for title, should be in body
+
+❌ WIP
+   → Not descriptive, doesn't explain intent
+
+❌ Merge branch 'feature/xyz'
+   → Meaningless merge commit (use squash or rebase)
+
+❌ asdfasdf
+   → Completely unhelpful
+
+❌ Fixes issue
+   → Which issue? No issue number
+
+❌ Updated stuff in the backend
+   → Vague, no technical detail
+```
+
+## Advanced Guidelines
+
+### Atomic Commits
+
+Each commit should represent one logical change:
+
+✅ **Good**: Three separate commits
+```
+feat(auth): add login endpoint
+feat(auth): add logout endpoint
+test(auth): add integration tests for auth endpoints
+```
+
+❌ **Bad**: One commit with everything
+```
+feat: implement authentication system
+(Contains login, logout, tests, and unrelated CSS changes)
+```
+
+### Commit Frequency
+
+**Commit often to**:
+- Keep messages focused and simple
+- Make code review easier
+- Simplify debugging with `git bisect`
+- Reduce risk of lost work
+
+**Good rhythm**:
+- After completing a logical unit of work
+- Before switching tasks or taking a break
+- When tests pass for a feature component
+
+### Issue/Ticket References
+
+Include issue references in the footer:
+
+```
+feat(api): add rate limiting middleware
+
+Implement rate limiting using express-rate-limit to
+prevent API abuse. Default: 100 requests per 15 minutes.
+
+Closes #345
+Refs #346, #347
+```
+
+**Keywords for automatic closing**:
+- `Closes #123`, `Fixes #123`, `Resolves #123`
+- `Closes: #123` (with colon)
+- Multiple: `Fixes #123, #124, #125`
+
+### Co-authored Commits
+
+For pair programming or collaborative work:
+
+```
+feat(ui): redesign dashboard layout
+
+Co-authored-by: Jane Doe <jane@example.com>
+Co-authored-by: John Smith <john@example.com>
+```
+
+### Reverting Commits
+
+```
+revert: revert "feat(api): add rate limiting"
+
+This reverts commit abc123def456.
+
+Rate limiting caused issues with legitimate high-volume
+clients. Will redesign with whitelist support.
+
+Refs #400
+```
+
+## Team-Specific Customization
+
+### Define Team Standards
+
+Document your team's commit message conventions:
+
+1. **Type Usage**: Which types your team uses (subset of conventional)
+2. **Scope Format**: How to name scopes (kebab-case? camelCase?)
+3. **Issue Format**: Jira ticket format vs GitHub issues
+4. **Special Markers**: Any team-specific prefixes or tags
+5. **Breaking Changes**: How to communicate breaking changes
+
+### Example Team Rules
+
+```markdown
+## Team Commit Standards
+
+- Always include scope for domain code
+- Use JIRA ticket format: `PROJECT-123`
+- Mark breaking changes with [BREAKING] prefix in title
+- Include emoji prefix: ✨ feat, 🐛 fix, 📚 docs
+- All feat/fix must reference a ticket
+```
+
+## Validation and Enforcement
+
+### Pre-commit Hooks
+
+Use tools to enforce commit message standards:
+
+**commitlint** (Recommended)
+```bash
+npm install --save-dev @commitlint/{cli,config-conventional}
+```
+
+**.commitlintrc.json**
+```json
+{
+  "extends": ["@commitlint/config-conventional"],
+  "rules": {
+    "type-enum": [2, "always", [
+      "feat", "fix", "docs", "style", "refactor",
+      "perf", "test", "build", "ci", "chore", "revert"
+    ]],
+    "subject-case": [2, "always", "sentence-case"],
+    "subject-max-length": [2, "always", 50],
+    "body-max-line-length": [2, "always", 72]
+  }
+}
+```
+
+### Manual Validation Checklist
+
+Before committing, verify:
+
+- [ ] Type is correct and lowercase
+- [ ] Subject is imperative mood
+- [ ] Subject is 50 characters or less
+- [ ] No period at end of subject
+- [ ] Body lines wrap at 72 characters
+- [ ] Body explains WHAT and WHY, not HOW
+- [ ] Issue/ticket referenced if applicable
+- [ ] Spelling and grammar checked
+- [ ] Breaking changes documented
+- [ ] Tests pass
+
+## Tools for Better Commit Messages
+
+### Git Commit Template
+
+Create a commit template to remind you of the format:
+
+**~/.gitmessage**
+```
+# <type>(<scope>): <subject> (max 50 chars)
+# |<----  Using a Maximum Of 50 Characters  ---->|
+
+# Explain why this change is being made
+# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|
+
+# Provide links or keys to any relevant tickets, articles or other resources
+# Example: Fixes #23
+
+# --- COMMIT END ---
+# Type can be:
+#   feat     (new feature)
+#   fix      (bug fix)
+#   refactor (refactoring production code)
+#   style    (formatting, missing semi colons, etc; no code change)
+#   docs     (changes to documentation)
+#   test     (adding or refactoring tests; no production code change)
+#   chore    (updating grunt tasks etc; no production code change)
+# --------------------
+# Remember to:
+#   - Use imperative mood in subject line
+#   - Do not end the subject line with a period
+#   - Capitalize the subject line
+#   - Separate subject from body with a blank line
+#   - Use the body to explain what and why vs. how
+#   - Can use multiple lines with "-" for bullet points in body
+```
+
+**Enable it**:
+```bash
+git config --global commit.template ~/.gitmessage
+```
+
+### IDE Extensions
+
+- **VS Code**: GitLens, Conventional Commits
+- **JetBrains**: Git Commit Template
+- **Sublime**: Git Commitizen
+
+### Git Aliases for Quick Commits
+
+```bash
+# Add to ~/.gitconfig or ~/.git/config
+[alias]
+  cf = "!f() { git commit -m \"feat: $1\"; }; f"
+  cx = "!f() { git commit -m \"fix: $1\"; }; f"
+  cd = "!f() { git commit -m \"docs: $1\"; }; f"
+  cc = "!f() { git commit -m \"chore: $1\"; }; f"
+```
+
+**Usage**:
+```bash
+git cf "add user authentication"  # Creates: feat: add user authentication
+git cx "resolve null pointer in handler"  # Creates: fix: resolve null pointer in handler
+```
+
+## Amending and Fixing Commit Messages
+
+### Edit Last Commit Message
+
+```bash
+git commit --amend -m "new commit message"
+```
+
+### Edit Last Commit Message in Editor
+
+```bash
+git commit --amend
+```
+
+### Edit Older Commit Messages
+
+```bash
+git rebase -i HEAD~3  # Edit last 3 commits
+# Change "pick" to "reword" for commits to edit
+```
+
+⚠️ **Warning**: Never amend or rebase commits that have been pushed to shared branches!
+
+## Language-Specific Considerations
+
+### Go Projects
+```
+feat(http): add middleware for request logging
+refactor(db): migrate from database/sql to sqlx
+fix(parser): handle edge case in JSON unmarshaling
+```
+
+### JavaScript/TypeScript Projects
+```
+feat(components): add error boundary component
+fix(hooks): prevent infinite loop in useEffect
+chore(deps): upgrade React to 18.3.0
+```
+
+### Python Projects
+```
+feat(api): add FastAPI endpoint for user registration
+fix(models): correct SQLAlchemy relationship mapping
+test(utils): add unit tests for date parsing
+```
+
+## Common Pitfalls and Solutions
+
+| Pitfall | Solution |
+|---------|----------|
+| Forgetting to commit | Set reminders, commit frequently |
+| Vague messages | Include specific details about what changed |
+| Too many changes in one commit | Break into atomic commits |
+| Past tense usage | Use imperative mood |
+| Missing issue references | Always link to tracking system |
+| Not explaining "why" | Add body explaining motivation |
+| Inconsistent formatting | Use commitlint or pre-commit hooks |
+
+## Changelog Generation
+
+Well-formatted commits enable automatic changelog generation:
+
+**Example Tools**:
+- `conventional-changelog`
+- `semantic-release`
+- `standard-version`
+
+**Generated Changelog**:
+```markdown
+## [1.2.0] - 2024-01-15
+
+### Features
+- **auth**: add two-factor authentication (#234)
+- **api**: add rate limiting middleware (#345)
+
+### Bug Fixes
+- **api**: prevent race condition in user updates (#567)
+- **ui**: correct alignment in mobile view (#590)
+
+### Documentation
+- add troubleshooting section to README
+- update API documentation with new endpoints
+```
+
+## Resources
+
+- [Conventional Commits Specification](https://www.conventionalcommits.org/)
+- [Angular Commit Guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit)
+- [Semantic Versioning](https://semver.org/)
+- [GitKraken Commit Message Guide](https://www.gitkraken.com/learn/git/best-practices/git-commit-message)
+- [Git Commit Message Style Guide](https://udacity.github.io/git-styleguide/)
+- [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/)
+
+## Summary
+
+**The 7 Rules of Great Commit Messages**:
+
+1. Use conventional commit format: `type(scope): subject`
+2. Limit subject line to 50 characters
+3. Use imperative mood: "Add" not "Added"
+4. Don't end subject with punctuation
+5. Separate subject from body with blank line
+6. Wrap body at 72 characters
+7. Explain what and why, not how
+
+**Remember**: A great commit message helps your future self and your team understand the evolution of the codebase. Write commit messages that you'd want to read when debugging at 2 AM! 🕑

.github/instructions/copilot-instructions.md

@@ -5,12 +5,35 @@
 Every session should improve the codebase, not just add to it. Actively refactor code you encounter, even outside of your immediate task scope. Think about long-term maintainability and consistency. Make a detailed plan before writing code. Always create unit tests for new code coverage.
 
 - **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
+- **ARCHITECTURE AWARENESS**: Always consult `ARCHITECTURE.md` at the repository root before making significant changes to:
+  - Core components (Backend API, Frontend, Caddy Manager, Security layers)
+  - System architecture or data flow
+  - Technology stack or dependencies
+  - Deployment configuration
+  - Directory structure or file organization
 - **DRY**: Consolidate duplicate patterns into reusable functions, types, or components after the second occurrence.
 - **CLEAN**: Delete dead code immediately. Remove unused imports, variables, functions, types, commented code, and console logs.
 - **LEVERAGE**: Use battle-tested packages over custom implementations.
 - **READABLE**: Maintain comments and clear naming for complex logic. Favor clarity over cleverness.
 - **CONVENTIONAL COMMITS**: Write commit messages using `feat:`, `fix:`, `chore:`, `refactor:`, or `docs:` prefixes.
 
+## Governance & Precedence
+
+When policy statements conflict across documentation sources, resolve using this precedence hierarchy:
+
+1. **Highest Precedence**: `.github/instructions/**` files (canonical source of truth)
+2. **Agent Overrides**: `.github/agents/**` files (agent-specific customizations)
+3. **Operator Documentation**: `SECURITY.md`, `docs/security.md`,
+   `docs/features/notifications.md` (user-facing guidance)
+
+**Reconciliation Rule**: When conflicts arise, the stricter security requirement
+wins. Update downstream documentation to match canonical text in
+`.github/instructions/**`.
+
+**Example**: If `.github/instructions/security.instructions.md` mandates token
+redaction but operator docs suggest logging is acceptable, token redaction
+requirement takes precedence and operator docs must be updated.
+
 ## 🚨 CRITICAL ARCHITECTURE RULES 🚨
 
 - **Single Frontend Source**: All frontend code MUST reside in `frontend/`. NEVER create `backend/frontend/` or any other nested frontend directory.
@@ -44,7 +67,7 @@ Before proposing ANY code change or fix, you must build a mental map of the feat
 
 - **Run**: `cd backend && go run ./cmd/api`.
 - **Test**: `go test ./...`.
-- **Static Analysis (BLOCKING)**: Fast linters run automatically on every commit via pre-commit hooks.
+- **Static Analysis (BLOCKING)**: Fast linters run automatically on every commit via lefthook pre-commit-phase hooks.
   - **Staticcheck errors MUST be fixed** - commits are BLOCKED until resolved
   - Manual run: `make lint-fast` or VS Code task "Lint: Staticcheck (Fast)"
   - Staticcheck-only: `make lint-staticcheck-only`
@@ -56,7 +79,7 @@ Before proposing ANY code change or fix, you must build a mental map of the feat
 - **Security**: Sanitize all file paths using `filepath.Clean`. Use `fmt.Errorf("context: %w", err)` for error wrapping.
 - **Graceful Shutdown**: Long-running work must respect `server.Run(ctx)`.
 
-### Troubleshooting Pre-Commit Staticcheck Failures
+### Troubleshooting Lefthook Staticcheck Failures
 
 **Common Issues:**
 
@@ -101,6 +124,13 @@ Before proposing ANY code change or fix, you must build a mental map of the feat
 
 ## Documentation
 
+- **Architecture**: Update `ARCHITECTURE.md` when making changes to:
+  - System architecture or component interactions
+  - Technology stack (major version upgrades, library replacements)
+  - Directory structure or organizational conventions
+  - Deployment model or infrastructure
+  - Security architecture or data flow
+  - Integration points or external dependencies
 - **Features**: Update `docs/features.md` when adding capabilities. This is a short "marketing" style list. Keep details to their individual docs.
 - **Links**: Use GitHub Pages URLs (`https://wikid82.github.io/charon/`) for docs and GitHub blob links for repo files.
 
@@ -110,28 +140,64 @@ Before proposing ANY code change or fix, you must build a mental map of the feat
 - **Beta**: `feature/beta-release` always builds.
 - **History-Rewrite PRs**: If a PR touches files in `scripts/history-rewrite/` or `docs/plans/history_rewrite.md`, the PR description MUST include the history-rewrite checklist from `.github/PULL_REQUEST_TEMPLATE/history-rewrite.md`. This is enforced by CI.
 
+## PR Sizing & Decomposition
+
+- **Default Rule**: Prefer smaller, reviewable PRs over one large PR when work spans multiple domains.
+- **Split into Multiple PRs When**:
+    - The change touches backend + frontend + infrastructure/security in one effort
+    - The estimated diff is large enough to reduce review quality or increase rollback risk
+    - The work can be delivered in independently testable slices without breaking behavior
+    - A foundational refactor is needed before feature delivery
+- **Suggested PR Sequence**:
+    1. Foundation PR (types/contracts/refactors, no behavior change)
+    2. Backend PR (API/model/service changes + tests)
+    3. Frontend PR (UI integration + tests)
+    4. Hardening PR (security/CI/docs/follow-up fixes)
+- **Per-PR Requirement**: Every PR must remain deployable, pass DoD checks, and include a clear dependency note on prior PRs.
+
 ## ✅ Task Completion Protocol (Definition of Done)
 
 Before marking an implementation task as complete, perform the following in order:
 
 1. **Playwright E2E Tests** (MANDATORY - Run First):
-    - **Run**: `npx playwright test --project=chromium` from project root
+    - **Run**: `cd /projects/Charon npx playwright test --project=firefox` from project root
     - **Why First**: If the app is broken at E2E level, unit tests may need updates. Catch integration issues early.
     - **Scope**: Run tests relevant to modified features (e.g., `tests/manual-dns-provider.spec.ts`)
     - **On Failure**: Trace root cause through frontend → backend flow before proceeding
     - **Base URL**: Uses `PLAYWRIGHT_BASE_URL` or default from `playwright.config.js`
     - All E2E tests must pass before proceeding to unit tests
 
-2. **Security Scans** (MANDATORY - Zero Tolerance):
-    - **CodeQL Go Scan**: Run VS Code task "Security: CodeQL Go Scan (CI-Aligned)" OR `pre-commit run codeql-go-scan --all-files`
+1.5. **GORM Security Scan** (CONDITIONAL, BLOCKING):
+    - **Trigger Condition**: Execute this gate when changes include backend models or database interaction logic:
+        - `backend/internal/models/**`
+        - GORM query/service layers
+        - Database migrations or seeding logic
+    - **Exclusions**: Skip this gate for docs-only (`**/*.md`) or frontend-only (`frontend/**`) changes
+    - **Run One Of**:
+        - VS Code task: `Lint: GORM Security Scan`
+        - Lefthook: `lefthook run pre-commit` (includes gorm-security-scan)
+        - Direct: `./scripts/scan-gorm-security.sh --check`
+        - **Gate Enforcement**: DoD is process-blocking until scanner reports zero
+            CRITICAL/HIGH findings, even while automation remains in manual stage
+        - **Check Mode Required**: Gate decisions must use check mode semantics
+            (`--check` flag or equivalent task wiring) for pass/fail determination
+
+2. **Local Patch Coverage Preflight** (MANDATORY - Run Before Unit/Coverage Tests):
+    - **Run**: VS Code task `Test: Local Patch Report` or `bash scripts/local-patch-report.sh` from repo root.
+    - **Purpose**: Surface exact changed files and uncovered changed lines before adding/refining unit tests.
+    - **Required Artifacts**: `test-results/local-patch-report.md` and `test-results/local-patch-report.json`.
+    - **Expected Behavior**: Report may warn (non-blocking rollout), but artifact generation is mandatory.
+
+3. **Security Scans** (MANDATORY - Zero Tolerance):
+    - **CodeQL Go Scan**: Run VS Code task "Security: CodeQL Go Scan (CI-Aligned)" OR `lefthook run pre-commit`
         - Must use `security-and-quality` suite (CI-aligned)
         - **Zero high/critical (error-level) findings allowed**
         - Medium/low findings should be documented and triaged
-    - **CodeQL JS Scan**: Run VS Code task "Security: CodeQL JS Scan (CI-Aligned)" OR `pre-commit run codeql-js-scan --all-files`
+    - **CodeQL JS Scan**: Run VS Code task "Security: CodeQL JS Scan (CI-Aligned)" OR `lefthook run pre-commit`
         - Must use `security-and-quality` suite (CI-aligned)
         - **Zero high/critical (error-level) findings allowed**
         - Medium/low findings should be documented and triaged
-    - **Validate Findings**: Run `pre-commit run codeql-check-findings --all-files` to check for HIGH/CRITICAL issues
+    - **Validate Findings**: Run `lefthook run pre-commit` to check for HIGH/CRITICAL issues
     - **Trivy Container Scan**: Run VS Code task "Security: Trivy Scan" for container/dependency vulnerabilities
     - **Results Viewing**:
         - Primary: VS Code SARIF Viewer extension (`MS-SarifVSCode.sarif-viewer`)
@@ -144,12 +210,12 @@ Before marking an implementation task as complete, perform the following in orde
         - Database creation: `--threads=0 --overwrite`
         - Analysis: `--sarif-add-baseline-file-info`
 
-3. **Pre-Commit Triage**: Run `pre-commit run --all-files`.
+4. **Lefthook Triage**: Run `lefthook run pre-commit`.
     - If errors occur, **fix them immediately**.
     - If logic errors occur, analyze and propose a fix.
     - Do not output code that violates pre-commit standards.
 
-4. **Staticcheck BLOCKING Validation**: Pre-commit hooks automatically run fast linters including staticcheck.
+5. **Staticcheck BLOCKING Validation**: Pre-commit hooks automatically run fast linters including staticcheck.
     - **CRITICAL:** Staticcheck errors are BLOCKING - you MUST fix them before commit succeeds.
     - Manual verification: Run VS Code task "Lint: Staticcheck (Fast)" or `make lint-fast`
     - To check only staticcheck: `make lint-staticcheck-only`
@@ -157,8 +223,9 @@ Before marking an implementation task as complete, perform the following in orde
     - If pre-commit fails: Fix the reported issues, then retry commit
     - **Do NOT** use `--no-verify` to bypass this check unless emergency hotfix
 
-5. **Coverage Testing** (MANDATORY - Non-negotiable):
-    - **MANDATORY**: Patch coverage must cover 100% of modified lines (Codecov Patch view must be green). If patch coverage fails, add targeted tests for the missing patch line ranges.
+6. **Coverage Testing** (MANDATORY - Non-negotiable):
+    - **Overall Coverage**: Minimum 85% coverage is MANDATORY and will fail the PR if not met.
+    - **Patch Coverage**: Developers should aim for 100% coverage of modified lines (Codecov Patch view). If patch coverage is incomplete, add targeted tests. However, patch coverage is a suggestion and will not block PR approval.
     - **Backend Changes**: Run the VS Code task "Test: Backend with Coverage" or execute `scripts/go-test-coverage.sh`.
         - Minimum coverage: 85% (set via `CHARON_MIN_COVERAGE` or `CPM_MIN_COVERAGE`).
         - If coverage drops below threshold, write additional tests to restore coverage.
@@ -170,21 +237,21 @@ Before marking an implementation task as complete, perform the following in orde
     - **Critical**: Coverage tests are NOT run by default pre-commit hooks (they are in manual stage for performance). You MUST run them explicitly via VS Code tasks or scripts before completing any task.
     - **Why**: CI enforces coverage in GitHub Actions. Local verification prevents CI failures and maintains code quality.
 
-6. **Type Safety** (Frontend only):
+7. **Type Safety** (Frontend only):
     - Run the VS Code task "Lint: TypeScript Check" or execute `cd frontend && npm run type-check`.
     - Fix all type errors immediately. This is non-negotiable.
     - This check is also in manual stage for performance but MUST be run before completion.
 
-7. **Verify Build**: Ensure the backend compiles and the frontend builds without errors.
+8. **Verify Build**: Ensure the backend compiles and the frontend builds without errors.
     - Backend: `cd backend && go build ./...`
     - Frontend: `cd frontend && npm run build`
 
-8. **Fixed and New Code Testing**:
+9. **Fixed and New Code Testing**:
     - Ensure all existing and new unit tests pass with zero failures.
     - When failures and errors are found, deep-dive into root causes. Using the correct `subAgent`, update the working plan, review the implementation, and fix the issues.
     - No issue is out of scope for investigation and resolution. All issues must be addressed before task completion.
 
-9. **Clean Up**: Ensure no debug print statements or commented-out blocks remain.
+10. **Clean Up**: Ensure no debug print statements or commented-out blocks remain.
     - Remove `console.log`, `fmt.Println`, and similar debugging statements.
     - Delete commented-out code blocks.
     - Remove unused imports.

.github/instructions/documentation-coding-best-practices.instructions.md

@@ -0,0 +1,43 @@
+---
+description: This file describes the documentation and coding best practices for the project.
+applyTo: '*'
+---
+
+
+# Documentation & Coding Best Practices
+
+The following instructions govern how you should generate and update documentation and code. These rules are absolute.
+
+## 1. Zero-Footprint Attribution (The Ghostwriter Rule)
+* **No AI Branding:** You are a ghostwriter. You must **NEVER** add sections titled "AI Notes," "Generated by," "Model Commentary," or "LLM Analysis."
+* **Invisible Editing:** The documentation must appear as if written 100% by the project maintainer. Do not leave "scars" or meta-tags indicating an AI touched the file.
+* **The "Author" Field:** * **Existing Files:** NEVER modify an existing `Author` field.
+    * **New Files:** Do NOT add an `Author` field unless explicitly requested.
+    * **Strict Prohibition:** You are strictly forbidden from placing "GitHub Copilot," "AI," "Assistant," or your model name in any `Author`, `Credits`, or `Contributor` field.
+
+## 2. Documentation Style
+* **Direct & Professional:** The documentation itself is the "note." Do not add a separate preamble or postscript explaining what you wrote.
+* **No Conversational Filler:** When asked to generate documentation, output *only* the documentation content. Do not wrap it in "Here is the updated file:" or "I have added the following..."
+* **Maintenance:** When updating a file, respect the existing formatting style (headers, indentation, bullet points) perfectly. Do not "fix" style choices unless they are actual syntax errors.
+* **Consistency:** Follow the existing style of the file. If the file uses a specific format for sections, maintain that format. Do not introduce new formatting styles.
+* **Clarity & Brevity:** Be concise and clear. Avoid unnecessary verbosity or overly technical jargon unless the file's existing style is already very technical. Match the tone and complexity of the existing documentation.
+
+## 3. Interaction Constraints
+* **Calm & Concise:** Be succinct. Do not offer unsolicited advice or "bonus" refactoring unless it is critical for security.
+* **Context Retention:** Assume the user knows what they are doing. Do not explain basic concepts unless asked.
+* **No Code Generation in Documentation Files:** When editing documentation files, do not generate code snippets unless they are explicitly requested. Focus on the documentation content itself.
+* **No Meta-Comments:** Do not include comments about the editing process, your thought process, or any "notes to self" in the documentation. The output should be clean and ready for use.
+* **Respect User Intent:** If the user asks for a specific change, do only that change. Do not add additional edits or improvements unless they are critical for security or correctness.
+* **No "Best Practices" Sections:** Do not add sections titled "Best Practices," "Recommendations," or "Guidelines" unless the existing file already has such a section. If the file does not have such a section, do not create one.
+* **No "Next Steps" or "Further Reading":** Do not add sections that suggest next steps, further reading, or related topics unless the existing file already includes such sections.
+* **No Personalization:** Do not personalize the documentation with phrases like "As a developer, you should..." or "In this project, we recommend..." Keep the tone neutral and professional.
+* **No Apologies or Uncertainty:** Do not include phrases like "I hope this helps," "Sorry for the confusion," or "Please let me know if you have any questions." The documentation should be authoritative and confident.
+* **No Redundant Information:** Do not include information that is already clearly stated in the existing documentation. Avoid redundancy.
+* **No Unsolicited Refactoring:** Do not refactor existing documentation for style or clarity unless it contains critical errors. Focus on the specific changes requested by the user.
+* **No "Summary" or "Overview" Sections:** Do not add summary or overview sections unless the existing file already has them. If the file does not have such sections, do not create them.
+* **No "How It Works" Sections:** Do not add sections explaining how the code works unless the existing documentation already includes such sections. If the file does not have such sections, do not create them.
+* **No "Use Cases" or "Examples":** Do not add use cases, examples, or case studies unless the existing documentation already has such sections. If the file does not have such sections, do not create them.
+* **No "Troubleshooting" Sections:** Do not add troubleshooting sections unless the existing documentation already includes them. Toubleshooting is its own section of the docs and should not be added ad-hoc to unrelated files.
+* **No "FAQ" Sections:** Do not add FAQ sections unless the existing documentation already has them. If the file does not have such sections, do not create them.
+* **No "Contact" or "Support" Sections:** Do not add contact information, support channels, or similar sections unless the existing documentation already includes them. If the file does not have such sections, do not create them.
+* **No "Contributing" Sections:** Contributing has its on documentation file. Do not add contributing guidelines to unrelated documentation files unless they already have such sections.

.github/instructions/features.instructions.md

@@ -9,8 +9,8 @@ When creating or updating the `docs/features.md` file, please adhere to the foll
 
 ## Structure
 
-   - This document should provide a short, to the point overview of each feature. It is used for marketing of the project. A quick read of what the feature is and why it matters. It is the "elevator pitch" for each feature.
-   - Each feature should have its own section with a clear heading.
+    - This document should provide a short, to the point overview of each feature. It is used for marketing of the project. A quick read of what the feature is and why it matters. It is the "elevator pitch" for each feature.
+    - Each feature should have its own section with a clear heading.
     - Use bullet points or numbered lists to break down complex information.
     - Include relevant links to other documentation or resources for further reading.
     - Use consistent formatting for headings, subheadings, and text styles throughout the document.
@@ -20,7 +20,11 @@ When creating or updating the `docs/features.md` file, please adhere to the foll
 ## Content
     - Start with a brief summary of the feature.
     - Explain the purpose and benefits of the feature.
-    - Keep
+    - Keep descriptions concise and focused.
     - Ensure accuracy and up-to-date information.
 
 ## Review
+    - Changes to `docs/features.md` should be reviewed by at least one other contributor before merging.
+    - Review for correctness, clarity, and consistency with the guidelines in this file.
+    - Confirm that each feature description reflects the current behavior and positioning of the project.
+    - Ensure the tone remains high-level and marketing‑oriented, avoiding deep technical implementation details.

.github/instructions/github-actions-ci-cd-best-practices.instructions.md

@@ -502,6 +502,8 @@ This checklist provides a granular set of criteria for reviewing GitHub Actions
 
 This section provides an expanded guide to diagnosing and resolving frequent problems encountered when working with GitHub Actions workflows.
 
+Note: If workflow logs are not accessible via MCP web fetch due to missing auth, retrieve logs with the authenticated `gh` CLI.
+
 ### **1. Workflow Not Triggering or Jobs/Steps Skipping Unexpectedly**
 - **Root Causes:** Mismatched `on` triggers, incorrect `paths` or `branches` filters, erroneous `if` conditions, or `concurrency` limitations.
 - **Actionable Steps:**

.github/instructions/go.instructions.md

@@ -353,7 +353,7 @@ Follow idiomatic Go practices and community standards when writing Go code. Thes
 ### Development Practices
 
 - Run tests before committing
-- Use pre-commit hooks for formatting and linting
+- Use lefthook pre-commit-phase hooks for formatting and linting
 - Keep commits focused and atomic
 - Write meaningful commit messages
 - Review diffs before committing

.github/instructions/html-css-style-color-guide.instructions.md

@@ -0,0 +1,104 @@
+---
+description: 'Color usage guidelines and styling rules for HTML elements to ensure accessible, professional designs.'
+applyTo: '**/*.html, **/*.css, **/*.js'
+---
+
+# HTML CSS Style Color Guide
+
+Follow these guidelines when updating or creating HTML/CSS styles for browser rendering. Color names
+represent the full spectrum of their respective hue ranges (e.g., "blue" includes navy, sky blue, etc.).
+
+## Color Definitions
+
+- **Hot Colors**: Oranges, reds, and yellows
+- **Cool Colors**: Blues, greens, and purples
+- **Neutral Colors**: Grays and grayscale variations
+- **Binary Colors**: Black and white
+- **60-30-10 Rule**
+  - **Primary Color**: Use 60% of the time (*cool or light color*)
+  - **Secondary Color**: Use 30% of the time (*cool or light color*)
+  - **Accent**: Use 10% of the time (*complementary hot color*)
+
+## Color Usage Guidelines
+
+Balance the colors used by applying the **60-30-10 rule** to graphic design elements like backgrounds,
+buttons, cards, etc...
+
+### Background Colors
+
+**Never Use:**
+
+- Purple or magenta
+- Red, orange, or yellow
+- Pink
+- Any hot color
+
+**Recommended:**
+
+- White or off-white
+- Light cool colors (e.g., light blues, light greens)
+- Subtle neutral tones
+- Light gradients with minimal color shift
+
+### Text Colors
+
+**Never Use:**
+
+- Yellow (poor contrast and readability)
+- Pink
+- Pure white or light text on light backgrounds
+- Pure black or dark text on dark backgrounds
+
+**Recommended:**
+
+- Dark neutral colors (e.g., #1f2328, #24292f)
+- Near-black variations (#000000 to #333333)
+  - Ensure background is a light color
+- Dark grays (#4d4d4d, #6c757d)
+- High-contrast combinations for accessibility
+- Near-white variations (#ffffff to #f0f2f3)
+  - Ensure background is a dark color
+
+### Colors to Avoid
+
+Unless explicitly required by design specifications or user request, avoid:
+
+- Bright purples and magentas
+- Bright pinks and neon colors
+- Highly saturated hot colors
+- Colors with low contrast ratios (fails WCAG accessibility standards)
+
+### Colors to Use Sparingly
+
+**Hot Colors** (red, orange, yellow):
+
+- Reserve for critical alerts, warnings, or error messages
+- Use only when conveying urgency or importance
+- Limit to small accent areas rather than large sections
+- Consider alternatives like icons or bold text before using hot colors
+
+## Gradients
+
+Apply gradients with subtle color transitions to maintain professional aesthetics.
+
+### Best Practices
+
+- Keep color shifts minimal (e.g., #E6F2FF to #F5F7FA)
+- Use gradients within the same color family
+- Avoid combining hot and cool colors in a single gradient
+- Prefer linear gradients over radial for backgrounds
+
+### Appropriate Use Cases
+
+- Background containers and sections
+- Button hover states and interactive elements
+- Drop shadows and depth effects
+- Header and navigation bars
+- Card components and panels
+
+## Additional Resources
+
+- [Color Tool](https://civicactions.github.io/uswds-color-tool/)
+- [Government or Professional Color Standards](https://designsystem.digital.gov/design-tokens/color/overview/)
+- [UI Color Palette Best Practices](https://www.interaction-design.org/literature/article/ui-color-palette)
+- [Color Combination Resource](https://www.figma.com/resource-library/color-combinations/)

.github/instructions/markdown.instructions.md

@@ -24,7 +24,7 @@ Follow these guidelines for formatting and structuring your markdown content:
 - **Headings**: Use `##` for H2 and `###` for H3. Ensure that headings are used in a hierarchical manner. Recommend restructuring if content includes H4, and more strongly recommend for H5.
 - **Lists**: Use `-` for bullet points and `1.` for numbered lists. Indent nested lists with two spaces.
 - **Code Blocks**: Use triple backticks (`) to create fenced code blocks. Specify the language after the opening backticks for syntax highlighting (e.g., `csharp).
-- **Links**: Use `[link text](URL)` for links. Ensure that the link text is descriptive and the URL is valid.
+- **Links**: Use `[link text](https://example.com)` for links. Ensure that the link text is descriptive and the URL is valid.
 - **Images**: Use `![alt text](image URL)` for images. Include a brief description of the image in the alt text.
 - **Tables**: Use `|` to create tables. Ensure that columns are properly aligned and headers are included.
 - **Line Length**: Break lines at 80 characters to improve readability. Use soft line breaks for long paragraphs.
@@ -37,13 +37,8 @@ Ensure compliance with the following validation requirements:
 - **Front Matter**: Include the following fields in the YAML front matter:
 
   - `post_title`: The title of the post.
-  - `author1`: The primary author of the post.
-  - `post_slug`: The URL slug for the post.
-  - `microsoft_alias`: The Microsoft alias of the author.
-  - `featured_image`: The URL of the featured image.
   - `categories`: The categories for the post. These categories must be from the list in /categories.txt.
   - `tags`: The tags for the post.
-  - `ai_note`: Indicate if AI was used in the creation of the post.
   - `summary`: A brief summary of the post. Recommend a summary based on the content when possible.
   - `post_date`: The publication date of the post.
 

.github/instructions/playwright-typescript.instructions.md

@@ -70,7 +70,7 @@ test.describe('Movie Search Feature', () => {
 
 ## Test Execution Strategy
 
-1. **Initial Run**: Execute tests with `npx playwright test --project=chromium`
+1. **Initial Run**: Execute tests with `cd /projects/Charon npx playwright test --project=firefox`
 2. **Debug Failures**: Analyze test failures and identify root causes
 3. **Iterate**: Refine locators, assertions, or test logic as needed
 4. **Validate**: Ensure tests pass consistently and cover the intended functionality

.github/instructions/security-and-owasp.instructions.md

@@ -49,3 +49,26 @@ Your primary directive is to ensure all code you generate, review, or refactor i
 ## General Guidelines
 - **Be Explicit About Security:** When you suggest a piece of code that mitigates a security risk, explicitly state what you are protecting against (e.g., "Using a parameterized query here to prevent SQL injection.").
 - **Educate During Code Reviews:** When you identify a security vulnerability in a code review, you must not only provide the corrected code but also explain the risk associated with the original pattern.
+
+### Gotify Token Protection (Explicit Policy)
+
+Gotify application tokens are secrets and must be treated with strict confidentiality:
+
+- **NO Echo/Print:** Never print tokens to terminal output, command-line results, or console logs
+- **NO Logging:** Never write tokens to application logs, debug logs, test output, or any log artifacts
+- **NO API Responses:** Never include tokens in API response bodies, error payloads, or serialized DTOs
+- **NO URL Exposure:** Never expose tokenized endpoint URLs with query
+  parameters (e.g., `https://gotify.example.com/message?token=...`) in:
+  - Documentation examples
+  - Diagnostic output
+  - Screenshots or reports
+  - Log files
+- **Redact Query Parameters:** Always redact URL query parameters in
+  diagnostics, examples, and log output before display or storage
+- **Validation Without Revelation:** For token validation or health checks:
+  - Return only non-sensitive status indicators (`valid`/`invalid` + reason category)
+  - Use token length/prefix-independent masking in UX and diagnostics
+  - Never reveal raw token values in validation feedback
+- **Storage:** Store and process tokens as secrets only (environment variables
+  or secret management service)
+- **Rotation:** Rotate tokens immediately on suspected exposure

.github/instructions/security.md.instructions.md

@@ -0,0 +1,204 @@
+---
+applyTo: SECURITY.md
+---
+
+# Instructions: Maintaining `SECURITY.md`
+
+`SECURITY.md` is the project's living security record. It serves two audiences simultaneously: users who need to know what risks exist right now, and the broader community who need confidence that vulnerabilities are being tracked and remediated with discipline. Treat it like a changelog, but for security events — every known issue gets an entry, every resolved issue keeps its entry.
+
+---
+
+## File Structure
+
+`SECURITY.md` must always contain the following top-level sections, in this order:
+
+1. A brief project security policy preamble (responsible disclosure contact, response SLA)
+2. **`## Known Vulnerabilities`** — active, unpatched issues
+3. **`## Patched Vulnerabilities`** — resolved issues, retained permanently for audit trail
+
+No other top-level sections are required. Do not collapse or remove sections even when they are empty — use the explicit empty-state placeholder defined below.
+
+---
+
+## Section 1: Known Vulnerabilities
+
+This section lists every vulnerability that is currently unpatched or only partially mitigated. Entries must be sorted with the highest severity first, then by discovery date descending within the same severity tier.
+
+### Entry Format
+
+Each entry is an H3 heading followed by a structured block:
+
+```markdown
+### [SEVERITY] CVE-XXXX-XXXXX · Short Title
+
+| Field        | Value |
+|--------------|-------|
+| **ID**       | CVE-XXXX-XXXXX (or `CHARON-YYYY-NNN` if no CVE assigned yet) |
+| **Severity** | Critical / High / Medium / Low · CVSS v3.1 score if known (e.g. `8.1 · High`) |
+| **Status**   | Investigating / Fix In Progress / Awaiting Upstream / Mitigated (partial) |
+
+**What**
+One to three sentences describing the vulnerability class and its impact.
+Be specific: name the weakness type (e.g. SQL injection, path traversal, SSRF).
+
+**Who**
+- Discovered by: [Reporter name or handle, or "Internal audit", or "Automated scan (tool name)"]
+- Reported: YYYY-MM-DD
+- Affects: [User roles, API consumers, unauthenticated users, etc.]
+
+**Where**
+- Component: [Module or service name]
+- File(s): `path/to/affected/file.go`, `path/to/other/file.ts`
+- Versions affected: `>= X.Y.Z` (or "all versions" / "prior to X.Y.Z")
+
+**When**
+- Discovered: YYYY-MM-DD
+- Disclosed (if public): YYYY-MM-DD (or "Not yet publicly disclosed")
+- Target fix: YYYY-MM-DD (or sprint/milestone reference)
+
+**How**
+A concise technical description of the attack vector, prerequisites, and exploitation
+method. Omit proof-of-concept code. Reference CVE advisories or upstream issue
+trackers where appropriate.
+
+**Planned Remediation**
+Describe the fix strategy: library upgrade, logic refactor, config change, etc.
+If a workaround is available in the meantime, document it here.
+Link to the tracking issue: [#NNN](https://github.com/owner/repo/issues/NNN)
+```
+
+### Empty State
+
+When there are no known vulnerabilities:
+
+```markdown
+## Known Vulnerabilities
+
+No known unpatched vulnerabilities at this time.
+Last reviewed: YYYY-MM-DD
+```
+
+---
+
+## Section 2: Patched Vulnerabilities
+
+This section is a permanent, append-only ledger. Entries are never deleted. Sort newest-patched first. This section builds community trust by demonstrating that issues are resolved promptly and transparently.
+
+### Entry Format
+
+```markdown
+### ✅ [SEVERITY] CVE-XXXX-XXXXX · Short Title
+
+| Field        | Value |
+|--------------|-------|
+| **ID**       | CVE-XXXX-XXXXX (or internal ID) |
+| **Severity** | Critical / High / Medium / Low · CVSS v3.1 score |
+| **Patched**  | YYYY-MM-DD in `vX.Y.Z` |
+
+**What**
+Same description carried over from the Known Vulnerabilities entry.
+
+**Who**
+- Discovered by: [Reporter or method]
+- Reported: YYYY-MM-DD
+
+**Where**
+- Component: [Module or service name]
+- File(s): `path/to/affected/file.go`
+- Versions affected: `< X.Y.Z`
+
+**When**
+- Discovered: YYYY-MM-DD
+- Patched: YYYY-MM-DD
+- Time to patch: N days
+
+**How**
+Same technical description as the original entry.
+
+**Resolution**
+Describe exactly what was changed to fix the issue.
+- Commit: [`abc1234`](https://github.com/owner/repo/commit/abc1234)
+- PR: [#NNN](https://github.com/owner/repo/pull/NNN)
+- Release: [`vX.Y.Z`](https://github.com/owner/repo/releases/tag/vX.Y.Z)
+
+**Credit**
+[Optional] Thank the reporter if they consented to attribution.
+```
+
+### Empty State
+
+```markdown
+## Patched Vulnerabilities
+
+No patched vulnerabilities on record yet.
+```
+
+---
+
+## Lifecycle: Moving an Entry from Known → Patched
+
+When a fix ships:
+
+1. Remove the entry from `## Known Vulnerabilities` entirely.
+2. Add a new entry to the **top** of `## Patched Vulnerabilities` using the patched format above.
+3. Carry forward all original fields verbatim — do not rewrite the history of the issue.
+4. Add the `**Resolution**` and `**Credit**` blocks with patch details.
+5. Update the `Last reviewed` date on the Known Vulnerabilities section if it is now empty.
+
+Do not edit or backfill existing Patched entries once they are committed.
+
+---
+
+## Severity Classification
+
+Use the following definitions consistently:
+
+| Severity | CVSS Range | Meaning |
+|----------|------------|---------|
+| **Critical** | 9.0–10.0 | Remote code execution, auth bypass, full data exposure |
+| **High**     | 7.0–8.9  | Significant data exposure, privilege escalation, DoS |
+| **Medium**   | 4.0–6.9  | Limited data exposure, requires user interaction or auth |
+| **Low**      | 0.1–3.9  | Minimal impact, difficult to exploit, defense-in-depth |
+
+When a CVE CVSS score is not yet available, assign a preliminary severity based on these definitions and note it as `(preliminary)` until confirmed.
+
+---
+
+## Internal IDs
+
+If a vulnerability has no CVE assigned, use the format `CHARON-YYYY-NNN` where `YYYY` is the year and `NNN` is a zero-padded sequence number starting at `001` for each year. Example: `CHARON-2025-003`. Assign a CVE ID in the entry retroactively if one is issued later, and add the internal ID as an alias in parentheses.
+
+---
+
+## Responsible Disclosure Preamble
+
+The preamble at the top of `SECURITY.md` (before the vulnerability sections) must include:
+
+- The preferred contact method for reporting vulnerabilities (e.g. a GitHub private advisory link, a security email address, or both)
+- An acknowledgment-first response commitment: confirm receipt within 48 hours, even if the full investigation takes longer
+- A statement that reporters will not be penalized or publicly named without consent
+- A link to the full disclosure policy if one exists
+
+Example:
+
+```markdown
+## Reporting a Vulnerability
+
+To report a security issue, please use
+[GitHub Private Security Advisories](https://github.com/owner/repo/security/advisories/new)
+or email `security@example.com`.
+
+We will acknowledge your report within **48 hours** and provide a remediation
+timeline within **7 days**. Reporters are credited with their consent.
+We do not pursue legal action against good-faith security researchers.
+```
+
+---
+
+## Maintenance Rules
+
+- **Review cadence**: Update the `Last reviewed` date in the Known Vulnerabilities section at least once per release cycle, even if no entries changed.
+- **No silent patches**: Every security fix — no matter how minor — must produce an entry in `## Patched Vulnerabilities` before or alongside the release.
+- **No redaction**: Do not redact or soften historical entries. Accuracy builds trust; minimizing past issues destroys it.
+- **Dependency vulnerabilities**: Transitive dependency CVEs that affect Charon's exposed attack surface must be tracked here the same as first-party vulnerabilities. Pure dev-dependency CVEs with no runtime impact may be omitted at maintainer discretion, but must still be noted in the relevant dependency update PR.
+- **Partial mitigations**: If a workaround is deployed but the root cause is not fixed, the entry stays in `## Known Vulnerabilities` with `Status: Mitigated (partial)` and the workaround documented in `**Planned Remediation**`.

.github/instructions/structure.instructions.md

@@ -9,7 +9,7 @@ description: 'Repository structure guidelines to maintain organized file placeme
 
 The repository root should contain ONLY:
 
-- Essential config files (`.gitignore`, `.pre-commit-config.yaml`, `Makefile`, etc.)
+- Essential config files (`.gitignore`, `Makefile`, etc.)
 - Standard project files (`README.md`, `CONTRIBUTING.md`, `LICENSE`, `CHANGELOG.md`)
 - Go workspace files (`go.work`, `go.work.sum`)
 - VS Code workspace (`Chiron.code-workspace`)

.github/instructions/subagent.instructions.md

@@ -23,10 +23,22 @@ runSubagent({
 
 - Validate: `plan_file` exists and contains a `Handoff Contract` JSON.
 - Kickoff: call `Planning` to create the plan if not present.
+- Decide: check how to organize work into logical commits within a single PR (size, risk, cross-domain impact).
 - Run: execute `Backend Dev` then `Frontend Dev` sequentially.
 - Parallel: run `QA and Security`, `DevOps` and `Doc Writer` in parallel for CI / QA checks and documentation.
 - Return: a JSON summary with `subagent_results`, `overall_status`, and aggregated artifacts.
 
+2.1) Multi-Commit Slicing Protocol
+
+- All work for a single feature ships as one PR with ordered logical commits.
+- Each commit must have:
+  - Scope boundary (what is included/excluded)
+  - Dependency on previous commits
+  - Validation gates (tests/scans required for that commit)
+  - Explicit rollback notes for the PR as a whole
+- Do not start the next commit until the current commit is complete and verified.
+- Keep each commit independently reviewable within the PR.
+
 3) Return Contract that all subagents must return
 
 ```
@@ -43,6 +55,7 @@ runSubagent({
 
 - On a subagent failure, the Management agent must capture `tests.output` and decide to retry (1 retry maximum), or request a revert/rollback.
 - Clearly mark the `status` as `failed`, and include `errors` and `failing_tests` in the `summary`.
+- For multi-commit execution, mark failed commit as blocked and stop downstream commits until resolved.
 
 5) Example: Run a full Feature Implementation
 

.github/instructions/testing.instructions.md

@@ -4,13 +4,172 @@ description: 'Strict protocols for test execution, debugging, and coverage valid
 ---
 # Testing Protocols
 
+**Governance Note**: This file is subject to the precedence hierarchy defined in
+`.github/instructions/copilot-instructions.md`. When conflicts arise, canonical
+instruction files take precedence over agent files and operator documentation.
+
 ## 0. E2E Verification First (Playwright)
 
-**MANDATORY**: Before running unit tests, verify the application functions correctly end-to-end.
+**MANDATORY**: Before running unit tests, verify the application UI/UX functions correctly end-to-end.
 
-* **Run Playwright E2E Tests**: Execute `npx playwright test --project=chromium` from the project root.
+## 0.5 Local Patch Coverage Report (After Coverage Tests)
+
+**MANDATORY**: After running backend and frontend coverage tests (which generate
+`backend/coverage.txt` and `frontend/coverage/lcov.info`), run the local patch
+report to identify uncovered lines in changed files.
+
+**Purpose**: Overall coverage can be healthy while the specific lines you changed
+are untested. This step catches that gap. If uncovered lines are found in
+feature code, add targeted tests before completing the task.
+
+**Prerequisites**: Coverage artifacts must exist before running the report:
+- `backend/coverage.txt` — generated by `scripts/go-test-coverage.sh`
+- `frontend/coverage/lcov.info` — generated by `scripts/frontend-test-coverage.sh`
+
+Run one of the following from `/projects/Charon`:
+
+```bash
+# Preferred (task)
+Test: Local Patch Report
+
+# Script
+bash scripts/local-patch-report.sh
+```
+
+Required output artifacts:
+- `test-results/local-patch-report.md`
+- `test-results/local-patch-report.json`
+
+**Action on results**: If patch coverage for any changed file is below 90%, add
+tests targeting the uncovered changed lines. Re-run coverage and this report to
+verify improvement. Artifact generation is required for DoD regardless of
+threshold results.
+
+### PREREQUISITE: Start E2E Environment
+
+**CRITICAL**: Rebuild the E2E container when application or Docker build inputs change. If changes are test-only and the container is already healthy, reuse it. If the container is not running or state is suspect, rebuild.
+
+**Rebuild required (application/runtime changes):**
+- Application code or dependencies: backend/**, frontend/**, backend/go.mod, backend/go.sum, package.json, package-lock.json.
+- Container build/runtime configuration: Dockerfile, .docker/**, .docker/compose/docker-compose.playwright-*.yml, .docker/docker-entrypoint.sh.
+- Runtime behavior changes baked into the image.
+
+**Rebuild optional (test-only changes):**
+- Playwright tests and fixtures: tests/**.
+- Playwright config and runners: playwright.config.js, playwright.caddy-debug.config.js.
+- Documentation or planning files: docs/**, requirements.md, design.md, tasks.md.
+- CI/workflow changes that do not affect runtime images: .github/workflows/**.
+
+When a rebuild is required (or the container is not running), use:
+
+```bash
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e
+```
+
+This step:
+- Builds the latest Docker image with your code changes
+- Starts the `charon-e2e` container with proper environment variables from `.env`
+- Exposes required ports: 8080 (app), 2020 (emergency), 2019 (Caddy admin)
+- Waits for health check to pass
+
+**Without this step**, tests will fail with:
+- `connect ECONNREFUSED ::1:2020` - Emergency server not running
+- `connect ECONNREFUSED ::1:8080` - Application not running
+- `501 Not Implemented` - Container missing required env vars
+
+### Testing Scope Clarification
+
+**Playwright E2E Tests (UI/UX):**
+- Test user interactions with the React frontend
+- Verify UI state changes when settings are toggled
+- Ensure forms submit correctly
+- Check navigation and page rendering
+- **Port: 8080 (Charon Management Interface)**
+- **Default Browser: Firefox** (provides best cross-browser compatibility baseline)
+
+**Integration Tests (Middleware Enforcement):**
+- Test Cerberus security module enforcement
+- Verify ACL, WAF, Rate Limiting, CrowdSec actually block/allow requests
+- Test requests routing through Caddy proxy with full middleware
+- **Port: 80 (User Traffic via Caddy)**
+- **Location: `backend/integration/` with `//go:build integration` tag**
+- **CI: Runs in separate workflows (cerberus-integration.yml, waf-integration.yml, etc.)**
+
+### Two Modes: Docker vs Vite
+
+Playwright E2E tests can run in two modes with different capabilities:
+
+| Mode | Base URL | Coverage Support | When to Use |
+|------|----------|-----------------|-------------|
+| **Docker** | `http://localhost:8080` | ❌ No (0% reported) | Integration testing, CI validation |
+| **Vite Dev** | `http://localhost:5173` | ✅ Yes (real coverage) | Local development, coverage collection |
+
+**Why?** The `@bgotink/playwright-coverage` library uses V8 coverage which requires access to source files. Only the Vite dev server exposes source maps and raw source files needed for coverage instrumentation.
+
+### Running E2E Tests (Integration Mode)
+
+For general integration testing without coverage:
+
+```bash
+# Against Docker container (default)
+cd /projects/Charon && npx playwright test --project=chromium --project=firefox --project=webkit
+
+# With explicit base URL
+PLAYWRIGHT_BASE_URL=http://localhost:8080 npx playwright test --project=chromium --project=firefox --project=webkit
+```
+
+### Running E2E Tests with Coverage
+
+**IMPORTANT**: Use the dedicated skill for coverage collection:
+
+```bash
+# Recommended: Uses skill that starts Vite and runs against localhost:5173
+.github/skills/scripts/skill-runner.sh test-e2e-playwright-coverage
+```
+
+The coverage skill:
+1. Starts Vite dev server on port 5173
+2. Sets `PLAYWRIGHT_BASE_URL=http://localhost:5173`
+3. Runs tests with V8 coverage collection
+4. Generates reports in `coverage/e2e/` (LCOV, HTML, JSON)
+
+**DO NOT** expect coverage when running against Docker:
+```bash
+# ❌ WRONG: Coverage will show "Unknown% (0/0)"
+PLAYWRIGHT_BASE_URL=http://localhost:8080 npx playwright test --coverage
+
+# ✅ CORRECT: Use the coverage skill
+.github/skills/scripts/skill-runner.sh test-e2e-playwright-coverage
+```
+
+### Verifying Coverage Locally Before CI
+
+Before pushing code, verify E2E coverage:
+
+1. Run the coverage skill:
+   ```bash
+   .github/skills/scripts/skill-runner.sh test-e2e-playwright-coverage
+   ```
+
+2. Check coverage output:
+   ```bash
+   # View HTML report
+   open coverage/e2e/index.html
+
+   # Check LCOV file exists for Codecov
+   ls -la coverage/e2e/lcov.info
+   ```
+
+3. Verify non-zero coverage:
+   ```bash
+   # Should show real percentages, not "0%"
+   head -20 coverage/e2e/lcov.info
+   ```
+
+### General Guidelines
+
+* **No Truncation**: Never pipe Playwright test output through `head`, `tail`, or other truncating commands. Playwright runs interactively and requires user input to quit when piped, causing the command to hang indefinitely.
 * **Why First**: If the application is broken at the E2E level, unit tests may need updates. Playwright catches integration issues early.
-* **Base URL**: Tests use `PLAYWRIGHT_BASE_URL` env var or default from `playwright.config.js` (Tailscale IP: `http://100.98.12.109:8080`).
 * **On Failure**: Analyze failures, trace root cause through frontend → backend flow, then fix before proceeding to unit tests.
 * **Scope**: Run relevant test files for the feature being modified (e.g., `tests/manual-dns-provider.spec.ts`).
 
@@ -26,5 +185,110 @@ description: 'Strict protocols for test execution, debugging, and coverage valid
 ## 3. Coverage & Completion
 * **Coverage Gate:** A task is not "Complete" until a coverage report is generated.
 * **Threshold Compliance:** You must compare the final coverage percentage against the project's threshold (Default: 85% unless specified otherwise). If coverage drops, you must identify the "uncovered lines" and add targeted tests.
-* **Patch Coverage Gate (Codecov):** If production code is modified, Codecov **patch coverage must be 100%** for the modified lines. Do not relax thresholds; add targeted tests.
-* **Patch Triage Requirement:** Plans must include the exact missing/partial patch line ranges copied from Codecov’s **Patch** view.
+* **Patch Coverage (Suggestion):** Codecov reports patch coverage as an indicator. While developers should aim for 100% coverage of modified lines, patch coverage is **not a hard requirement** and will not block PR approval. If patch coverage is low, consider adding targeted tests to improve the metric.
+* **Review Patch Coverage:** When reviewing patch coverage reports, assess whether missing lines represent genuine gaps or are acceptable (e.g., error handling branches, deprecated code paths). Use the report to inform testing decisions, not as an absolute gate.
+
+## 4. GORM Security Validation (Manual Stage)
+
+**Requirement:** For any change that touches backend models or
+database-related logic, the GORM Security Scanner is a mandatory local DoD gate
+and must pass with zero CRITICAL/HIGH findings.
+
+**Policy vs. Automation Reconciliation:** "Manual stage" describes execution
+mechanism only (not automated pre-commit hook); policy enforcement remains
+process-blocking for DoD. Gate decisions must use check semantics
+(`./scripts/scan-gorm-security.sh --check` or equivalent task wiring).
+
+### When to Run (Conditional Trigger Matrix)
+
+**Mandatory Trigger Paths (Include):**
+- `backend/internal/models/**` — GORM model definitions
+- Backend services/repositories with GORM query logic
+- Database migrations or seeding logic affecting model persistence behavior
+
+**Explicit Exclusions:**
+- Docs-only changes (`**/*.md`, governance documentation)
+- Frontend-only changes (`frontend/**`)
+
+**Gate Decision Rule:** IF any Include path matches, THEN scanner execution in
+check mode is mandatory DoD gate. IF only Exclude paths match, THEN GORM gate
+is not required for that change set.
+
+### Definition of Done
+- **Before Committing:** When modifying trigger paths listed above
+- **Before Opening PR:** Verify no security issues introduced
+- **After Code Review:** If model-related changes were requested
+- **Blocking Gate:** Scanner must pass with zero CRITICAL/HIGH issues before
+   task completion
+
+### Running the Scanner
+
+**Via VS Code (Recommended for Development):**
+1. Open Command Palette (`Cmd/Ctrl+Shift+P`)
+2. Select "Tasks: Run Task"
+3. Choose "Lint: GORM Security Scan"
+
+**Via Pre-commit (Manual Stage):**
+```bash
+# Run on all Go files
+pre-commit run --hook-stage manual gorm-security-scan --all-files
+
+# Run on staged files only
+pre-commit run --hook-stage manual gorm-security-scan
+```
+
+**Direct Execution:**
+```bash
+# Report mode - Show all issues, exit 0 (always)
+./scripts/scan-gorm-security.sh --report
+
+# Check mode - Exit 1 if issues found (use in CI)
+./scripts/scan-gorm-security.sh --check
+```
+
+### Expected Behavior
+
+**Pass (Exit Code 0):**
+- No security issues detected
+- Proceed with commit/PR
+
+**Fail (Exit Code 1):**
+- Issues detected (ID leaks, exposed secrets, DTO embedding, etc.)
+- Review scanner output for file:line references
+- Fix issues before committing
+- See [GORM Security Scanner Documentation](../docs/implementation/gorm_security_scanner_complete.md)
+
+### Common Issues Detected
+
+1. **🔴 CRITICAL: ID Leak** — Numeric ID with `json:"id"` tag
+   - Fix: Change to `json:"-"`, use UUID for external reference
+
+2. **🔴 CRITICAL: Exposed Secret** — APIKey/Token/Password with JSON tag
+   - Fix: Change to `json:"-"` to hide sensitive field
+
+3. **🟡 HIGH: DTO Embedding** — Response struct embeds model with exposed ID
+   - Fix: Use explicit field definitions instead of embedding
+
+### Integration Status
+
+**Current Stage:** Manual (soft launch)
+- Scanner available for manual invocation
+- Does not block commits automatically
+- Developers should run proactively
+
+**Future Stage:** Blocking (after remediation)
+- Scanner will block commits with CRITICAL/HIGH issues
+- CI integration will enforce on all PRs
+- See [GORM Scanner Roadmap](../docs/implementation/gorm_security_scanner_complete.md#remediation-roadmap)
+
+### Performance
+
+- **Execution Time:** ~2 seconds per full scan
+- **Fast enough** for pre-commit use
+- **No impact** on commit workflow when passing
+
+### Documentation
+
+- **Implementation Details:** [docs/implementation/gorm_security_scanner_complete.md](../docs/implementation/gorm_security_scanner_complete.md)
+- **Specification:** [docs/plans/gorm_security_scanner_spec.md](../docs/plans/gorm_security_scanner_spec.md)
+- **QA Report:** [docs/reports/gorm_scanner_qa_report.md](../docs/reports/gorm_scanner_qa_report.md)

.github/instructions/update-docs-on-code-change.instructions.md

@@ -107,6 +107,15 @@ Automatically check if documentation updates are needed when:
 - Installation or setup procedures change
 - Command-line interfaces or scripts are updated
 - Code examples in documentation become outdated
+- **ARCHITECTURE.md must be updated when:**
+  - System architecture or component interactions change
+  - New components are added or removed
+  - Technology stack changes (major version upgrades, library replacements)
+  - Directory structure or organizational conventions change
+  - Deployment model or infrastructure changes
+  - Security architecture or data flow changes
+  - Integration points or external dependencies change
+  - Development workflow or testing strategy changes
 
 ## Documentation Update Rules
 
@@ -219,6 +228,7 @@ If `apply-doc-file-structure == true`, then apply the following configurable ins
 Maintain these documentation files and update as needed:
 
 - **README.md**: Project overview, quick start, basic usage
+- **ARCHITECTURE.md**: System architecture, component design, technology stack, data flow
 - **CHANGELOG.md**: Version history and user-facing changes
 - **docs/**: Detailed documentation
   - `installation.md`: Setup and installation guide

.github/prompts/ai-prompt-engineering-safety-review.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: "Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content."
-agent: 'agent'
+mode: 'agent'
 ---
 
 # AI Prompt Engineering Safety Review & Improvement

.github/prompts/breakdown-feature-implementation.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.'
 ---
 

.github/prompts/codecov-patch-coverage-fix.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Generate targeted tests to achieve 100% Codecov patch coverage when CI reports uncovered lines'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'fetch', 'findTestFiles', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages']
 ---

.github/prompts/create-github-issues-feature-from-implementation-plan.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.'
 tools: ['search/codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
 ---

.github/prompts/create-implementation-plan.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
 ---

.github/prompts/create-technical-spike.prompt.md

@@ -1,7 +1,7 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.'
-tools: ['runCommands', 'runTasks', 'edit', 'search', 'extensions', 'usages', 'vscodeAPI', 'think', 'problems', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'Microsoft Docs', 'search']
+tools: ['runCommands', 'runTasks', 'edit', 'search', 'extensions', 'usages', 'vscodeAPI', 'think', 'problems', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'Microsoft Docs']
 ---
 
 # Create Technical Spike Document

.github/prompts/debug-web-console-errors.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: 'Investigates JavaScript errors, network failures, and warnings from browser DevTools console to identify root causes and implement fixes'
-agent: 'agent'
+mode: 'agent'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'problems', 'search', 'search/searchResults', 'findTestFiles', 'usages', 'runTests']
 ---
 

.github/prompts/playwright-explore-website.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: agent
+mode: agent
 description: 'Website exploration for testing using Playwright MCP'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'fetch', 'findTestFiles', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright']
 model: 'Claude Sonnet 4'

.github/prompts/playwright-generate-test.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: agent
+mode: agent
 description: 'Generate a Playwright test based on a scenario using Playwright MCP'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'fetch', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright/*']
 model: 'Claude Sonnet 4.5'

.github/prompts/prompt-builder.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 tools: ['search/codebase', 'edit/editFiles', 'search']
 description: 'Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices.'
 ---

.github/prompts/sql-code-review.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'problems']
 description: 'Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage.'
 tested_with: 'GitHub Copilot Chat (GPT-4o) - Validated July 20, 2025'

.github/prompts/sql-optimization.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'problems']
 description: 'Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance.'
 tested_with: 'GitHub Copilot Chat (GPT-4o) - Validated July 20, 2025'

.github/prompts/structured-autonomy-generate.prompt.md

@@ -2,7 +2,7 @@
 name: sa-generate
 description: Structured Autonomy Implementation Generator Prompt
 model: GPT-5.1-Codex (Preview) (copilot)
-agent: agent
+mode: agent
 ---
 
 You are a PR implementation plan generator that creates complete, copy-paste ready implementation documentation.

.github/prompts/structured-autonomy-implement.prompt.md

@@ -2,7 +2,7 @@
 name: sa-implement
 description: 'Structured Autonomy Implementation Prompt'
 model: GPT-5 mini (copilot)
-agent: agent
+mode: agent
 ---
 
 You are an implementation agent responsible for carrying out the implementation plan without deviating from it.

.github/prompts/structured-autonomy-plan.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: sa-plan
 description: Structured Autonomy Planning Prompt
-model: Claude Sonnet 4.5 (copilot)]
+model: Claude Sonnet 4.5 (copilot)
 agent: agent
 ---
 

.github/prompts/suggest-awesome-github-copilot-agents.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: "agent"
+mode: "agent"
 description: "Suggest relevant GitHub Copilot Custom Agents files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing custom agents in this repository."
 tools: ["edit", "search", "runCommands", "runTasks", "changes", "testFailure", "openSimpleBrowser", "fetch", "githubRepo", "todos"]
 ---

.github/prompts/suggest-awesome-github-copilot-chatmodes.prompt.md

@@ -1,7 +1,7 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Suggest relevant GitHub Copilot Custom Chat Modes files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing custom chat modes in this repository.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
+tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos']
 ---
 
 # Suggest Awesome GitHub Copilot Custom Chat Modes

.github/prompts/suggest-awesome-github-copilot-collections.prompt.md

@@ -1,7 +1,7 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Suggest relevant GitHub Copilot collections from the awesome-copilot repository based on current repository context and chat history, providing automatic download and installation of collection assets.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
+tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos']
 ---
 # Suggest Awesome GitHub Copilot Collections
 

.github/prompts/suggest-awesome-github-copilot-instructions.prompt.md

@@ -1,7 +1,7 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
+tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos']
 ---
 # Suggest Awesome GitHub Copilot Instructions
 

.github/prompts/suggest-awesome-github-copilot-prompts.prompt.md

@@ -1,7 +1,7 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Suggest relevant GitHub Copilot prompt files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing prompts in this repository.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
+tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos']
 ---
 # Suggest Awesome GitHub Copilot Prompts
 

.github/prompts/supply-chain-vulnerability-remediation.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Research, analyze, and fix vulnerabilities found in supply chain security scans with actionable remediation steps'
 tools: ['search/codebase', 'edit/editFiles', 'fetch', 'runCommands', 'runTasks', 'search', 'problems', 'usages', 'runCommands/terminalLastCommand']
 ---

.github/prompts/update-implementation-plan.prompt.md

@@ -1,5 +1,5 @@
 ---
-agent: 'agent'
+mode: 'agent'
 description: 'Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.'
 tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
 ---

.github/propagate-config.yml

@@ -6,7 +6,11 @@
 sensitive_paths:
   - scripts/history-rewrite/
   - data/backups
-  - docs/plans/history_rewrite.md
-  - .github/workflows/
+  - docs/plans/
+  - .github/agents/
+  - .github/instructions/
+  - .github/prompts/
+  - .github/skills/
+  - .vscode/
   - scripts/history-rewrite/preview_removals.sh
   - scripts/history-rewrite/clean_history.sh

.github/renovate.json

@@ -6,34 +6,52 @@
     ":separateMultipleMajorReleases",
     "helpers:pinGitHubActionDigests"
   ],
-  "baseBranches": [
+  "baseBranchPatterns": [
     "feature/beta-release",
     "development"
   ],
+  "postUpdateOptions": ["npmDedupe"],
   "timezone": "America/New_York",
   "dependencyDashboard": true,
+  "dependencyDashboardApproval": true,
   "prConcurrentLimit": 10,
   "prHourlyLimit": 0,
   "labels": [
     "dependencies"
   ],
 
+  "ignorePaths": [
+    ".docker/**"
+  ],
+
   "rebaseWhen": "auto",
 
   "vulnerabilityAlerts": {
-    "enabled": true
+    "enabled": true,
+    "dependencyDashboardApproval": false,
+    "automerge": false,
+    "labels": ["security", "vulnerability"]
   },
 
-  "schedule": [
-    "before 8am on monday"
-  ],
-
   "rangeStrategy": "bump",
-  "automerge": true,
+  "automerge": false,
   "automergeType": "pr",
   "platformAutomerge": true,
 
   "customManagers": [
+    {
+      "customType": "regex",
+      "description": "Track caddy-security plugin version in Dockerfile",
+      "managerFilePatterns": [
+        "/^Dockerfile$/"
+      ],
+      "matchStrings": [
+        "ARG CADDY_SECURITY_VERSION=(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "github.com/greenpau/caddy-security",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
     {
       "customType": "regex",
       "description": "Track Go dependencies patched in Dockerfile for Caddy CVE fixes",
@@ -45,24 +63,223 @@
       ],
       "datasourceTemplate": "go",
       "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track Alpine base image digest in Dockerfile for security updates",
+      "managerFilePatterns": ["/^Dockerfile$/"],
+      "matchStrings": [
+        "#\\s*renovate:\\s*datasource=docker\\s+depName=alpine.*\\nARG ALPINE_IMAGE=alpine:(?<currentValue>[^@\\s]+)@(?<currentDigest>sha256:[a-f0-9]+)"
+      ],
+      "depNameTemplate": "alpine",
+      "datasourceTemplate": "docker",
+      "versioningTemplate": "docker"
+    },
+    {
+      "customType": "regex",
+      "description": "Track Go toolchain version ARG in Dockerfile",
+      "managerFilePatterns": ["/^Dockerfile$/"],
+      "matchStrings": [
+        "#\\s*renovate:\\s*datasource=docker\\s+depName=golang.*\\nARG GO_VERSION=(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "golang",
+      "datasourceTemplate": "docker",
+      "versioningTemplate": "docker"
+    },
+    {
+      "customType": "regex",
+      "description": "Track expr-lang version ARG in Dockerfile",
+      "managerFilePatterns": ["/^Dockerfile$/"],
+      "matchStrings": [
+        "#\\s*renovate:\\s*datasource=go\\s+depName=github\\.com/expr-lang/expr.*\\nARG EXPR_LANG_VERSION=(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "github.com/expr-lang/expr",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track golang.org/x/net version ARG in Dockerfile",
+      "managerFilePatterns": ["/^Dockerfile$/"],
+      "matchStrings": [
+        "#\\s*renovate:\\s*datasource=go\\s+depName=golang\\.org/x/net.*\\nARG XNET_VERSION=(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "golang.org/x/net",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track Delve version in Dockerfile",
+      "managerFilePatterns": ["/^Dockerfile$/"],
+      "matchStrings": [
+        "ARG DLV_VERSION=(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "github.com/go-delve/delve",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track xcaddy version in Dockerfile",
+      "managerFilePatterns": ["/^Dockerfile$/"],
+      "matchStrings": [
+        "ARG XCADDY_VERSION=(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "github.com/caddyserver/xcaddy",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track gotestsum version in codecov workflow",
+      "managerFilePatterns": [
+        "/^\\.github/workflows/codecov-upload\\.yml$/"
+      ],
+      "matchStrings": [
+        "gotestsum@v(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "gotest.tools/gotestsum",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track gotestsum version in quality checks workflow",
+      "managerFilePatterns": [
+        "/^\\.github/workflows/quality-checks\\.yml$/"
+      ],
+      "matchStrings": [
+        "gotestsum@v(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "gotest.tools/gotestsum",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track govulncheck version in scripts",
+      "managerFilePatterns": ["/^scripts\\/security-scan\\.sh$/"],
+      "matchStrings": [
+        "govulncheck@v(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "golang.org/x/vuln",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track gopls version in Go install script",
+      "managerFilePatterns": ["/^scripts\\/install-go-1\\.25\\.6\\.sh$/"],
+      "matchStrings": [
+        "gopls@v(?<currentValue>[^\\s]+)"
+      ],
+      "depNameTemplate": "golang.org/x/tools",
+      "datasourceTemplate": "go",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track Go toolchain version in go.work for the dl shim",
+      "managerFilePatterns": ["/^go\\.work$/"],
+      "matchStrings": [
+        "^go (?<currentValue>\\d+\\.\\d+\\.\\d+)$"
+      ],
+      "depNameTemplate": "golang/go",
+      "datasourceTemplate": "golang-version",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track GO_VERSION in Actions workflows",
+      "managerFilePatterns": ["/^\\.github/workflows/.*\\.yml$/"],
+      "matchStrings": [
+        "GO_VERSION: ['\"]?(?<currentValue>[\\d\\.]+)['\"]?"
+      ],
+      "depNameTemplate": "golang/go",
+      "datasourceTemplate": "golang-version",
+      "versioningTemplate": "semver"
+    },
+    {
+      "customType": "regex",
+      "description": "Track Syft version in workflows and scripts",
+      "managerFilePatterns": [
+        "/^\\.github/workflows/nightly-build\\.yml$/",
+        "/^\\.github/skills/security-scan-docker-image-scripts/run\\.sh$/"
+      ],
+      "matchStrings": [
+        "SYFT_VERSION=\\\"v(?<currentValue>[^\\\"\\s]+)\\\"",
+        "set_default_env \\\"SYFT_VERSION\\\" \\\"v(?<currentValue>[^\\\"]+)\\\""
+      ],
+      "depNameTemplate": "anchore/syft",
+      "datasourceTemplate": "github-releases",
+      "versioningTemplate": "semver",
+      "extractVersionTemplate": "^v(?<version>.*)$"
+    },
+    {
+      "customType": "regex",
+      "description": "Track Grype version in workflows and scripts",
+      "managerFilePatterns": [
+        "/^\\.github/workflows/supply-chain-pr\\.yml$/",
+        "/^\\.github/skills/security-scan-docker-image-scripts/run\\.sh$/"
+      ],
+      "matchStrings": [
+        "anchore/grype/main/install\\.sh \\| sh -s -- -b /usr/local/bin v(?<currentValue>[0-9]+\\.[0-9]+\\.[0-9]+)",
+        "set_default_env \\\"GRYPE_VERSION\\\" \\\"v(?<currentValue>[^\\\"]+)\\\""
+      ],
+      "depNameTemplate": "anchore/grype",
+      "datasourceTemplate": "github-releases",
+      "versioningTemplate": "semver",
+      "extractVersionTemplate": "^v(?<version>.*)$"
+    },
+    {
+      "customType": "regex",
+      "description": "Track go-version in skill example workflows",
+      "managerFilePatterns": ["/^\\.github/skills/examples/.*\\.yml$/"],
+      "matchStrings": [
+        "go-version: [\"']?(?<currentValue>[\\d\\.]+)[\"']?"
+      ],
+      "depNameTemplate": "golang/go",
+      "datasourceTemplate": "golang-version",
+      "versioningTemplate": "semver"
     }
   ],
 
+  "github-actions": {
+    "managerFilePatterns": [
+      "/^\\.github/skills/examples/.*\\.ya?ml$/"
+    ]
+  },
+
   "packageRules": [
     {
-      "description": "THE MEGAZORD: Group ALL non-major updates (NPM, Docker, Go, Actions) into one weekly PR",
-      "matchPackagePatterns": ["*"],
+      "description": "THE MEGAZORD: Group ALL non-major updates (NPM, Docker, Go, Actions) into one PR",
       "matchUpdateTypes": [
         "minor",
         "patch",
         "pin",
         "digest"
       ],
-      "groupName": "weekly-non-major-updates",
-      "automerge": true
+      "groupName": "non-major-updates",
+      "matchPackageNames": [
+        "*"
+      ]
+    },
+        {
+      "description": "Feature branches: Auto-merge non-major updates after proven stable",
+      "matchBaseBranches": ["feature/**"],
+      "matchUpdateTypes": ["minor", "patch", "pin", "digest"],
+      "automerge": false
     },
     {
-      "description": "Preserve your custom Caddy patch labels but allow them to group into the weekly PR",
+      "description": "Development branch: Auto-merge non-major updates after proven stable",
+      "matchBaseBranches": ["development"],
+      "matchUpdateTypes": ["minor", "patch", "pin", "digest"],
+      "automerge": false,
+      "minimumReleaseAge": "14 days"
+    },
+    {
+      "description": "Preserve your custom Caddy patch labels but allow them to group into a single PR",
       "matchManagers": ["custom.regex"],
       "matchFileNames": ["Dockerfile"],
       "labels": ["caddy-patch", "security"],
@@ -78,11 +295,41 @@
       "matchPackageNames": ["caddy"],
       "allowedVersions": "<3.0.0"
     },
+    {
+      "description": "Go: keep pgx within v4 (CrowdSec requires pgx/v4 module path)",
+      "matchDatasources": ["go"],
+      "matchPackageNames": ["github.com/jackc/pgx/v4"],
+      "allowedVersions": "<5.0.0"
+    },
+    {
+      "description": "Go: keep go-jose/v3 within v3 (v4 is a different Go module path)",
+      "matchDatasources": ["go"],
+      "matchPackageNames": ["github.com/go-jose/go-jose/v3"],
+      "allowedVersions": "<4.0.0"
+    },
+    {
+      "description": "Go: keep go-jose/v4 within v4 (v5 would be a different Go module path)",
+      "matchDatasources": ["go"],
+      "matchPackageNames": ["github.com/go-jose/go-jose/v4"],
+      "allowedVersions": "<5.0.0"
+    },
     {
       "description": "Safety: Keep MAJOR updates separate and require manual review",
       "matchUpdateTypes": ["major"],
       "automerge": false,
       "labels": ["manual-review"]
+    },
+    {
+      "description": "Fix Renovate lookup for geoip2-golang v2 module path",
+      "matchDatasources": ["go"],
+      "matchPackageNames": ["github.com/oschwald/geoip2-golang/v2"],
+      "sourceUrl": "https://github.com/oschwald/geoip2-golang"
+    },
+    {
+      "description": "Fix Renovate lookup for google/uuid",
+      "matchDatasources": ["go"],
+      "matchPackageNames": ["github.com/google/uuid"],
+      "sourceUrl": "https://github.com/google/uuid"
     }
   ]
 }

.github/security-severity-policy.yml

@@ -0,0 +1,55 @@
+version: 1
+effective_date: 2026-02-25
+scope:
+  - local pre-commit manual security hooks
+  - github actions security workflows
+
+defaults:
+  blocking:
+    - critical
+    - high
+  medium:
+    mode: risk-based
+    default_action: report
+    require_sla: true
+    default_sla_days: 14
+    escalation:
+      trigger: high-signal class or repeated finding
+      action: require issue + owner + due date
+  low:
+    action: report
+
+codeql:
+  severity_mapping:
+    error: high_or_critical
+    warning: medium_or_lower
+    note: informational
+  blocking_levels:
+    - error
+  warning_policy:
+    default_action: report
+    escalation_high_signal_rule_ids:
+      - go/request-forgery
+      - js/missing-rate-limiting
+      - js/insecure-randomness
+
+trivy:
+  blocking_severities:
+    - CRITICAL
+    - HIGH
+  medium_policy:
+    action: report
+    escalation: issue-with-sla
+
+grype:
+  blocking_severities:
+    - Critical
+    - High
+  medium_policy:
+    action: report
+    escalation: issue-with-sla
+
+enforcement_contract:
+  codeql_local_vs_ci: "local and ci block on codeql error-level findings only"
+  supply_chain_medium: "medium vulnerabilities are non-blocking by default and require explicit triage"
+  auth_regression_guard: "state-changing routes must remain protected by auth middleware"

.github/skills/.skill-quickref-gorm-scanner.md

@@ -0,0 +1,168 @@
+# GORM Security Scanner - Quick Reference
+
+## Purpose
+Detect GORM security issues including ID leaks, exposed secrets, and common GORM misconfigurations.
+
+## Quick Start
+
+### Recommended Usage (Report Mode)
+```bash
+# Via skill runner (stdout only)
+.github/skills/scripts/skill-runner.sh security-scan-gorm
+
+# Via skill runner (save report for agents/later review)
+.github/skills/scripts/skill-runner.sh security-scan-gorm --report docs/reports/gorm-scan.txt
+
+# Via VS Code task
+Command Palette → Tasks: Run Task → "Lint: GORM Security Scan"
+
+# Via pre-commit (manual stage)
+pre-commit run --hook-stage manual gorm-security-scan --all-files
+```
+
+### Check Mode (CI/Pre-commit)
+```bash
+# Exit 1 if issues found (console output only)
+.github/skills/scripts/skill-runner.sh security-scan-gorm --check
+
+# Exit 1 if issues found (save report as CI artifact)
+.github/skills/scripts/skill-runner.sh security-scan-gorm --check docs/reports/gorm-scan-ci.txt
+```
+
+### Why Export Reports?
+
+**Benefits:**
+- ✅ **Agent-Friendly**: AI agents can read files instead of parsing terminal history
+- ✅ **Persistence**: Results saved for later review and comparison
+- ✅ **CI/CD**: Upload as GitHub Actions artifacts for audit trail
+- ✅ **Tracking**: Compare reports over time to track remediation progress
+- ✅ **Compliance**: Evidence of security scans for audits
+
+**Example Agent Usage:**
+```bash
+# User/Agent generates report
+.github/skills/scripts/skill-runner.sh security-scan-gorm --report docs/reports/gorm-scan.txt
+
+# Agent reads the report file to analyze findings
+# File: docs/reports/gorm-scan.txt contains:
+# - Severity breakdown (CRITICAL, HIGH, MEDIUM, INFO)
+# - File:line references for each issue
+# - Remediation guidance
+# - Summary metrics
+```
+
+## Detection Patterns
+
+| Severity | Pattern | Example |
+|----------|---------|---------|
+| 🔴 CRITICAL | Numeric ID exposure | `ID uint json:"id"` → should be `json:"-"` |
+| 🔴 CRITICAL | Exposed secrets | `APIKey string json:"api_key"` → should be `json:"-"` |
+| 🟡 HIGH | DTO embedding models | `ProxyHostResponse embeds models.ProxyHost` |
+| 🔵 MEDIUM | Missing primary key tag | `ID uint` without `gorm:"primaryKey"` |
+| 🟢 INFO | Missing FK index | `UserID uint` without `gorm:"index"` |
+
+## Common Fixes
+
+### Fix ID Leak
+```go
+// Before
+type User struct {
+    ID   uint   `json:"id" gorm:"primaryKey"`
+    UUID string `json:"uuid"`
+}
+
+// After
+type User struct {
+    ID   uint   `json:"-" gorm:"primaryKey"`        // Hidden
+    UUID string `json:"uuid" gorm:"uniqueIndex"`    // Use this
+}
+```
+
+### Fix Exposed Secret
+```go
+// Before
+type User struct {
+    APIKey string `json:"api_key"`
+}
+
+// After
+type User struct {
+    APIKey string `json:"-"`  // Never expose
+}
+```
+
+### Fix DTO Embedding
+```go
+// Before
+type ProxyHostResponse struct {
+    models.ProxyHost  // Inherits exposed ID
+    Warnings []string
+}
+
+// After
+type ProxyHostResponse struct {
+    UUID        string   `json:"uuid"`        // Explicit only
+    Name        string   `json:"name"`
+    DomainNames string   `json:"domain_names"`
+    Warnings    []string `json:"warnings"`
+}
+```
+
+## Suppression
+
+Use when false positive or intentional exception:
+
+```go
+// gorm-scanner:ignore External API response, not a GORM model
+type GitHubUser struct {
+    ID int `json:"id"`
+}
+```
+
+## Performance
+
+- **Execution Time:** ~2 seconds
+- **Files Scanned:** 40 Go files
+- **Fast enough for:** Pre-commit hooks
+
+## Exit Codes
+
+- **0:** Success (report mode) or no issues (check/enforce)
+- **1:** Issues found (check/enforce modes)
+- **2:** Invalid arguments
+- **3:** File system error
+
+## Integration Points
+
+- ✅ VS Code Task: "Lint: GORM Security Scan"
+- ✅ Pre-commit: Manual stage (soft launch)
+- ✅ CI/CD: GitHub Actions quality-checks workflow
+- ✅ Definition of Done: Required check
+
+## Documentation
+
+- **Full Skill:** [security-scan-gorm.SKILL.md](./security-scan-gorm.SKILL.md)
+- **Specification:** [docs/plans/gorm_security_scanner_spec.md](../../docs/plans/gorm_security_scanner_spec.md)
+- **Implementation:** [docs/implementation/gorm_security_scanner_complete.md](../../docs/implementation/gorm_security_scanner_complete.md)
+
+## Security Rationale
+
+**Why ID leaks matter:**
+- Information disclosure (sequential patterns)
+- IDOR vulnerability (guess valid IDs)
+- Database structure exposure
+- Attack surface increase
+
+**Best Practice:** Use UUIDs for external references, hide internal numeric IDs.
+
+## Status
+
+**Production Ready:** ✅ Yes (2026-01-28)
+**QA Approved:** ✅ 100% (16/16 tests passed)
+**False Positive Rate:** 0%
+**False Negative Rate:** 0%
+
+---
+
+**Last Updated:** 2026-01-28
+**Maintained by:** Charon Project

.github/skills/README.md

@@ -37,6 +37,9 @@ Agent Skills are self-documenting, AI-discoverable task definitions that combine
 | [test-backend-unit](./test-backend-unit.SKILL.md) | test | Run fast Go unit tests without coverage | ✅ Active |
 | [test-frontend-coverage](./test-frontend-coverage.SKILL.md) | test | Run frontend tests with coverage reporting | ✅ Active |
 | [test-frontend-unit](./test-frontend-unit.SKILL.md) | test | Run fast frontend unit tests without coverage | ✅ Active |
+| [test-e2e-playwright](./test-e2e-playwright.SKILL.md) | test | Run Playwright E2E tests with browser selection | ✅ Active |
+| [test-e2e-playwright-debug](./test-e2e-playwright-debug.SKILL.md) | test | Run E2E tests in headed/debug mode for troubleshooting | ✅ Active |
+| [test-e2e-playwright-coverage](./test-e2e-playwright-coverage.SKILL.md) | test | Run E2E tests with coverage collection | ✅ Active |
 
 ### Integration Testing Skills
 
@@ -52,6 +55,7 @@ Agent Skills are self-documenting, AI-discoverable task definitions that combine
 
 | Skill Name | Category | Description | Status |
 |------------|----------|-------------|--------|
+| [security-scan-gorm](./security-scan-gorm.SKILL.md) | security | Detect GORM ID leaks, exposed secrets, and misconfigurations | ✅ Active |
 | [security-scan-trivy](./security-scan-trivy.SKILL.md) | security | Run Trivy vulnerability scanner | ✅ Active |
 | [security-scan-go-vuln](./security-scan-go-vuln.SKILL.md) | security | Run Go vulnerability check | ✅ Active |
 
@@ -59,7 +63,7 @@ Agent Skills are self-documenting, AI-discoverable task definitions that combine
 
 | Skill Name | Category | Description | Status |
 |------------|----------|-------------|--------|
-| [qa-precommit-all](./qa-precommit-all.SKILL.md) | qa | Run all pre-commit hooks on entire codebase | ✅ Active |
+| [qa-lefthook-all](./qa-lefthook-all.SKILL.md) | qa | Run all lefthook pre-commit‑phase hooks on entire codebase | ✅ Active |
 
 ### Utility Skills
 
@@ -76,6 +80,7 @@ Agent Skills are self-documenting, AI-discoverable task definitions that combine
 |------------|----------|-------------|--------|
 | [docker-start-dev](./docker-start-dev.SKILL.md) | docker | Start development Docker Compose environment | ✅ Active |
 | [docker-stop-dev](./docker-stop-dev.SKILL.md) | docker | Stop development Docker Compose environment | ✅ Active |
+| [docker-rebuild-e2e](./docker-rebuild-e2e.SKILL.md) | docker | Rebuild Docker image and restart E2E Playwright container | ✅ Active |
 | [docker-prune](./docker-prune.SKILL.md) | docker | Clean up unused Docker resources | ✅ Active |
 
 ## Usage

.github/skills/docker-rebuild-e2e-scripts/run.sh

@@ -0,0 +1,314 @@
+#!/usr/bin/env bash
+# Docker: Rebuild E2E Environment - Execution Script
+#
+# Rebuilds the Docker image and restarts the Playwright E2E testing
+# environment with fresh code and optionally clean state.
+
+set -euo pipefail
+
+# Source helper scripts
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+SKILLS_SCRIPTS_DIR="$(cd "${SCRIPT_DIR}/../scripts" && pwd)"
+
+# shellcheck source=../scripts/_logging_helpers.sh
+source "${SKILLS_SCRIPTS_DIR}/_logging_helpers.sh"
+# shellcheck source=../scripts/_error_handling_helpers.sh
+source "${SKILLS_SCRIPTS_DIR}/_error_handling_helpers.sh"
+# shellcheck source=../scripts/_environment_helpers.sh
+source "${SKILLS_SCRIPTS_DIR}/_environment_helpers.sh"
+
+# Project root is 3 levels up from this script
+PROJECT_ROOT="$(cd "${SCRIPT_DIR}/../../.." && pwd)"
+
+# Docker compose file for Playwright E2E tests
+COMPOSE_FILE=".docker/compose/docker-compose.playwright-local.yml"
+CONTAINER_NAME="charon-e2e"
+IMAGE_NAME="charon:local"
+HEALTH_TIMEOUT=60
+HEALTH_INTERVAL=5
+
+# Default parameter values
+NO_CACHE=false
+CLEAN=false
+PROFILE=""
+
+# Parse command-line arguments
+parse_arguments() {
+    while [[ $# -gt 0 ]]; do
+        case "$1" in
+            --no-cache)
+                NO_CACHE=true
+                shift
+                ;;
+            --clean)
+                CLEAN=true
+                shift
+                ;;
+            --profile=*)
+                PROFILE="${1#*=}"
+                shift
+                ;;
+            --profile)
+                PROFILE="${2:-}"
+                shift 2
+                ;;
+            -h|--help)
+                show_help
+                exit 0
+                ;;
+            *)
+                log_warning "Unknown argument: $1"
+                shift
+                ;;
+        esac
+    done
+}
+
+# Show help message
+show_help() {
+    cat << EOF
+Usage: run.sh [OPTIONS]
+
+Rebuild Docker image and restart E2E Playwright container.
+
+Options:
+    --no-cache          Force rebuild without Docker cache
+    --clean             Remove test volumes for fresh state
+    --profile=PROFILE   Docker Compose profile to enable
+                        (security-tests, notification-tests)
+    -h, --help          Show this help message
+
+Environment Variables:
+    DOCKER_NO_CACHE         Force rebuild without cache (default: false)
+    SKIP_VOLUME_CLEANUP     Preserve test data volumes (default: false)
+
+Examples:
+    run.sh                              # Standard rebuild
+    run.sh --no-cache                   # Force complete rebuild
+    run.sh --clean                      # Rebuild with fresh volumes
+    run.sh --profile=security-tests     # Enable CrowdSec for testing
+    run.sh --no-cache --clean           # Complete fresh rebuild
+EOF
+}
+
+# Stop existing containers
+stop_containers() {
+    log_step "STOP" "Stopping existing E2E containers"
+
+    local compose_cmd="docker compose -f ${COMPOSE_FILE}"
+
+    # Add profile if specified
+    if [[ -n "${PROFILE}" ]]; then
+        compose_cmd="${compose_cmd} --profile ${PROFILE}"
+    fi
+
+    # Stop and remove containers
+    if ${compose_cmd} ps -q 2>/dev/null | grep -q .; then
+        log_info "Stopping containers..."
+        ${compose_cmd} down --remove-orphans || true
+    else
+        log_info "No running containers to stop"
+    fi
+}
+
+# Clean volumes if requested
+clean_volumes() {
+    if [[ "${CLEAN}" != "true" ]]; then
+        return 0
+    fi
+
+    if [[ "${SKIP_VOLUME_CLEANUP:-false}" == "true" ]]; then
+        log_warning "Skipping volume cleanup (SKIP_VOLUME_CLEANUP=true)"
+        return 0
+    fi
+
+    log_step "CLEAN" "Removing test volumes"
+
+    local volumes=(
+        "playwright_data"
+        "playwright_caddy_data"
+        "playwright_caddy_config"
+        "playwright_crowdsec_data"
+        "playwright_crowdsec_config"
+    )
+
+    for vol in "${volumes[@]}"; do
+        # Try both prefixed and unprefixed volume names
+        for prefix in "compose_" ""; do
+            local full_name="${prefix}${vol}"
+            if docker volume inspect "${full_name}" &>/dev/null; then
+                log_info "Removing volume: ${full_name}"
+                docker volume rm "${full_name}" || true
+            fi
+        done
+    done
+
+    log_success "Volumes cleaned"
+}
+
+# Build Docker image
+build_image() {
+    log_step "BUILD" "Building Docker image: ${IMAGE_NAME}"
+
+    local build_args=("-t" "${IMAGE_NAME}" ".")
+
+    if [[ "${NO_CACHE}" == "true" ]] || [[ "${DOCKER_NO_CACHE:-false}" == "true" ]]; then
+        log_info "Building with --no-cache"
+        build_args=("--no-cache" "${build_args[@]}")
+    fi
+
+    log_command "docker build ${build_args[*]}"
+
+    if ! docker build "${build_args[@]}"; then
+        error_exit "Docker build failed"
+    fi
+
+    log_success "Image built successfully: ${IMAGE_NAME}"
+}
+
+# Start containers
+start_containers() {
+    log_step "START" "Starting E2E containers"
+
+    local compose_cmd="docker compose -f ${COMPOSE_FILE}"
+
+    # Add profile if specified
+    if [[ -n "${PROFILE}" ]]; then
+        log_info "Enabling profile: ${PROFILE}"
+        compose_cmd="${compose_cmd} --profile ${PROFILE}"
+    fi
+
+    log_command "${compose_cmd} up -d"
+
+    if ! ${compose_cmd} up -d; then
+        error_exit "Failed to start containers"
+    fi
+
+    log_success "Containers started"
+}
+
+# Wait for container health
+wait_for_health() {
+    log_step "HEALTH" "Waiting for container to be healthy"
+
+    local elapsed=0
+    local healthy=false
+
+    while [[ ${elapsed} -lt ${HEALTH_TIMEOUT} ]]; do
+        local health_status
+        health_status=$(docker inspect --format='{{.State.Health.Status}}' "${CONTAINER_NAME}" 2>/dev/null || echo "unknown")
+
+        case "${health_status}" in
+            healthy)
+                healthy=true
+                break
+                ;;
+            unhealthy)
+                log_error "Container is unhealthy"
+                docker logs "${CONTAINER_NAME}" --tail 20
+                error_exit "Container health check failed"
+                ;;
+            starting)
+                log_info "Health status: starting (${elapsed}s/${HEALTH_TIMEOUT}s)"
+                ;;
+            *)
+                log_info "Health status: ${health_status} (${elapsed}s/${HEALTH_TIMEOUT}s)"
+                ;;
+        esac
+
+        sleep "${HEALTH_INTERVAL}"
+        elapsed=$((elapsed + HEALTH_INTERVAL))
+    done
+
+    if [[ "${healthy}" != "true" ]]; then
+        log_error "Container did not become healthy in ${HEALTH_TIMEOUT}s"
+        docker logs "${CONTAINER_NAME}" --tail 50
+        error_exit "Health check timeout"
+    fi
+
+    log_success "Container is healthy"
+}
+
+# Verify environment
+verify_environment() {
+    log_step "VERIFY" "Verifying E2E environment"
+
+    # Check container is running
+    if ! docker ps --filter "name=${CONTAINER_NAME}" --format "{{.Names}}" | grep -q "${CONTAINER_NAME}"; then
+        error_exit "Container ${CONTAINER_NAME} is not running"
+    fi
+
+    # Test health endpoint
+    log_info "Testing health endpoint..."
+    if curl -sf http://localhost:8080/api/v1/health &>/dev/null; then
+        log_success "Health endpoint responding"
+    else
+        log_warning "Health endpoint not responding (may need more time)"
+    fi
+
+    # Show container status
+    log_info "Container status:"
+    docker ps --filter "name=${CONTAINER_NAME}" --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
+}
+
+# Show summary
+show_summary() {
+    log_step "SUMMARY" "E2E environment ready"
+
+    echo ""
+    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+    echo "  E2E Environment Ready"
+    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+    echo ""
+    echo "  Application URL:  http://localhost:8080"
+    echo "  Health Check:     http://localhost:8080/api/v1/health"
+    echo "  Container:        ${CONTAINER_NAME}"
+    echo ""
+    echo "  Run E2E tests:"
+    echo "    .github/skills/scripts/skill-runner.sh test-e2e-playwright"
+    echo ""
+    echo "  Run in debug mode:"
+    echo "    .github/skills/scripts/skill-runner.sh test-e2e-playwright-debug"
+    echo ""
+    echo "  View logs:"
+    echo "    docker logs ${CONTAINER_NAME} -f"
+    echo ""
+    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+}
+
+# Main execution
+main() {
+    parse_arguments "$@"
+
+    # Validate environment
+    log_step "ENVIRONMENT" "Validating prerequisites"
+    validate_docker_environment || error_exit "Docker is not available"
+    check_command_exists "docker" "Docker is required"
+
+    # Validate project structure
+    log_step "VALIDATION" "Checking project structure"
+    cd "${PROJECT_ROOT}"
+    check_file_exists "Dockerfile" "Dockerfile is required"
+    check_file_exists "${COMPOSE_FILE}" "Playwright compose file is required"
+
+    # Log configuration
+    log_step "CONFIG" "Rebuild configuration"
+    log_info "No cache: ${NO_CACHE}"
+    log_info "Clean volumes: ${CLEAN}"
+    log_info "Profile: ${PROFILE:-<none>}"
+    log_info "Compose file: ${COMPOSE_FILE}"
+
+    # Execute rebuild steps
+    stop_containers
+    clean_volumes
+    build_image
+    start_containers
+    wait_for_health
+    verify_environment
+    show_summary
+
+    log_success "E2E environment rebuild complete"
+}
+
+# Run main with all arguments
+main "$@"

.github/skills/docker-rebuild-e2e.SKILL.md

@@ -0,0 +1,303 @@
+---
+# agentskills.io specification v1.0
+name: "docker-rebuild-e2e"
+version: "1.0.0"
+description: "Rebuild Docker image and restart E2E Playwright container with fresh code and clean state"
+author: "Charon Project"
+license: "MIT"
+tags:
+  - "docker"
+  - "e2e"
+  - "playwright"
+  - "rebuild"
+  - "testing"
+compatibility:
+  os:
+    - "linux"
+    - "darwin"
+  shells:
+    - "bash"
+requirements:
+  - name: "docker"
+    version: ">=24.0"
+    optional: false
+  - name: "docker-compose"
+    version: ">=2.0"
+    optional: false
+environment_variables:
+  - name: "DOCKER_NO_CACHE"
+    description: "Set to 'true' to force a complete rebuild without cache"
+    default: "false"
+    required: false
+  - name: "SKIP_VOLUME_CLEANUP"
+    description: "Set to 'true' to preserve test data volumes"
+    default: "false"
+    required: false
+parameters:
+  - name: "no-cache"
+    type: "boolean"
+    description: "Force rebuild without Docker cache"
+    default: "false"
+    required: false
+  - name: "clean"
+    type: "boolean"
+    description: "Remove test volumes for a completely fresh state"
+    default: "false"
+    required: false
+  - name: "profile"
+    type: "string"
+    description: "Docker Compose profile to enable (security-tests, notification-tests)"
+    default: ""
+    required: false
+outputs:
+  - name: "exit_code"
+    type: "integer"
+    description: "0 on success, non-zero on failure"
+metadata:
+  category: "docker"
+  subcategory: "e2e"
+  execution_time: "long"
+  risk_level: "low"
+  ci_cd_safe: true
+  requires_network: true
+  idempotent: true
+---
+
+# Docker: Rebuild E2E Environment
+
+## Overview
+
+Rebuilds the Charon Docker image and restarts the Playwright E2E testing environment with fresh code. This skill handles the complete lifecycle: stopping existing containers, optionally cleaning volumes, rebuilding the image, and starting fresh containers with health check verification.
+
+**Use this skill when:**
+- You've made code changes and need to test them in E2E tests
+- E2E tests are failing due to stale container state
+- You need a clean slate for debugging
+- The container is in an inconsistent state
+
+## Prerequisites
+
+- Docker Engine installed and running
+- Docker Compose V2 installed
+- Dockerfile in repository root
+  - `.docker/compose/docker-compose.playwright-ci.yml` file (used in CI)
+- Network access for pulling base images (if needed)
+- Sufficient disk space for image rebuild
+
+## Usage
+
+### Basic Usage
+
+Rebuild image and restart E2E container:
+
+```bash
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e
+```
+
+### Force Rebuild (No Cache)
+
+Rebuild from scratch without Docker cache:
+
+```bash
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e --no-cache
+```
+
+### Clean Rebuild
+
+Remove test volumes and rebuild with fresh state:
+
+```bash
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e --clean
+```
+
+### With Security Testing Services
+
+Enable CrowdSec for security testing:
+
+```bash
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e --profile=security-tests
+```
+
+### With Notification Testing Services
+
+Enable MailHog for email testing:
+
+```bash
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e --profile=notification-tests
+```
+
+### Full Clean Rebuild with All Services
+
+```bash
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e --no-cache --clean --profile=security-tests
+```
+
+## Parameters
+
+| Parameter | Type | Required | Default | Description |
+|-----------|------|----------|---------|-------------|
+| no-cache  | boolean | No | false | Force rebuild without Docker cache |
+| clean     | boolean | No | false | Remove test volumes for fresh state |
+| profile   | string | No | "" | Docker Compose profile to enable |
+
+## Environment Variables
+
+| Variable | Required | Default | Description |
+|----------|----------|---------|-------------|
+| DOCKER_NO_CACHE | No | false | Force rebuild without cache |
+| SKIP_VOLUME_CLEANUP | No | false | Preserve test data volumes |
+
+## What This Skill Does
+
+1. **Stop Existing Containers**: Gracefully stops any running Playwright containers
+2. **Clean Volumes** (if `--clean`): Removes test data volumes for fresh state
+3. **Rebuild Image**: Builds `charon:local` image from Dockerfile
+4. **Start Containers**: Starts the Playwright compose environment
+5. **Wait for Health**: Verifies container health before returning
+6. **Report Status**: Outputs container status and connection info
+
+## Docker Compose Configuration
+
+This skill uses `.docker/compose/docker-compose.playwright-ci.yml` which includes:
+
+- **charon-app**: Main application container on port 8080
+- **crowdsec** (profile: security-tests): Security bouncer for WAF testing
+- **mailhog** (profile: notification-tests): Email testing service
+
+### Volumes Created
+
+| Volume | Purpose |
+|--------|---------|
+| playwright_data | Application data and SQLite database |
+| playwright_caddy_data | Caddy server data |
+| playwright_caddy_config | Caddy configuration |
+| playwright_crowdsec_data | CrowdSec data (if enabled) |
+| playwright_crowdsec_config | CrowdSec config (if enabled) |
+
+## Examples
+
+### Example 1: Quick Rebuild After Code Change
+
+```bash
+# Rebuild and restart after making backend changes
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e
+
+# Run E2E tests
+.github/skills/scripts/skill-runner.sh test-e2e-playwright
+```
+
+### Example 2: Debug Failing Tests with Clean State
+
+```bash
+# Complete clean rebuild
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e --clean --no-cache
+
+# Run specific test in debug mode
+.github/skills/scripts/skill-runner.sh test-e2e-playwright-debug --grep="failing-test"
+```
+
+### Example 3: Test Security Features
+
+```bash
+# Start with CrowdSec enabled
+.github/skills/scripts/skill-runner.sh docker-rebuild-e2e --profile=security-tests
+
+# Run security-related E2E tests
+.github/skills/scripts/skill-runner.sh test-e2e-playwright --grep="security"
+```
+
+## Health Check Verification
+
+After starting, the skill waits for the health check to pass:
+
+```bash
+# Health endpoint checked
+curl -sf http://localhost:8080/api/v1/health
+```
+
+The skill will:
+- Wait up to 60 seconds for container to be healthy
+- Check every 5 seconds
+- Report final health status
+- Exit with error if health check fails
+
+## Error Handling
+
+### Common Issues
+
+#### Docker Build Failed
+```
+Error: docker build failed
+```
+**Solution**: Check Dockerfile syntax, ensure all COPY sources exist
+
+#### Port Already in Use
+```
+Error: bind: address already in use
+```
+**Solution**: Stop conflicting services on port 8080
+
+#### Health Check Timeout
+```
+Error: Container did not become healthy in 60s
+```
+**Solution**: Check container logs with `docker logs charon-playwright`
+
+#### Volume Permission Issues
+```
+Error: permission denied
+```
+**Solution**: Run with `--clean` to recreate volumes with proper permissions
+
+## Verifying the Environment
+
+After the skill completes, verify the environment:
+
+```bash
+# Check container status
+docker ps --filter "name=charon-playwright"
+
+# Check logs
+docker logs charon-playwright --tail 50
+
+# Test health endpoint
+curl http://localhost:8080/api/v1/health
+
+# Check database state
+docker exec charon-playwright sqlite3 /app/data/charon.db ".tables"
+```
+
+## Related Skills
+
+- [test-e2e-playwright](./test-e2e-playwright.SKILL.md) - Run E2E tests
+- [test-e2e-playwright-debug](./test-e2e-playwright-debug.SKILL.md) - Debug E2E tests
+- [docker-start-dev](./docker-start-dev.SKILL.md) - Start development environment
+- [docker-stop-dev](./docker-stop-dev.SKILL.md) - Stop development environment
+- [docker-prune](./docker-prune.SKILL.md) - Clean up Docker resources
+
+## Key File Locations
+
+| File | Purpose |
+|------|---------|
+| `Dockerfile` | Main application Dockerfile |
+| `.docker/compose/docker-compose.playwright-ci.yml` | CI E2E test compose config |
+| `.docker/compose/docker-compose.playwright-local.yml` | Local E2E test compose config |
+| `playwright.config.js` | Playwright test configuration |
+| `tests/` | E2E test files |
+| `playwright/.auth/user.json` | Stored authentication state |
+
+## Notes
+
+- **Build Time**: Full rebuild takes 2-5 minutes depending on cache
+- **Disk Space**: Image is ~500MB, volumes add ~100MB
+- **Network**: Base images may need to be pulled on first run
+- **Idempotent**: Safe to run multiple times
+- **CI/CD Safe**: Designed for use in automated pipelines
+
+---
+
+**Last Updated**: 2026-01-27
+**Maintained by**: Charon Project Team
+**Compose Files**:
+- CI: `.docker/compose/docker-compose.playwright-ci.yml` (uses GitHub Secrets, no .env)
+- Local: `.docker/compose/docker-compose.playwright-local.yml` (uses .env file)

.github/skills/examples/gorm-scanner-ci-workflow.yml

@@ -0,0 +1,124 @@
+# Example GitHub Actions Workflow - GORM Security Scanner with Report Artifacts
+# This demonstrates how to use the GORM scanner skill in CI/CD with report export
+
+name: GORM Security Scan
+
+on:
+  pull_request:
+    paths:
+      - 'backend/**/*.go'
+      - 'backend/go.mod'
+  push:
+    branches:
+      - main
+      - development
+
+jobs:
+  gorm-security-scan:
+    name: GORM Security Analysis
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+
+      - name: Setup Go
+        uses: actions/setup-go@4a3601121dd01d1626a1e23e37211e3254c1c06c # v6
+        with:
+          go-version: "1.26.2"
+
+      - name: Run GORM Security Scanner
+        id: gorm-scan
+        run: |
+          # Generate report file for artifact upload
+          .github/skills/scripts/skill-runner.sh security-scan-gorm \
+            --check \
+            docs/reports/gorm-scan-ci-${{ github.run_id }}.txt
+        continue-on-error: true
+
+      - name: Parse Report for PR Comment
+        if: always() && github.event_name == 'pull_request'
+        id: parse-report
+        run: |
+          REPORT_FILE="docs/reports/gorm-scan-ci-${{ github.run_id }}.txt"
+
+          # Extract summary metrics
+          CRITICAL=$(grep -oP '🔴 CRITICAL: \K\d+' "$REPORT_FILE" || echo "0")
+          HIGH=$(grep -oP '🟡 HIGH: \K\d+' "$REPORT_FILE" || echo "0")
+          MEDIUM=$(grep -oP '🔵 MEDIUM: \K\d+' "$REPORT_FILE" || echo "0")
+          INFO=$(grep -oP '🟢 INFO: \K\d+' "$REPORT_FILE" || echo "0")
+
+          # Create summary for PR comment
+          echo "critical=$CRITICAL" >> $GITHUB_OUTPUT
+          echo "high=$HIGH" >> $GITHUB_OUTPUT
+          echo "medium=$MEDIUM" >> $GITHUB_OUTPUT
+          echo "info=$INFO" >> $GITHUB_OUTPUT
+
+      - name: Comment on PR
+        if: always() && github.event_name == 'pull_request'
+        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9
+        with:
+          script: |
+            const critical = ${{ steps.parse-report.outputs.critical }};
+            const high = ${{ steps.parse-report.outputs.high }};
+            const medium = ${{ steps.parse-report.outputs.medium }};
+            const info = ${{ steps.parse-report.outputs.info }};
+
+            const status = (critical > 0 || high > 0) ? '❌' : '✅';
+            const message = `## ${status} GORM Security Scan Results
+
+            | Severity | Count |
+            |----------|-------|
+            | 🔴 CRITICAL | ${critical} |
+            | 🟡 HIGH | ${high} |
+            | 🔵 MEDIUM | ${medium} |
+            | 🟢 INFO | ${info} |
+
+            **Total Issues:** ${critical + high + medium} (excluding informational)
+
+            ${critical > 0 || high > 0 ? '⚠️ **Action Required:** Fix CRITICAL/HIGH issues before merge.' : '✅ No critical issues found.'}
+
+            📄 Full report available in workflow artifacts.`;
+
+            github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: message
+            });
+
+      - name: Upload GORM Scan Report
+        if: always()
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
+        with:
+          name: gorm-security-report-${{ github.run_id }}
+          path: docs/reports/gorm-scan-ci-*.txt
+          retention-days: 30
+          if-no-files-found: error
+
+      - name: Fail Build on Critical Issues
+        if: steps.gorm-scan.outcome == 'failure'
+        run: |
+          echo "::error title=GORM Security Issues::Critical security issues detected. See report artifact for details."
+          exit 1
+
+# Usage in other workflows:
+#
+# 1. Download previous report for comparison:
+#    - uses: actions/download-artifact@v4
+#      with:
+#        name: gorm-security-report-previous
+#        path: reports/previous/
+#
+# 2. Compare reports:
+#    - run: |
+#        diff reports/previous/gorm-scan-ci-*.txt \
+#             docs/reports/gorm-scan-ci-*.txt \
+#             || echo "Issues changed"
+#
+# 3. AI Agent Analysis:
+#    - name: Analyze with AI
+#      run: |
+#        # AI agent reads the report file
+#        REPORT=$(cat docs/reports/gorm-scan-ci-*.txt)
+#        # Process findings, suggest fixes, create issues, etc.

.github/skills/integration-test-all-scripts/run.sh

@@ -2,10 +2,9 @@
 set -euo pipefail
 
 # Integration Test All - Wrapper Script
-# Executes the comprehensive integration test suite
+# Executes the canonical integration test suite aligned with CI workflows
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PROJECT_ROOT="$(cd "${SCRIPT_DIR}/../../.." && pwd)"
 
-# Delegate to the existing integration test script
-exec "${PROJECT_ROOT}/scripts/integration-test.sh" "$@"
+exec bash "${PROJECT_ROOT}/scripts/integration-test-all.sh" "$@"

.github/skills/integration-test-all.SKILL.md

@@ -2,7 +2,7 @@
 # agentskills.io specification v1.0
 name: "integration-test-all"
 version: "1.0.0"
-description: "Run all integration tests including WAF, CrowdSec, Cerberus, and rate limiting"
+description: "Run the canonical integration tests aligned with CI workflows, covering Cerberus, Coraza WAF, CrowdSec bouncer/decisions/startup, and rate limiting. Use when you need local parity with CI integration runs."
 author: "Charon Project"
 license: "MIT"
 tags:
@@ -56,7 +56,7 @@ metadata:
 
 ## Overview
 
-Executes the complete integration test suite for the Charon project. This skill runs all integration tests including WAF functionality (Coraza), CrowdSec bouncer integration, Cerberus backend protection, and rate limiting. It validates the entire security stack in a containerized environment.
+Executes the integration test suite for the Charon project aligned with CI workflows. This skill runs Cerberus full-stack, Coraza WAF, CrowdSec bouncer/decisions/startup, and rate limiting integration tests. It validates the core security stack in a containerized environment.
 
 This is the comprehensive test suite that ensures all components work together correctly before deployment.
 
@@ -127,10 +127,11 @@ For use in GitHub Actions workflows:
 Example output:
 ```
 === Running Integration Test Suite ===
+✓ Cerberus Integration Tests
 ✓ Coraza WAF Integration Tests
 ✓ CrowdSec Bouncer Integration Tests
-✓ CrowdSec Decision API Tests
-✓ Cerberus Authentication Tests
+✓ CrowdSec Decision Tests
+✓ CrowdSec Startup Tests
 ✓ Rate Limiting Tests
 
 All integration tests passed!
@@ -167,11 +168,12 @@ DOCKER_BUILDKIT=1 .github/skills/scripts/skill-runner.sh integration-test-all
 
 This skill executes the following test suites:
 
-1. **Coraza WAF Tests**: SQL injection, XSS, path traversal detection
-2. **CrowdSec Bouncer Tests**: IP blocking, decision synchronization
-3. **CrowdSec Decision Tests**: Decision creation, removal, persistence
-4. **Cerberus Tests**: Authentication, authorization, token management
-5. **Rate Limit Tests**: Request throttling, burst handling
+1. **Cerberus Tests**: WAF + rate limit + handler order checks
+2. **Coraza WAF Tests**: SQL injection, XSS, path traversal detection
+3. **CrowdSec Bouncer Tests**: IP blocking, decision synchronization
+4. **CrowdSec Decision Tests**: Decision API lifecycle
+5. **CrowdSec Startup Tests**: LAPI and bouncer startup validation
+6. **Rate Limit Tests**: Request throttling, burst handling
 
 ## Error Handling
 
@@ -197,11 +199,12 @@ This skill executes the following test suites:
 
 ## Related Skills
 
+- [integration-test-cerberus](./integration-test-cerberus.SKILL.md) - Cerberus full stack tests
 - [integration-test-coraza](./integration-test-coraza.SKILL.md) - Coraza WAF tests only
 - [integration-test-crowdsec](./integration-test-crowdsec.SKILL.md) - CrowdSec tests only
 - [integration-test-crowdsec-decisions](./integration-test-crowdsec-decisions.SKILL.md) - Decision API tests
 - [integration-test-crowdsec-startup](./integration-test-crowdsec-startup.SKILL.md) - Startup tests
-- [docker-verify-crowdsec-config](./docker-verify-crowdsec-config.SKILL.md) - Config validation
+- [integration-test-rate-limit](./integration-test-rate-limit.SKILL.md) - Rate limit tests
 
 ## Notes
 
@@ -215,6 +218,6 @@ This skill executes the following test suites:
 
 ---
 
-**Last Updated**: 2025-12-20
+**Last Updated**: 2026-02-07
 **Maintained by**: Charon Project Team
-**Source**: `scripts/integration-test.sh`
+**Source**: `scripts/integration-test-all.sh`

.github/skills/integration-test-cerberus-scripts/run.sh

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# Integration Test Cerberus - Wrapper Script
+# Tests Cerberus full-stack integration
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(cd "${SCRIPT_DIR}/../../.." && pwd)"
+
+exec "${PROJECT_ROOT}/scripts/cerberus_integration.sh" "$@"

.github/skills/integration-test-cerberus.SKILL.md

@@ -0,0 +1,128 @@
+---
+# agentskills.io specification v1.0
+name: "integration-test-cerberus"
+version: "1.0.0"
+description: "Run Cerberus full-stack integration tests (WAF + rate limit + handler order). Use for local parity with CI Cerberus workflow."
+author: "Charon Project"
+license: "MIT"
+tags:
+  - "integration"
+  - "security"
+  - "cerberus"
+  - "waf"
+  - "rate-limit"
+compatibility:
+  os:
+    - "linux"
+    - "darwin"
+  shells:
+    - "bash"
+requirements:
+  - name: "docker"
+    version: ">=24.0"
+    optional: false
+  - name: "curl"
+    version: ">=7.0"
+    optional: false
+environment_variables:
+  - name: "CHARON_EMERGENCY_TOKEN"
+    description: "Emergency token required for some Cerberus teardown flows"
+    default: ""
+    required: false
+parameters:
+  - name: "verbose"
+    type: "boolean"
+    description: "Enable verbose output"
+    default: "false"
+    required: false
+outputs:
+  - name: "test_results"
+    type: "stdout"
+    description: "Cerberus integration test results"
+metadata:
+  category: "integration-test"
+  subcategory: "cerberus"
+  execution_time: "medium"
+  risk_level: "medium"
+  ci_cd_safe: true
+  requires_network: true
+  idempotent: true
+---
+
+# Integration Test Cerberus
+
+## Overview
+
+Runs the Cerberus full-stack integration tests. This suite validates handler order, WAF enforcement, rate limiting behavior, and end-to-end request flow in a containerized environment.
+
+## Prerequisites
+
+- Docker 24.0 or higher installed and running
+- curl 7.0 or higher for HTTP testing
+- Network access for pulling container images
+
+## Usage
+
+### Basic Usage
+
+Run Cerberus integration tests:
+
+```bash
+cd /path/to/charon
+.github/skills/scripts/skill-runner.sh integration-test-cerberus
+```
+
+### Verbose Mode
+
+```bash
+VERBOSE=1 .github/skills/scripts/skill-runner.sh integration-test-cerberus
+```
+
+### CI/CD Integration
+
+```yaml
+- name: Run Cerberus Integration
+  run: .github/skills/scripts/skill-runner.sh integration-test-cerberus
+  timeout-minutes: 10
+```
+
+## Parameters
+
+| Parameter | Type | Required | Default | Description |
+|-----------|------|----------|---------|-------------|
+| verbose   | boolean | No    | false   | Enable verbose output |
+
+## Environment Variables
+
+| Variable | Required | Default | Description |
+|----------|----------|---------|-------------|
+| CHARON_EMERGENCY_TOKEN | No | (empty) | Emergency token for Cerberus teardown flows |
+| SKIP_CLEANUP | No | false | Skip container cleanup after tests |
+| TEST_TIMEOUT | No | 600 | Timeout in seconds for the test |
+
+## Outputs
+
+### Success Exit Code
+- **0**: All Cerberus integration tests passed
+
+### Error Exit Codes
+- **1**: One or more tests failed
+- **2**: Docker environment setup failed
+- **3**: Container startup timeout
+
+## Related Skills
+
+- [integration-test-all](./integration-test-all.SKILL.md) - Full integration suite
+- [integration-test-coraza](./integration-test-coraza.SKILL.md) - Coraza WAF tests
+- [integration-test-rate-limit](./integration-test-rate-limit.SKILL.md) - Rate limit tests
+
+## Notes
+
+- **Execution Time**: Medium execution (5-10 minutes typical)
+- **CI Parity**: Matches the Cerberus integration workflow entrypoint
+
+---
+
+**Last Updated**: 2026-02-07
+**Maintained by**: Charon Project Team
+**Source**: `scripts/cerberus_integration.sh`

.github/skills/integration-test-rate-limit-scripts/run.sh

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# Integration Test Rate Limit - Wrapper Script
+# Tests rate limit integration
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(cd "${SCRIPT_DIR}/../../.." && pwd)"
+
+exec "${PROJECT_ROOT}/scripts/rate_limit_integration.sh" "$@"

.github/skills/integration-test-rate-limit.SKILL.md

@@ -0,0 +1,126 @@
+---
+# agentskills.io specification v1.0
+name: "integration-test-rate-limit"
+version: "1.0.0"
+description: "Run rate limit integration tests aligned with the CI rate-limit workflow. Use to validate 200/429 behavior and reset windows."
+author: "Charon Project"
+license: "MIT"
+tags:
+  - "integration"
+  - "security"
+  - "rate-limit"
+  - "throttling"
+compatibility:
+  os:
+    - "linux"
+    - "darwin"
+  shells:
+    - "bash"
+requirements:
+  - name: "docker"
+    version: ">=24.0"
+    optional: false
+  - name: "curl"
+    version: ">=7.0"
+    optional: false
+environment_variables:
+  - name: "RATE_LIMIT_REQUESTS"
+    description: "Requests allowed per window in the test"
+    default: "3"
+    required: false
+parameters:
+  - name: "verbose"
+    type: "boolean"
+    description: "Enable verbose output"
+    default: "false"
+    required: false
+outputs:
+  - name: "test_results"
+    type: "stdout"
+    description: "Rate limit integration test results"
+metadata:
+  category: "integration-test"
+  subcategory: "rate-limit"
+  execution_time: "medium"
+  risk_level: "low"
+  ci_cd_safe: true
+  requires_network: true
+  idempotent: true
+---
+
+# Integration Test Rate Limit
+
+## Overview
+
+Runs the rate limit integration tests. This suite validates request throttling, HTTP 429 responses, Retry-After headers, and rate limit window resets.
+
+## Prerequisites
+
+- Docker 24.0 or higher installed and running
+- curl 7.0 or higher for HTTP testing
+- Network access for pulling container images
+
+## Usage
+
+### Basic Usage
+
+Run rate limit integration tests:
+
+```bash
+cd /path/to/charon
+.github/skills/scripts/skill-runner.sh integration-test-rate-limit
+```
+
+### Verbose Mode
+
+```bash
+VERBOSE=1 .github/skills/scripts/skill-runner.sh integration-test-rate-limit
+```
+
+### CI/CD Integration
+
+```yaml
+- name: Run Rate Limit Integration
+  run: .github/skills/scripts/skill-runner.sh integration-test-rate-limit
+  timeout-minutes: 7
+```
+
+## Parameters
+
+| Parameter | Type | Required | Default | Description |
+|-----------|------|----------|---------|-------------|
+| verbose   | boolean | No    | false   | Enable verbose output |
+
+## Environment Variables
+
+| Variable | Required | Default | Description |
+|----------|----------|---------|-------------|
+| RATE_LIMIT_REQUESTS | No | 3 | Allowed requests per window in the test |
+| RATE_LIMIT_WINDOW_SEC | No | 10 | Window size in seconds |
+| RATE_LIMIT_BURST | No | 1 | Burst size in tests |
+
+## Outputs
+
+### Success Exit Code
+- **0**: All rate limit integration tests passed
+
+### Error Exit Codes
+- **1**: One or more tests failed
+- **2**: Docker environment setup failed
+- **3**: Container startup timeout
+
+## Related Skills
+
+- [integration-test-all](./integration-test-all.SKILL.md) - Full integration suite
+- [integration-test-cerberus](./integration-test-cerberus.SKILL.md) - Cerberus full stack tests
+
+## Notes
+
+- **Execution Time**: Medium execution (3-5 minutes typical)
+- **CI Parity**: Matches the rate limit integration workflow entrypoint
+
+---
+
+**Last Updated**: 2026-02-07
+**Maintained by**: Charon Project Team
+**Source**: `scripts/rate_limit_integration.sh`

.github/skills/integration-test-waf-scripts/run.sh

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# Integration Test WAF - Wrapper Script
+# Tests generic WAF integration
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(cd "${SCRIPT_DIR}/../../.." && pwd)"
+
+exec "${PROJECT_ROOT}/scripts/waf_integration.sh" "$@"

.github/skills/integration-test-waf.SKILL.md

@@ -0,0 +1,101 @@
+---
+# agentskills.io specification v1.0
+name: "integration-test-waf"
+version: "1.0.0"
+description: "Test generic WAF integration behavior"
+author: "Charon Project"
+license: "MIT"
+tags:
+  - "integration"
+  - "waf"
+  - "security"
+  - "testing"
+compatibility:
+  os:
+    - "linux"
+    - "darwin"
+  shells:
+    - "bash"
+requirements:
+  - name: "docker"
+    version: ">=24.0"
+    optional: false
+  - name: "curl"
+    version: ">=7.0"
+    optional: false
+environment_variables:
+  - name: "WAF_MODE"
+    description: "Override WAF mode (monitor or block)"
+    default: ""
+    required: false
+parameters:
+  - name: "verbose"
+    type: "boolean"
+    description: "Enable verbose output"
+    default: "false"
+    required: false
+outputs:
+  - name: "test_results"
+    type: "stdout"
+    description: "WAF integration test results"
+metadata:
+  category: "integration-test"
+  subcategory: "waf"
+  execution_time: "medium"
+  risk_level: "medium"
+  ci_cd_safe: true
+  requires_network: true
+  idempotent: true
+---
+
+# Integration Test WAF
+
+## Overview
+
+Tests the generic WAF integration behavior using the legacy WAF script. This test is kept for local verification and is not the CI WAF entrypoint (Coraza is the CI path).
+
+## Prerequisites
+
+- Docker 24.0 or higher installed and running
+- curl 7.0 or higher for API testing
+
+## Usage
+
+Run the WAF integration tests:
+
+.github/skills/scripts/skill-runner.sh integration-test-waf
+
+## Parameters
+
+| Parameter | Type | Required | Default | Description |
+|-----------|------|----------|---------|-------------|
+| verbose | boolean | No | false | Enable verbose output |
+
+## Environment Variables
+
+| Variable | Required | Default | Description |
+|----------|----------|---------|-------------|
+| WAF_MODE | No | (script default) | Override WAF mode |
+
+## Outputs
+
+### Success Exit Code
+- 0: All WAF integration tests passed
+
+### Error Exit Codes
+- 1: One or more tests failed
+- 2: Docker environment setup failed
+- 3: Container startup timeout
+
+## Test Coverage
+
+This skill validates:
+
+1. WAF blocking behavior for common payloads
+2. Allowed requests succeed
+
+---
+
+**Last Updated**: 2026-02-07
+**Maintained by**: Charon Project Team
+**Source**: `scripts/waf_integration.sh`

.github/skills/qa-lefthook-all.SKILL.md

@@ -0,0 +1,349 @@
+---
+# agentskills.io specification v1.0
+name: "qa-lefthook-all"
+version: "1.0.0"
+description: "Run all lefthook pre-commit-phase hooks for comprehensive code quality validation"
+author: "Charon Project"
+license: "MIT"
+tags:
+  - "qa"
+  - "quality"
+  - "pre-commit"
+  - "linting"
+  - "validation"
+compatibility:
+  os:
+    - "linux"
+    - "darwin"
+  shells:
+    - "bash"
+requirements:
+  - name: "python3"
+    version: ">=3.8"
+    optional: false
+  - name: "lefthook"
+    version: ">=0.14"
+    optional: false
+environment_variables:
+    - name: "SKIP"
+    description: "Comma-separated list of hook IDs to skip"
+    default: ""
+    required: false
+parameters:
+  - name: "files"
+    type: "string"
+    description: "Specific files to check (default: all staged files)"
+    default: "--all-files"
+    required: false
+outputs:
+  - name: "validation_report"
+    type: "stdout"
+    description: "Results of all pre-commit hook executions"
+  - name: "exit_code"
+    type: "number"
+    description: "0 if all hooks pass, non-zero if any fail"
+metadata:
+  category: "qa"
+  subcategory: "quality"
+  execution_time: "medium"
+  risk_level: "low"
+  ci_cd_safe: true
+  requires_network: false
+  idempotent: true
+---
+
+# QA Pre-commit All
+
+## Overview
+
+Executes all configured lefthook pre-commit-phase hooks to validate code quality, formatting, security, and best practices across the entire codebase. This skill runs checks for Python, Go, JavaScript/TypeScript, Markdown, YAML, and more.
+
+This skill is designed for CI/CD pipelines and local quality validation before committing code.
+
+## Prerequisites
+
+- Python 3.8 or higher installed and in PATH
+- Python virtual environment activated (`.venv`)
+- Pre-commit installed in virtual environment: `pip install pre-commit`
+- Pre-commit hooks installed: `pre-commit install`
+- All language-specific tools installed (Go, Node.js, etc.)
+
+## Usage
+
+### Basic Usage
+
+Run all pre-commit-phase hooks on all files:
+
+```bash
+cd /path/to/charon
+lefthook run pre-commit
+```
+
+### Staged Files Only
+
+Run lefthook on staged files only (faster):
+
+```bash
+lefthook run pre-commit --staged
+```
+
+### Specific Hook
+
+Run only a specific hook by ID:
+
+```bash
+lefthook run pre-commit --hooks=trailing-whitespace
+```
+
+### Skip Specific Hooks
+
+Skip certain hooks during execution:
+
+```bash
+SKIP=prettier,eslint .github/skills/scripts/skill-runner.sh qa-precommit-all
+```
+
+## Parameters
+
+| Parameter | Type | Required | Default | Description |
+|-----------|------|----------|---------|-------------|
+| files     | string | No     | --all-files | File selection mode (--all-files or staged) |
+
+## Environment Variables
+
+| Variable | Required | Default | Description |
+|----------|----------|---------|-------------|
+| SKIP | No | "" | Comma-separated hook IDs to skip |
+| PRE_COMMIT_HOME | No | ~/.cache/pre-commit | Pre-commit cache directory |
+
+## Outputs
+
+- **Success Exit Code**: 0 (all hooks passed)
+- **Error Exit Codes**: Non-zero (one or more hooks failed)
+- **Output**: Detailed results from each hook
+
+## Pre-commit Hooks Included
+
+The following hooks are configured in `.pre-commit-config.yaml`:
+
+### General Hooks
+- **trailing-whitespace**: Remove trailing whitespace
+- **end-of-file-fixer**: Ensure files end with newline
+- **check-yaml**: Validate YAML syntax
+- **check-json**: Validate JSON syntax
+- **check-merge-conflict**: Detect merge conflict markers
+- **check-added-large-files**: Prevent committing large files
+
+### Python Hooks
+- **black**: Code formatting
+- **isort**: Import sorting
+- **flake8**: Linting
+- **mypy**: Type checking
+
+### Go Hooks
+- **gofmt**: Code formatting
+- **go-vet**: Static analysis
+- **golangci-lint**: Comprehensive linting
+
+### JavaScript/TypeScript Hooks
+- **prettier**: Code formatting
+- **eslint**: Linting and code quality
+
+### Markdown Hooks
+- **markdownlint**: Markdown linting and formatting
+
+### Security Hooks
+- **detect-private-key**: Prevent committing private keys
+- **detect-aws-credentials**: Prevent committing AWS credentials
+
+## Examples
+
+### Example 1: Full Quality Check
+
+```bash
+# Run all hooks on all files
+source .venv/bin/activate
+.github/skills/scripts/skill-runner.sh qa-precommit-all
+```
+
+Output:
+```
+Trim Trailing Whitespace.....................................Passed
+Fix End of Files.............................................Passed
+Check Yaml...................................................Passed
+Check JSON...................................................Passed
+Check for merge conflicts....................................Passed
+Check for added large files..................................Passed
+black........................................................Passed
+isort........................................................Passed
+prettier.....................................................Passed
+eslint.......................................................Passed
+markdownlint.................................................Passed
+```
+
+### Example 2: Quick Staged Files Check
+
+```bash
+# Run only on staged files (faster for pre-commit)
+.github/skills/scripts/skill-runner.sh qa-precommit-all staged
+```
+
+### Example 3: Skip Slow Hooks
+
+```bash
+# Skip time-consuming hooks for quick validation
+SKIP=golangci-lint,mypy .github/skills/scripts/skill-runner.sh qa-precommit-all
+```
+
+### Example 4: CI/CD Pipeline Integration
+
+```yaml
+# GitHub Actions example
+- name: Set up Python
+  uses: actions/setup-python@v4
+  with:
+    python-version: '3.11'
+
+- name: Install pre-commit
+  run: pip install pre-commit
+
+- name: Run QA Pre-commit Checks
+  run: .github/skills/scripts/skill-runner.sh qa-precommit-all
+```
+
+### Example 5: Auto-fix Mode
+
+```bash
+# Some hooks can auto-fix issues
+# Run twice: first to fix, second to validate
+.github/skills/scripts/skill-runner.sh qa-precommit-all || \
+.github/skills/scripts/skill-runner.sh qa-precommit-all
+```
+
+## Error Handling
+
+### Common Issues
+
+**Virtual environment not activated**:
+```bash
+Error: pre-commit not found
+Solution: source .venv/bin/activate
+```
+
+**Pre-commit not installed**:
+```bash
+Error: pre-commit command not available
+Solution: pip install pre-commit
+```
+
+**Hooks not installed**:
+```bash
+Error: Run 'pre-commit install'
+Solution: pre-commit install
+```
+
+**Hook execution failed**:
+```bash
+Hook X failed
+Solution: Review error output and fix reported issues
+```
+
+**Language tool missing**:
+```bash
+Error: golangci-lint not found
+Solution: Install required language tools
+```
+
+## Exit Codes
+
+- **0**: All hooks passed
+- **1**: One or more hooks failed
+- **Other**: Hook execution error
+
+## Hook Fixing Strategies
+
+### Auto-fixable Issues
+These hooks automatically fix issues:
+- `trailing-whitespace`
+- `end-of-file-fixer`
+- `black`
+- `isort`
+- `prettier`
+- `gofmt`
+
+**Workflow**: Run pre-commit, review changes, commit fixed files
+
+### Manual Fixes Required
+These hooks only report issues:
+- `check-yaml`
+- `check-json`
+- `flake8`
+- `eslint`
+- `markdownlint`
+- `go-vet`
+- `golangci-lint`
+
+**Workflow**: Review errors, manually fix code, re-run pre-commit
+
+## Related Skills
+
+- [test-backend-coverage](./test-backend-coverage.SKILL.md) - Backend test coverage
+- [test-frontend-coverage](./test-frontend-coverage.SKILL.md) - Frontend test coverage
+- [security-scan-trivy](./security-scan-trivy.SKILL.md) - Security scanning
+
+## Notes
+
+- Pre-commit hooks cache their environments for faster execution
+- First run may be slow while environments are set up
+- Subsequent runs are much faster (seconds vs minutes)
+- Hooks run in parallel where possible
+- Failed hooks stop execution (fail-fast behavior)
+- Use `SKIP` to bypass specific hooks temporarily
+- Recommended to run before every commit
+- Can be integrated into Git pre-commit hook for automatic checks
+- Cache location: `~/.cache/pre-commit` (configurable)
+
+## Performance Tips
+
+- **Initial Setup**: First run takes longer (installing hook environments)
+- **Incremental**: Run on staged files only for faster feedback
+- **Parallel**: Pre-commit runs compatible hooks in parallel
+- **Cache**: Hook environments are cached and reused
+- **Skip**: Use `SKIP` to bypass slow hooks during development
+
+## Integration with Git
+
+To automatically run on every commit:
+
+```bash
+# Install Git pre-commit hook
+pre-commit install
+
+# Now pre-commit runs automatically on git commit
+git commit -m "Your commit message"
+```
+
+To bypass pre-commit hook temporarily:
+
+```bash
+git commit --no-verify -m "Emergency commit"
+```
+
+## Configuration
+
+Pre-commit configuration is in `.pre-commit-config.yaml`. To update hooks:
+
+```bash
+# Update to latest versions
+pre-commit autoupdate
+
+# Clean cache and re-install
+pre-commit clean
+pre-commit install --install-hooks
+```
+
+---
+
+**Last Updated**: 2025-12-20
+**Maintained by**: Charon Project
+**Source**: `pre-commit run --all-files`

.github/skills/qa-precommit-all.SKILL.md

@@ -1,8 +1,8 @@
 ---
 # agentskills.io specification v1.0
-name: "qa-precommit-all"
+name: "qa-lefthook-all"
 version: "1.0.0"
-description: "Run all pre-commit hooks for comprehensive code quality validation"
+description: "Run all lefthook pre-commit-phase hooks for comprehensive code quality validation"
 author: "Charon Project"
 license: "MIT"
 tags:
@@ -21,15 +21,11 @@ requirements:
   - name: "python3"
     version: ">=3.8"
     optional: false
-  - name: "pre-commit"
-    version: ">=2.0"
+  - name: "lefthook"
+    version: ">=0.14"
     optional: false
 environment_variables:
-  - name: "PRE_COMMIT_HOME"
-    description: "Pre-commit cache directory"
-    default: "~/.cache/pre-commit"
-    required: false
-  - name: "SKIP"
+    - name: "SKIP"
     description: "Comma-separated list of hook IDs to skip"
     default: ""
     required: false
@@ -60,7 +56,7 @@ metadata:
 
 ## Overview
 
-Executes all configured pre-commit hooks to validate code quality, formatting, security, and best practices across the entire codebase. This skill runs checks for Python, Go, JavaScript/TypeScript, Markdown, YAML, and more.
+Executes all configured lefthook pre-commit-phase hooks to validate code quality, formatting, security, and best practices across the entire codebase. This skill runs checks for Python, Go, JavaScript/TypeScript, Markdown, YAML, and more.
 
 This skill is designed for CI/CD pipelines and local quality validation before committing code.
 
@@ -76,19 +72,19 @@ This skill is designed for CI/CD pipelines and local quality validation before c
 
 ### Basic Usage
 
-Run all hooks on all files:
+Run all pre-commit-phase hooks on all files:
 
 ```bash
 cd /path/to/charon
-.github/skills/scripts/skill-runner.sh qa-precommit-all
+lefthook run pre-commit
 ```
 
 ### Staged Files Only
 
-Run hooks on staged files only (faster):
+Run lefthook on staged files only (faster):
 
 ```bash
-.github/skills/scripts/skill-runner.sh qa-precommit-all staged
+lefthook run pre-commit --staged
 ```
 
 ### Specific Hook
@@ -96,7 +92,7 @@ Run hooks on staged files only (faster):
 Run only a specific hook by ID:
 
 ```bash
-SKIP="" .github/skills/scripts/skill-runner.sh qa-precommit-all trailing-whitespace
+lefthook run pre-commit --hooks=trailing-whitespace
 ```
 
 ### Skip Specific Hooks

.github/skills/scripts/_environment_helpers.sh

@@ -192,6 +192,101 @@ get_project_root() {
     return 1
 }
 
+# ensure_charon_encryption_key: Ensure CHARON_ENCRYPTION_KEY is present and valid
+# for backend tests. Generates an ephemeral base64-encoded 32-byte key when
+# missing or invalid.
+ensure_charon_encryption_key() {
+    local key_source="existing"
+    local decoded_key_hex=""
+    local decoded_key_bytes=0
+
+    generate_key() {
+        if command -v openssl >/dev/null 2>&1; then
+            openssl rand -base64 32 | tr -d '\n'
+            return
+        fi
+
+        if command -v python3 >/dev/null 2>&1; then
+            python3 - <<'PY'
+import base64
+import os
+
+print(base64.b64encode(os.urandom(32)).decode())
+PY
+            return
+        fi
+
+        echo ""
+    }
+
+    if [[ -z "${CHARON_ENCRYPTION_KEY:-}" ]]; then
+        key_source="generated"
+        CHARON_ENCRYPTION_KEY="$(generate_key)"
+    fi
+
+    if [[ -z "${CHARON_ENCRYPTION_KEY:-}" ]]; then
+        if declare -f log_error >/dev/null 2>&1; then
+            log_error "Could not auto-provision CHARON_ENCRYPTION_KEY (requires openssl or python3)"
+        else
+            echo "[ERROR] Could not auto-provision CHARON_ENCRYPTION_KEY (requires openssl or python3)" >&2
+        fi
+        return 1
+    fi
+
+    if ! decoded_key_hex=$(printf '%s' "$CHARON_ENCRYPTION_KEY" | base64 --decode 2>/dev/null | od -An -tx1 -v | tr -d ' \n'); then
+        key_source="regenerated"
+        CHARON_ENCRYPTION_KEY="$(generate_key)"
+        if ! decoded_key_hex=$(printf '%s' "$CHARON_ENCRYPTION_KEY" | base64 --decode 2>/dev/null | od -An -tx1 -v | tr -d ' \n'); then
+            if declare -f log_error >/dev/null 2>&1; then
+                log_error "CHARON_ENCRYPTION_KEY is invalid and regeneration failed"
+            else
+                echo "[ERROR] CHARON_ENCRYPTION_KEY is invalid and regeneration failed" >&2
+            fi
+            return 1
+        fi
+    fi
+
+    decoded_key_bytes=$(( ${#decoded_key_hex} / 2 ))
+    if [[ "$decoded_key_bytes" -ne 32 ]]; then
+        key_source="regenerated"
+        CHARON_ENCRYPTION_KEY="$(generate_key)"
+        if ! decoded_key_hex=$(printf '%s' "$CHARON_ENCRYPTION_KEY" | base64 --decode 2>/dev/null | od -An -tx1 -v | tr -d ' \n'); then
+            if declare -f log_error >/dev/null 2>&1; then
+                log_error "CHARON_ENCRYPTION_KEY has invalid length and regeneration failed"
+            else
+                echo "[ERROR] CHARON_ENCRYPTION_KEY has invalid length and regeneration failed" >&2
+            fi
+            return 1
+        fi
+
+        decoded_key_bytes=$(( ${#decoded_key_hex} / 2 ))
+        if [[ "$decoded_key_bytes" -ne 32 ]]; then
+            if declare -f log_error >/dev/null 2>&1; then
+                log_error "Could not provision a valid 32-byte CHARON_ENCRYPTION_KEY"
+            else
+                echo "[ERROR] Could not provision a valid 32-byte CHARON_ENCRYPTION_KEY" >&2
+            fi
+            return 1
+        fi
+    fi
+
+    export CHARON_ENCRYPTION_KEY
+
+    if [[ "$key_source" == "generated" ]]; then
+        if declare -f log_info >/dev/null 2>&1; then
+            log_info "CHARON_ENCRYPTION_KEY not set; generated ephemeral test key"
+        fi
+    elif [[ "$key_source" == "regenerated" ]]; then
+        if declare -f log_warn >/dev/null 2>&1; then
+            log_warn "CHARON_ENCRYPTION_KEY invalid; generated ephemeral test key"
+        elif declare -f log_info >/dev/null 2>&1; then
+            log_info "CHARON_ENCRYPTION_KEY invalid; generated ephemeral test key"
+        fi
+    fi
+
+    return 0
+}
+
 # Export functions
 export -f validate_go_environment
 export -f validate_python_environment
@@ -200,3 +295,4 @@ export -f validate_docker_environment
 export -f set_default_env
 export -f validate_project_structure
 export -f get_project_root
+export -f ensure_charon_encryption_key

.github/skills/security-scan-codeql-scripts/run.sh

@@ -95,6 +95,7 @@ run_codeql_scan() {
     local source_root=$2
     local db_name="codeql-db-${lang}"
     local sarif_file="codeql-results-${lang}.sarif"
+    local suite=""
     local build_mode_args=()
     local codescanning_config="${PROJECT_ROOT}/.github/codeql/codeql-config.yml"
 
@@ -107,6 +108,9 @@ run_codeql_scan() {
 
     if [[ "${lang}" == "javascript" ]]; then
         build_mode_args=(--build-mode=none)
+        suite="codeql/javascript-queries:codeql-suites/javascript-security-and-quality.qls"
+    else
+        suite="codeql/go-queries:codeql-suites/go-security-and-quality.qls"
     fi
 
     log_step "CODEQL" "Scanning ${lang} code in ${source_root}/"
@@ -135,8 +139,9 @@ run_codeql_scan() {
     fi
 
     # Run analysis
-    log_info "Analyzing with Code Scanning config (CI-aligned query filters)..."
+    log_info "Analyzing with CI-aligned suite: ${suite}"
     if ! codeql database analyze "${db_name}" \
+        "${suite}" \
         --format=sarif-latest \
         --output="${sarif_file}" \
         --sarif-add-baseline-file-info \

.github/skills/security-scan-codeql.SKILL.md

@@ -136,8 +136,8 @@ This skill uses the **security-and-quality** suite to match CI:
 
 | Language | Suite | Queries | Coverage |
 |----------|-------|---------|----------|
-| Go | go-security-and-quality.qls | 61 | Security + quality issues |
-| JavaScript | javascript-security-and-quality.qls | 204 | Security + quality issues |
+| Go | go-security-and-quality.qls | version-dependent | Security + quality issues |
+| JavaScript | javascript-security-and-quality.qls | version-dependent | Security + quality issues |
 
 **Note:** This matches GitHub Actions CodeQL default configuration exactly.
 
@@ -251,7 +251,7 @@ Solution: Verify source-root points to correct directory
 
 - [security-scan-trivy](./security-scan-trivy.SKILL.md) - Container/dependency vulnerabilities
 - [security-scan-go-vuln](./security-scan-go-vuln.SKILL.md) - Go-specific CVE checking
-- [qa-precommit-all](./qa-precommit-all.SKILL.md) - Pre-commit quality checks
+- [qa-lefthook-all](./qa-lefthook-all.SKILL.md) - Lefthook pre-commit-phase quality checks
 
 ## CI Alignment
 
@@ -260,8 +260,7 @@ This skill is specifically designed to match GitHub Actions CodeQL workflow:
 | Parameter | Local | CI | Aligned |
 |-----------|-------|-----|---------|
 | Query Suite | security-and-quality | security-and-quality | ✅ |
-| Go Queries | 61 | 61 | ✅ |
-| JS Queries | 204 | 204 | ✅ |
+| Query Expansion | version-dependent | version-dependent | ✅ (when versions match) |
 | Threading | auto | auto | ✅ |
 | Baseline Info | enabled | enabled | ✅ |
 

.github/skills/security-scan-docker-image-scripts/run.sh

@@ -35,7 +35,7 @@ fi
 # Check Grype
 if ! command -v grype >/dev/null 2>&1; then
     log_error "Grype not found - install from: https://github.com/anchore/grype"
-    log_error "Installation: curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin v0.85.0"
+    log_error "Installation: curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin v0.111.0"
     error_exit "Grype is required for vulnerability scanning" 2
 fi
 
@@ -50,8 +50,8 @@ SYFT_INSTALLED_VERSION=$(syft version | grep -oP 'Version:\s*\Kv?[0-9]+\.[0-9]+\
 GRYPE_INSTALLED_VERSION=$(grype version | grep -oP 'Version:\s*\Kv?[0-9]+\.[0-9]+\.[0-9]+' | head -1 || echo "unknown")
 
 # Set defaults matching CI workflow
-set_default_env "SYFT_VERSION" "v1.17.0"
-set_default_env "GRYPE_VERSION" "v0.85.0"
+set_default_env "SYFT_VERSION" "v1.42.4"
+set_default_env "GRYPE_VERSION" "v0.111.0"
 set_default_env "IMAGE_TAG" "charon:local"
 set_default_env "FAIL_ON_SEVERITY" "Critical,High"
 
@@ -139,7 +139,10 @@ log_info "This may take 30-60 seconds on first run (database download)"
 
 # Run Grype against the SBOM (generated from image, not filesystem)
 # This matches exactly what CI does in supply-chain-pr.yml
+# --config ensures .grype.yaml ignore rules are applied, separating
+# ignored matches from actionable ones in the JSON output
 if grype sbom:sbom.cyclonedx.json \
+    --config .grype.yaml \
     --output json \
     --file grype-results.json; then
     log_success "Vulnerability scan complete"
@@ -149,6 +152,7 @@ fi
 
 # Generate SARIF output for GitHub Security (matches CI)
 grype sbom:sbom.cyclonedx.json \
+    --config .grype.yaml \
     --output sarif \
     --file grype-results.sarif 2>/dev/null || true
 

.github/skills/security-scan-docker-image.SKILL.md

@@ -40,7 +40,7 @@ environment_variables:
     required: false
   - name: "GRYPE_VERSION"
     description: "Grype version to use for vulnerability scanning"
-    default: "v0.85.0"
+    default: "v0.107.0"
     required: false
   - name: "IMAGE_TAG"
     description: "Docker image tag to build and scan"
@@ -145,7 +145,7 @@ brew install syft  # macOS
 
 ```bash
 # Linux/macOS
-curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin v0.85.0
+curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin v0.107.0
 
 # Or via package manager
 brew install grype  # macOS
@@ -191,7 +191,7 @@ Override default versions or behavior:
 
 ```bash
 # Use specific tool versions
-SYFT_VERSION=v1.17.0 GRYPE_VERSION=v0.85.0 \
+SYFT_VERSION=v1.17.0 GRYPE_VERSION=v0.107.0 \
   .github/skills/scripts/skill-runner.sh security-scan-docker-image
 
 # Change failure threshold
@@ -211,7 +211,7 @@ FAIL_ON_SEVERITY="Critical" \
 | Variable | Required | Default | Description |
 |----------|----------|---------|-------------|
 | SYFT_VERSION | No | v1.17.0 | Syft version (matches CI) |
-| GRYPE_VERSION | No | v0.85.0 | Grype version (matches CI) |
+| GRYPE_VERSION | No | v0.107.0 | Grype version (matches CI) |
 | IMAGE_TAG | No | charon:local | Default image tag if not provided |
 | FAIL_ON_SEVERITY | No | Critical,High | Severities that cause exit code 1 |
 
@@ -239,7 +239,7 @@ FAIL_ON_SEVERITY="Critical" \
 [SBOM] Generating SBOM using Syft v1.17.0...
 [SBOM] Generated SBOM contains 247 packages
 
-[SCAN] Scanning for vulnerabilities using Grype v0.85.0...
+[SCAN] Scanning for vulnerabilities using Grype v0.107.0...
 [SCAN] Vulnerability Summary:
   🔴 Critical: 0
   🟠 High: 0
@@ -266,7 +266,7 @@ $ .github/skills/scripts/skill-runner.sh security-scan-docker-image
 [SBOM] Scanning image: charon:local
 [SBOM] Generated SBOM contains 247 packages
 
-[SCAN] Scanning for vulnerabilities using Grype v0.85.0...
+[SCAN] Scanning for vulnerabilities using Grype v0.107.0...
 [SCAN] Vulnerability Summary:
   🔴 Critical: 0
   🟠 High: 2
@@ -413,7 +413,7 @@ Solution: Install Syft v1.17.0 using installation instructions above
 **Grype not installed**:
 ```bash
 [ERROR] Grype not found - install from: https://github.com/anchore/grype
-Solution: Install Grype v0.85.0 using installation instructions above
+Solution: Install Grype v0.107.0 using installation instructions above
 ```
 
 **Build failure**:
@@ -476,7 +476,7 @@ This skill **exactly replicates** the supply-chain-pr.yml workflow:
 | Build Image | ✅ Docker build | ✅ Docker build | ✅ |
 | Load Image | ✅ Load from artifact | ✅ Use built image | ✅ |
 | Syft Version | v1.17.0 | v1.17.0 | ✅ |
-| Grype Version | v0.85.0 | v0.85.0 | ✅ |
+| Grype Version | v0.107.0 | v0.107.0 | ✅ |
 | SBOM Format | CycloneDX JSON | CycloneDX JSON | ✅ |
 | Scan Target | Docker image | Docker image | ✅ |
 | Severity Counts | Critical/High/Medium/Low | Critical/High/Medium/Low | ✅ |
@@ -571,7 +571,7 @@ Verify versions match:
 
 ```bash
 syft version  # Should be v1.17.0
-grype version # Should be v0.85.0
+grype version # Should be v0.107.0
 ```
 
 Update if needed:
@@ -579,7 +579,7 @@ Update if needed:
 ```bash
 # Reinstall specific versions
 curl -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh | sh -s -- -b /usr/local/bin v1.17.0
-curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin v0.85.0
+curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin v0.107.0
 ```
 
 ## Notes