docs: specify deployment scheduling and verify implementation plan

2026-09-08 09:45:49 +07:00
parent 7518954ab3
commit d5fa180984
6 changed files with 3318 additions and 0 deletions
@@ -0,0 +1,40 @@
+# DISPOSABLE VERIFICATION PROBE — NOT PRODUCTION CODE
+
+This directory holds throwaway verification probes for the
+deployment-scheduling slice
+(`docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md`).
+They are evidence-gathering scripts, not a production implementation:
+
+- `test_calendar_probe.py` — calendar-library probe (16 passed, 2 strict
+  xfailed: Part A pins the croniter contract, Part B keeps APScheduler
+  rejected-candidate evidence). Requires `croniter==6.2.4`, `tzdata`
+  (`apscheduler==3.11.0` for Part B only) on Python 3.14.
+  Run it from an isolated project (NOT the repo env, which does not
+  depend on croniter; the file `importorskip`s itself elsewhere):
+
+  ```powershell
+  $probe = "C:\Users\Admin\AppData\Local\Temp\opencode\sched-cal-probe"
+  $file = "<worktree>\probes\deployment_scheduling_verify\test_calendar_probe.py"
+  uv run --project $probe python -m pytest $file -q -p no:cacheprovider `
+    -o addopts=""
+  ```
+
+- `test_schedule_state_model.py` — pure-stdlib reference model of the
+  scheduling state machine (25 tests: overlap x misfire, coalescing,
+  slots, pause, faults, ownership). Runs in the repo env:
+
+  ```powershell
+  uv run pytest -q probes/deployment_scheduling_verify/test_schedule_state_model.py
+  ```
+
+- `test_expression_contract_probe.py` — pins the current input-expression
+  contract for the Phase 1 implementer (8 tests). Runs in the repo env:
+
+  ```powershell
+  uv run pytest -q probes/deployment_scheduling_verify/test_expression_contract_probe.py
+  ```
+
+Do not import these probes from `src/`. Do not copy their logic into
+production without going through the sequenced implementation plan at
+`docs/superpowers/plans/2026-09-09-deployment-scheduling-implementation-plan.md`.
+Delete this directory once the slice is implemented.