Merge pull request #202 from ethosengine/dev

Merge dev into staging

Author: Mbd06b

.claude/agents/ci-pipeline.md

@@ -23,7 +23,7 @@ elohim-holochain (DNA/hApp, WASM artifacts)
 **Changeset Patterns** (from orchestrator):
 ```groovy
 'elohim-holochain': ['holochain/dna/', 'holochain/holochain-cache-core/', 'holochain/rna/'],
-'elohim-edge': ['holochain/doorway/', 'holochain/edgenode/', 'holochain/elohim-storage/', 'holochain/manifests/', 'holochain/crates/'],
+'elohim-edge': ['doorway/', 'doorway-app/', 'holochain/edgenode/', 'holochain/elohim-storage/', 'holochain/crates/'],
 'elohim': ['elohim-app/', 'elohim-library/', 'VERSION'],
 'elohim-genesis': ['genesis/', 'data/'],
 'elohim-steward': ['steward/'] // manual only

.claude/agents/elohim-visual-alignment.md.save

@@ -8,7 +8,7 @@ color: magenta
 
 You are the Gateway and Storage Specialist for the Elohim Protocol. You understand the edge infrastructure that bridges web clients to the Holochain DHT.
 
-**For comprehensive infrastructure context, reference `holochain/claude.md` and `holochain/EDGE-ARCHITECTURE.md`.**
+**For comprehensive infrastructure context, reference `holochain/claude.md`.**
 
 ## Architecture Principle
 
@@ -18,7 +18,7 @@ P2P performance happens at the **agent level** (via holochain-cache-core), not a
 
 ## Component Structure
 
-### holochain/doorway/ (Rust WebSocket Gateway)
+### doorway/ (Rust WebSocket Gateway)
 
 | File | Purpose |
 |------|---------|
@@ -92,7 +92,7 @@ pub async fn run_admin_proxy(
 
 ```bash
 # Build doorway
-cd /projects/elohim/holochain/doorway
+cd /projects/elohim/doorway
 RUSTFLAGS='' cargo build --release
 
 # Run with dev mode
@@ -109,7 +109,7 @@ curl http://localhost:8888/status | jq .
 
 # Build elohim-storage
 cd /projects/elohim/holochain/elohim-storage
-RUSTFLAGS='' cargo build --release
+RUSTFLAGS='--cfg getrandom_backend="custom"' cargo build --release
 ```
 
 ## WriteBuffer Presets

.claude/agents/gateway-storage.md

@@ -146,6 +146,19 @@ When scanning for gaps, include all projects:
 
 **Depth over breadth:** Don't just grep for TODOs. Read the code around them. Understand what the feature *would* do, who it serves, and why it matters.
 
+### BDD Coverage Gap Reports
+
+When `orchestrator/e2e/reports/coverage-gap-report.json` exists (generated by the BDD gap scanner in CI or locally via `cd orchestrator/e2e && npm run scan:coverage`), incorporate it into your analysis:
+
+1. **Read the report** — it contains `prioritizedGaps` ranked by conceptual density
+2. **Cross-reference with feature gaps** — the report's `epicsWithZeroTests` maps to domain pillars that have zero executable E2E coverage
+3. **Sprint recommendations** — use `prioritizedGaps` entries as ready-made sprint candidates. Each gap includes a `suggestedFeatureFile` path and `rationale`
+4. **GitHub issues** — when creating feature-gap issues from BDD gaps, include:
+   - The gap's `domain` and `governanceLayer` in the title
+   - The `conceptualDensity` in the technical context
+   - Label with `bdd-gap` in addition to standard labels
+5. **Track convergence** — compare `summary.coveragePercent` across report timestamps to measure whether the gap-analysis loop is closing
+
 ## 3. User Story Generation
 
 Turn discovered gaps into well-formed user stories for sprint planning.

.claude/agents/quality-architect.md

@@ -104,8 +104,8 @@ Post-hooks run linting automatically on tool use. If hooks report violations in
 ### TypeScript/Angular
 | Tool | Purpose | Config |
 |------|---------|--------|
-| ESLint | Code quality rules | `.eslintrc.json` |
-| Prettier | Code formatting | `.prettierrc` |
+| ESLint | Code quality rules | `eslint.config.js` (flat config) |
+| Prettier | Code formatting | `.prettierrc.js` |
 | TypeScript | Type checking | `tsconfig.json` |
 
 ### Rust
@@ -157,7 +157,7 @@ npx tsc -p tsconfig.app.json --noEmit
 ### Clippy (Rust)
 ```bash
 # Run clippy
-cd /projects/elohim/holochain/doorway
+cd /projects/elohim/doorway
 RUSTFLAGS='' cargo clippy
 
 # With all warnings
@@ -350,29 +350,11 @@ Remaining: Y manual issues
 
 ## Configuration Files
 
-### ESLint (.eslintrc.json)
-```json
-{
-  "extends": [
-    "eslint:recommended",
-    "@angular-eslint/recommended"
-  ],
-  "rules": {
-    "@typescript-eslint/no-unused-vars": "error",
-    "@typescript-eslint/explicit-function-return-type": "warn"
-  }
-}
-```
+### ESLint (eslint.config.js)
+Uses ESLint 9 flat config format. See `elohim-app/eslint.config.js` for the full configuration.
 
-### Prettier (.prettierrc)
-```json
-{
-  "semi": true,
-  "singleQuote": true,
-  "tabWidth": 2,
-  "printWidth": 100
-}
-```
+### Prettier (.prettierrc.js)
+See `elohim-app/.prettierrc.js` for the full configuration (100 char width, single quotes, trailing commas).
 
 ### Clippy (clippy.toml)
 ```toml

.claude/agents/quality-sweep.md

@@ -63,7 +63,7 @@ grep -r "password\|token\|secret\|key" --include="*.ts" elohim-app/src/
 grep -r "validate\|verify\|check" --include="*.rs" holochain/dna/
 
 # Find exposed endpoints
-grep -r "router\|route\|endpoint" --include="*.rs" holochain/doorway/
+grep -r "router\|route\|endpoint" --include="*.rs" doorway/
 ```
 
 ### 2. Threat Modeling (STRIDE)

.claude/agents/red-team.md

@@ -0,0 +1,51 @@
+# BDD Coverage Gap Analysis
+
+Run the BDD coverage gap scanner and interpret the results for sprint planning.
+
+## Steps
+
+1. Run the scanner:
+```bash
+cd orchestrator/e2e && npx tsx scripts/scan-coverage.ts
+```
+
+2. Read the generated report:
+```
+orchestrator/e2e/reports/coverage-gap-report.json
+```
+
+3. Present an interpreted analysis with:
+
+### Summary Statistics
+- Total conceptual scenarios (from genesis feature files)
+- Total executable scenarios (from Cypress + Cucumber-JS)
+- Coverage percentage
+- Number of epics with zero test coverage
+
+### Top 5 Priority Gaps
+For each of the top 5 entries in `prioritizedGaps`:
+- **Domain** and **governance layer**
+- **Conceptual density** (how many scenarios exist conceptually)
+- **Rationale** for why this gap matters
+- **Suggested feature file** path for new executable tests
+
+### Sprint Recommendations
+Using quality-architect user story format:
+
+```
+**As a** [persona from the gap's user types]
+**I want** [executable E2E coverage for this domain]
+**So that** [the loop closes and regressions are caught]
+
+### Acceptance Criteria
+- [ ] Feature file created at suggested path
+- [ ] Step definitions use E2EWorld, DoorwayClient, BrowserDevice patterns
+- [ ] At least N scenarios converted from conceptual to executable
+- [ ] `npm run scan:coverage` shows improved coverage for this epic
+```
+
+### Genesis Features to Convert First
+For each gap, list the specific genesis feature files (`featureFile` from the conceptual scenarios) that should be translated first. Prioritize files with the most scenarios.
+
+### Loop Status
+How many iterations of the scanner → generate → review loop have occurred (check git log for coverage-gap-report.json commits). Note the trend in coverage percentage.

.claude/commands/gap-analysis.md

@@ -0,0 +1,67 @@
+# Generate Executable BDD Scenarios from Gap Report
+
+Read the BDD coverage gap report and generate executable feature files + step definition skeletons for the top priority gaps.
+
+**Argument**: Number of gaps to generate for (default: 3). Pass as `$ARGUMENTS`.
+
+## Steps
+
+1. Read the gap report:
+```
+orchestrator/e2e/reports/coverage-gap-report.json
+```
+
+If the report doesn't exist, run the scanner first:
+```bash
+cd orchestrator/e2e && npx tsx scripts/scan-coverage.ts
+```
+
+2. For the top N gaps (from `prioritizedGaps`, where N = `$ARGUMENTS` or 3):
+
+### a. Read Source Genesis Features
+For each gap, find the genesis feature files that match the gap's domain + governance layer:
+```
+genesis/docs/content/elohim-protocol/{domain}/{user_type}/scenarios/{governance_layer}.feature
+```
+
+Read these files to understand the conceptual scenarios.
+
+### b. Read Existing Executable Features as Style Reference
+Read these files to match the executable style:
+- `orchestrator/e2e/features/federation/cross-doorway-content.feature` — feature file pattern
+- `orchestrator/e2e/steps/federation.steps.ts` — step definition pattern
+
+### c. Generate Feature Files
+Create `.feature` files at the `suggestedFeatureFile` path from the gap report.
+
+**Translation strategy**: conceptual scenarios describe human experiences. Executable scenarios test the API contracts that would support those flows. For example:
+- "Workers implement community meal program" -> test content creation + tagging + cross-doorway discovery
+- "Workers welcome community stakeholder input" -> test content creation + governance metadata + search
+
+Each generated feature should:
+- Use `@e2e @{epic}` tags on the first line
+- Include a Background with doorway health checks
+- Translate 3-5 conceptual scenarios into executable ones
+- Use Given/When/Then with the existing step patterns (human registration, content creation, content discovery)
+- Add `@wip` tag to scenarios that need step definitions not yet implemented
+
+### d. Generate Step Definition Skeletons
+Create skeleton step files at `orchestrator/e2e/steps/{epic}.steps.ts`.
+
+Each skeleton should:
+- Import from `@cucumber/cucumber` (Given, When, Then)
+- Import `E2EWorld`, `Human`, `BrowserDevice` from the framework
+- Include stub step definitions matching the new feature file
+- Mark incomplete steps with `// TODO: implement` comments
+- Follow the pattern from `federation.steps.ts`
+
+### e. Verify
+For each generated file:
+- Ensure the feature file parses (no syntax errors)
+- Ensure the step file compiles (typecheck)
+
+3. Report what was generated:
+- List of new feature files with scenario counts
+- List of new step definition files
+- Which steps are fully implemented vs TODO
+- Updated coverage estimate (run scanner again)

.claude/commands/generate-scenarios.md

@@ -323,6 +323,16 @@ Each file read ≈ 1-3K tokens. Fix + write ≈ similar. Plus agent instructions
 
 ---
 
+## BDD Coverage Gap Reports as Campaign Source
+
+The BDD gap scanner (`cd orchestrator/e2e && npm run scan:coverage`) produces `orchestrator/e2e/reports/coverage-gap-report.json`. This report is also generated in CI as an advisory stage.
+
+**quality-architect can create campaigns from `prioritizedGaps` entries.** Each entry identifies a domain + governance layer with high conceptual density but zero executable tests. These are natural candidates for E2E coverage campaigns.
+
+To generate executable scenarios from gap report entries, use `/generate-scenarios N` where N is the number of top gaps to address.
+
+---
+
 ## Existing Infrastructure (Preserved)
 
 These tools continue to work alongside the team system:
@@ -333,6 +343,7 @@ These tools continue to work alongside the team system:
 | `generate-campaigns.py` | Group issues into campaigns | Phase 1 |
 | `lint-orchestrator.py` | Status tracking, escalation queries | `show-status`, `get-escalations` |
 | `pre-flight-check.py` | Build health validation | Phase 1 |
+| `scan-coverage.ts` | BDD coverage gap scanner | `cd orchestrator/e2e && npm run scan:coverage` |
 | PostToolUse hooks | Auto-lint on every edit | Continuous (automatic) |
 
 ---

.claude/skills/quality-orchestrator/SKILL.md

@@ -42,6 +42,12 @@ output/
 # Seed data is now version-controlled for CI access
 # data/lamad/**/*.json
 
+# Holochain runtime
+.hc_live_*
+
+# E2E test artifacts (generated per run, archived in CI)
+orchestrator/e2e/reports/
+
 # Rust/Holochain
 target/
 *.happ