# TASK 3.1: Add Static Blocked-Term Validation

## Summary

Run static validation over the eight migrated KDS monitor specs and fix any remaining source-schema references.

This task ensures the migrated prompts no longer instruct the agent to use source tables or source-only fields.

## Dependencies

- TASK 1.1 (prep-time and order-surge migration)
- TASK 1.2 (large-order-wave and priority-flood migration)
- TASK 2.1 (slow-kitchen and station-bottleneck migration)
- TASK 2.2 (forgotten-items and item-recall-storm migration)

## Files to Validate

- `backend/Kds.Ai.Data/MonitorSpecs/prep-time.md`
- `backend/Kds.Ai.Data/MonitorSpecs/order-surge.md`
- `backend/Kds.Ai.Data/MonitorSpecs/large-order-wave.md`
- `backend/Kds.Ai.Data/MonitorSpecs/priority-flood.md`
- `backend/Kds.Ai.Data/MonitorSpecs/slow-kitchen.md`
- `backend/Kds.Ai.Data/MonitorSpecs/station-bottleneck.md`
- `backend/Kds.Ai.Data/MonitorSpecs/forgotten-items.md`
- `backend/Kds.Ai.Data/MonitorSpecs/item-recall-storm.md`

## Required Validation

Run a static check for blocked terms:

- `kdsdev.`
- `store_guid`
- `is_deleted`
- `create_time`
- `update_time`
- `done=`
- `done =`
- `items_count`
- `device_id`
- `item_bumps`
- `prepared_local_time`
- `done_local_time`

Also check for invalid runtime surfaces:

- `staging.`
- `etl_meta.`
- `curated.payments`

## Required Behavior

For each blocked term:

- remove it if it instructs source-schema query behavior,
- replace it with the curated equivalent when appropriate,
- document any intentional false positive if one remains.

Expected final state:

- in-scope monitor specs reference only `curated.orders` and `curated.order_items`,
- time fields are curated timestamp fields,
- workflow logic uses curated workflow columns,
- no source cleanup filters remain.

## Acceptance Criteria

- [ ] Static blocked-term check is run across all eight files
- [ ] No in-scope monitor spec references `kdsdev.`
- [ ] No in-scope monitor spec requires `store_guid`
- [ ] No in-scope monitor spec requires `is_deleted`
- [ ] No in-scope monitor spec instructs use of `create_time` or `update_time`
- [ ] No in-scope monitor spec references `item_bumps`
- [ ] No in-scope monitor spec references `staging`, `etl_meta`, or curated objects outside `curated.orders` and `curated.order_items`
- [ ] Any remaining false positives are explicitly documented
- [ ] No runtime code is changed in this task

## Notes

- Use judgment for prose, but final prompts should not teach source-schema behavior.
- Prefer exact curated terminology from `serving-mapping.md`.