v2: Forge Console + Open WebUI artifacts + Docker

- web/: Local chat UI (Express + WS → Codex bridge)
- openwebui/: Preset, pipelines, knowledge manifest
- Dockerfile + docker-compose.yml
- Updated README with 3 frontend options
- CLI-agnostic: works with Codex, Claude Code, Kiro, Gemini

skills/epics-standards/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: epics-standards
+description: Create or audit RP Jira epics and linked Aha epics against PM standards. Use when creating new RP epics, creating Aha epics for a target release, checking compliance gaps, or updating epic fields/content to align with the PM standards and Aha workflow.
+---
+
+# RP Epic Standards
+
+Use this skill for `RP` epic creation, Aha epic creation, and compliance audits.
+
+Primary standard source:
+`https://reltio.jira.com/wiki/spaces/PM/pages/2688385025/PM+Standards+Epics`
+
+Workflow source and mapping:
+- `references/aha-epic-workflow.md`
+- `references/epic-fields-checklist.md`
+
+## Workflow
+
+1. Open the standard page and use it as source of truth.
+2. Validate/collect required inputs (see Intake below).
+3. Create/update Jira epic and Aha epic per workflow in `references/aha-epic-workflow.md`.
+4. Link Jira and Aha (`Aha! Reference` in Jira).
+5. Audit compliance against `references/epic-fields-checklist.md`.
+6. If fields are not editable in Jira/Aha, document exact gaps and owner.
+
+## Intake (Interactive)
+
+If required fields are not provided in the prompt, ask concise follow-up questions before creating records.
+
+Minimum required fields to ask for:
+- Jira epic key (if already created) or request to create one
+- Aha release (for example `2026.2.0.0`)
+- Epic short name (Jira/Aha title)
+- Problem Statement / Why
+- Solution / What
+- Persona / Who
+- Value Statement
+- Confidence Level
+- Product, Engineering, and UX leads
+- Execution Team
+- Required flags: Doc, Provisioning, UI/UX, Security, Training
+
+Ask only for missing items. Do not proceed with creation until minimum fields are available.
+
+## Epic Content Requirements
+
+Ensure description includes:
+- Problem Statement / Why
+- Solution / What
+- Persona / Who
+- Value Statement
+
+Keep summary short and clear for Jira readability.
+
+## Aha Creation Code
+
+Use the bundled script:
+- `scripts/aha_create_epic.py`
+
+Example:
+```bash
+python3 skills/epics-standards/scripts/aha_create_epic.py \
+  --release MDM-R-889 \
+  --name "RDM PrivateLink on AWS" \
+  --description "Tracks Jira epic RP-176273 (https://reltio.jira.com/browse/RP-176273)." \
+  --jira-key RP-176273
+```
+
+The script reads Aha credentials from `~/.mcporter/mcporter.json` (`mcpServers.aha.env`).
+
+## Integration Guardrails
+
+If the epic is created in Jira first, verify that Aha linkage is present (`Aha! Reference`).
+If missing, update Jira with the created Aha URL.