diff --git a/docs/requirements/001-agent-orchestrator.md b/docs/requirements/001-agent-orchestrator.md index a61e762..a6dbd7b 100644 --- a/docs/requirements/001-agent-orchestrator.md +++ b/docs/requirements/001-agent-orchestrator.md @@ -834,7 +834,12 @@ Replaced by [003 W4 Resources](003-operator-workbench.md#w4-resources). - [x] With a configured `svc-ai-speech` URL the hub sends STT and TTS there; without it the in-container engines answer (unit test with a stub). - [ ] `make orchestrator-install` succeeds in a scratch HOME without any core - stack. + stack: `tests/test_orchestrator_migration.py` runs the install there + with stub docker, claude and systemctl, and `docker build` of + `orchestrator/` without `INFINITO_ARTEFACT_BASE` builds the image from + the upstream URLs alone (operator 2026-11-17; a real install in a + scratch HOME would replace the live hub's compose project, image and + port). ### Phase 6: Gantt, estimates, burndown and burnup (S5) diff --git a/docs/requirements/002-cosmos.md b/docs/requirements/002-cosmos.md index 417d0f8..2c44266 100644 --- a/docs/requirements/002-cosmos.md +++ b/docs/requirements/002-cosmos.md @@ -43,6 +43,13 @@ background without carrying its code twice. set the cosmos repository ships (`cosmos.js`, `LICENSE`, `NOTICE.md`). This replaces the music, orbit and 3D parts of decisions 1 and 3. Rejected: removing the music, moving the 3D views. +10. **Hand-over (operator-confirmed 2026-11-17)**: cosmos requirement 001 + (`docs/requirements/001-cosmos.md` in the cosmos repository) leads; its + decision 6 replaces decision 6 here. The holder of `work/cosmos` + extracts the sky and switches the orchestrator to a pinned cosmos tag + in a skills worktree; Skills only reviews that switch. While the claim + has no live holder, 002 waits. Rejected: Skills taking the switch over, + closing 002 as superseded. ## Approach diff --git a/docs/requirements/010-security-scan-cache-per-file.md b/docs/requirements/010-security-scan-cache-per-file.md index 29bad35..41df471 100644 --- a/docs/requirements/010-security-scan-cache-per-file.md +++ b/docs/requirements/010-security-scan-cache-per-file.md @@ -47,7 +47,12 @@ file is never scanned twice across branches and sessions. `docker_compose_scanner` runs in the file's folder. `medusa scan` has no flag that selects scanners, so a file that `FILE_SCANNERS` routes to a cross-file scanner stays in a per-diff group, keyed like today minus the - expiry. The check is an acceptance criterion. + expiry. The check is an acceptance criterion. Operator 2026-11-17: + semgrep and gitleaks run over the whole tree but match within one file, + so they count as file-local once `test_findings_file_local` shows it; + their configuration files (`.semgrepignore`, `.gitleaks.toml`, + `.gitleaksignore`) join `CROSS_FILE`. Rejected: semgrep and gitleaks as + cross-file routes, which would leave nearly every code file per diff. 7. **Through the quality store**: entries are written and read with `quality store put` and `get` (quality 003) under tool `medusa`; `/security-cache/` goes away. A payload holds per finding @@ -108,9 +113,10 @@ flowchart TD findings scanned inside the full fixture tree; every route where they differ is listed in `CROSS_FILE` in `security.py`. - [ ] `CROSS_FILE` holds the routes of `trivy_scanner`, `rust_scanner` and - `docker_compose_scanner` and the configuration names that - `_find_config_file` looks up, unless `test_findings_file_local` proves - one of them file-local. + `docker_compose_scanner`, the configuration names that + `_find_config_file` looks up and `.semgrepignore`, `.gitleaks.toml` and + `.gitleaksignore`, unless `test_findings_file_local` proves one of them + file-local; the semgrep and gitleaks routes themselves are not in it. - [ ] `test_cross_file_group_rescans`: changing a sibling of a file in the per-diff group (a `Cargo.toml` next to a `.rs` file) rescans the group.