Record CUST-WP-0045 report sinks
This commit is contained in:
@@ -186,7 +186,7 @@ produce a validated report payload under test.
|
||||
|
||||
```task
|
||||
id: CUST-WP-0045-T04
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
depends_on: [CUST-WP-0045-T03]
|
||||
state_hub_task_id: "04e56428-d3a8-4aa7-a6e1-172c974ece3a"
|
||||
@@ -329,12 +329,20 @@ and condition metadata. A lightweight daily triage report schema is available
|
||||
at `schemas/daily-triage-report.json` so report payloads can be validated under
|
||||
test before T04 wires the deterministic working-memory and State Hub sinks.
|
||||
|
||||
T04 is complete in activity-core. Instruction definitions can now declare
|
||||
`report_sinks`; report payloads are persisted through deterministic sink code
|
||||
instead of model-authored file operations. The first two sink types are
|
||||
`working-memory` and `state-hub-progress`. Working-memory writes refuse
|
||||
canonical Custodian `canon/` and `workplans/` paths, use run-id/date based
|
||||
idempotency, and State Hub progress posting deduplicates by activity run id and
|
||||
instruction id before posting.
|
||||
|
||||
Verification:
|
||||
|
||||
- `uv run pytest tests/test_state_hub_context_resolver.py -q`:
|
||||
5 passed
|
||||
- `uv run pytest -q` in activity-core:
|
||||
102 passed, 1 skipped
|
||||
106 passed, 1 skipped
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
|
||||
Reference in New Issue
Block a user