chore: gitignore modal/results; point AFK_CHECK at requeued task #1

- /modal/results/ holds derived modal-cloud run status (junk RemoteError
  summary); stop tracking it.
- AFK_CHECK live-plan pointer #221 -> #1 (queue was cleared 2026-06-07 and the
  directionality set requeued via just queue-dir6 43).

Co-Authored-By: Claudypoo <288921227+claudypoo@users.noreply.github.com>

.gitignore

@@ -18,6 +18,9 @@
 # vendored upstream reference repos cloned for grep access (see RESEARCH_JOURNAL.md)
 /docs/vendor/
 
+# modal cloud run outputs (derived; _summary.json is just the remote status)
+/modal/results/
+
 # build/install artefacts
 *.egg-info/
 __pycache__/

docs/AFK_CHECK.md

@@ -2,7 +2,8 @@
 
 LITE check, once per hour (cron fe8385ed, :23). The default outcome is DO NOTHING.
 This doc holds the durable rules. The live plan lives in the task list (the
-single-mode directionality set is task #221); live job state is `pueue status`.
+single-mode directionality set is task #1, requeued via `just queue-dir6 43`
+after the queue was cleared 2026-06-07); live job state is `pueue status`.
 Do not hardcode job numbers here -- they churn.
 
 ## Rule 0: no-op if the queue is in order
@@ -18,7 +19,7 @@ Only when one of those breaks do you do the matching step under "On a break".
 
 ## What to read for the plan
 
-- `TaskList` -> the in_progress directionality task (#221) holds the arm order, the
+- `TaskList` -> the in_progress directionality task (#1) holds the arm order, the
   per-arm expectation, and the PASS condition. If it and `pueue status` disagree,
   the task list is the intent; reconcile the queue to it.
 - `pueue status --json | jq` for which job is which arm (the why-label says the arm