fix: docs: per-agent AGENTS.md files still describe cron triggers (#547)

predictor/AGENTS.md

@@ -22,14 +22,15 @@ exploit counts as 2 (prediction + action dispatch). The predictor MUST NOT
 emit feature work — only observations challenging claims, exposing gaps,
 and surfacing risks.
 
-**Trigger**: `predictor-run.sh` runs daily at 06:00 UTC via cron (1h before
-the planner at 07:00). Sources `lib/guard.sh` and calls `check_active predictor`
-first — skips if `$FACTORY_ROOT/state/.predictor-active` is absent. Also guarded
-by PID lock (`/tmp/predictor-run.lock`) and memory check (skips if available
-RAM < 2000 MB).
+**Trigger**: `predictor-run.sh` is invoked by the polling loop in `docker/agents/entrypoint.sh`
+every 24 hours (iteration math at line 224-236). Sources `lib/guard.sh` and calls
+`check_active predictor` first — skips if `$FACTORY_ROOT/state/.predictor-active` is absent.
+Also guarded by PID lock (`/tmp/predictor-run.lock`) and memory check (skips if available
+RAM < 2000 MB). Note: the 24h cadence is iteration-based, not anchored to 06:00 UTC —
+drifts on container restart.
 
 **Key files**:
-- `predictor/predictor-run.sh` — Cron wrapper + orchestrator: active-state guard,
+- `predictor/predictor-run.sh` — Polling loop participant + orchestrator: active-state guard,
   lock, memory guard, sources disinto project config, builds structural analysis
   via `lib/formula-session.sh:build_graph_section()` (full-project scan — results
   included in prompt as `## Structural analysis`; failures non-fatal), builds
@@ -44,7 +45,7 @@ RAM < 2000 MB).
 - `FORGE_TOKEN`, `FORGE_PREDICTOR_TOKEN` (falls back to FORGE_TOKEN), `FORGE_REPO`, `FORGE_API`, `PROJECT_NAME`, `PROJECT_REPO_ROOT`, `OPS_REPO_ROOT`
 - `PRIMARY_BRANCH`, `CLAUDE_MODEL` (set to sonnet by predictor-run.sh)
 
-**Lifecycle**: predictor-run.sh (daily 06:00 cron) → lock + memory guard →
+**Lifecycle**: predictor-run.sh (invoked by polling loop every 24h) → lock + memory guard →
 load formula + context (AGENTS.md, VISION.md from code repo; RESOURCES.md, prerequisites.md from ops repo)
 → create tmux session → Claude fetches prediction history (open + closed) →
 reviews track record (actioned/dismissed/watching) → finds weaknesses