tegwick
5d3fb33c6b
Surfaced while bringing up the dev worker for the CUST-WP-0045 T06 cutover.
weekly-sbom-staleness fires its state-hub resolver with query
repo_sbom_status, which hits GET /sbom/status?repo=. State Hub does not
expose that route, so _fetch_json returns {} and the rule
context.repos.sbom_age_days > 30 silently no-ops. The weekly SBOM check has
been a no-op for as long as the route mismatch has existed. Logged as a
low-priority adhoc rather than promoting to a workplan because the resolver
and definition both need a one-line decision (single-repo vs fan-out), not
multi-phase design.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| ACTIVITY-WP-0005-railiance01-production-service.md | ||
| ADHOC-2026-06-01.md | ||
| custodian-WP-0001-temporal-backbone.md | ||
| custodian-WP-0002-triggers-ops.md | ||
| custodian-WP-0003-event-bridge.md | ||
| custodian-WP-0003a-event-bridge-model-rules-registry.md | ||
| custodian-WP-0003b-event-bridge-parser-workflow-triggers.md | ||
| custodian-WP-0003c-event-bridge-context-integration.md | ||
| custodian-WP-0004-railiance-ops.md | ||
| WP-0002-next-steps.md | ||