docs: close controlled SBOM source rollout

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf
This commit is contained in:
tegwick 2026-09-04 15:08:20 +02:00
parent 52f2ac9a5c
commit 2c7c8a6477
2 changed files with 27 additions and 11 deletions

View file

@ -4,11 +4,11 @@ type: workplan
title: "Freeze controlled SBOM source references across retries"
domain: infotech
repo: activity-core
status: active
status: finished
owner: codex
topic_slug: infotech
created: "2026-08-22"
updated: "2026-08-23"
updated: "2026-09-04"
quality_dor: DoR-Ok
quality_dor_at: "2026-08-22"
quality_dor_by: codex
@ -43,7 +43,7 @@ tests for normalization, POST payload, retry identity, and terminal reasons.
```task
id: ACTIVITY-WP-0034-T02
status: progress
status: done
priority: high
state_hub_task_id: "036de401-18de-5a94-8f0d-18d60b64c56a"
```
@ -77,3 +77,14 @@ An in-worker, read-only report probe against the live selection returned
references. The existing schedule was not manually fired. Verification before
deploy: 61 focused tests and 435 repository tests passed, with one live
integration test skipped.
Closed 2026-09-04 from natural schedule evidence. The first unassisted weekday
fire at 2026-08-24 07:15 UTC selected exactly three repositories, retained three
`forgejo-archive-v1` references with full revisions, updated `clay-borg`, and
recorded bounded `no-manifest` outcomes for `citation-work` and `config-atlas`.
State Hub progress `f62eaadd-d10c-4a21-8547-293569ed5637` and activity-core run
`4c4594ad-366b-5720-b3f9-44fb300fda70` carry the result. Subsequent weekday
runs continued exposing exactly three new oldest repositories per fire and
reported unavailable sources explicitly as `no-checkout`; `never_count`
therefore progressed from 91 after the controlled fire to 64 on 2026-09-04
without widening the schedule or substituting a target during a run.