Record CUST-WP-0045 instruction execution
This commit is contained in:
@@ -155,7 +155,7 @@ Done when activity-core tests cover all four new query names and the existing
|
||||
|
||||
```task
|
||||
id: CUST-WP-0045-T03
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
depends_on: [CUST-WP-0045-T02]
|
||||
state_hub_task_id: "e766ff2e-1887-49e6-9c66-598bb395e76c"
|
||||
@@ -321,12 +321,20 @@ supports the daily triage queries `state_summary`, `next_steps`,
|
||||
`repo_sbom_status`. Resolver failures return `{}` so the workflow can degrade
|
||||
to offline context instead of failing the whole run.
|
||||
|
||||
T03 is complete in activity-core. `RunActivityWorkflow` now evaluates
|
||||
instruction blocks after rules, using the existing instruction executor and a
|
||||
small llm-connect HTTP client boundary. Instruction results carry task specs,
|
||||
optional report payloads, prompt hash, model, validation status, review flag,
|
||||
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.
|
||||
|
||||
Verification:
|
||||
|
||||
- `uv run pytest tests/test_state_hub_context_resolver.py -q`:
|
||||
5 passed
|
||||
- `uv run pytest -q` in activity-core:
|
||||
95 passed, 1 skipped
|
||||
102 passed, 1 skipped
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
|
||||
Reference in New Issue
Block a user