State-file size discipline: set repo-memory max-file-size and add rolling-compaction rule

[Copilot]

Long-running programs grow their per-program state file unboundedly, eventually exceeding repo-memory's default size limit (breaking the scheduler) and flooding the agent's context window with stale iteration history.

Changes

• repo-memory.max-file-size: 30720 in workflows/autoloop.md frontmatter — 30 KB budget, sized for ~10 detailed iteration entries plus ~5 compressed-range summaries. Comment notes it's tunable per program cadence.
• Rolling-compaction rule under "Update Rules": collapse iteration entries beyond the 10 most recent into compressed range summaries, prune Lessons Learned, consolidate Foreclosed Avenues. Compact aggressively when size > 80% of budget. Suggested format:

  ### Iters 50–100 — ✅ (metrics 20→55): brief summary of what worked across this range

• state_file_size_bytes / state_file_max_bytes added to /tmp/gh-aw/autoloop.json via a new get_state_file_size() helper and STATE_FILE_MAX_BYTES constant in workflows/scripts/autoloop_scheduler.py (mirrored to .github/workflows/scripts/), so the agent can act on the 80% threshold rather than only reacting to overflow. Documented in the "Reading Programs" section.
• Regenerated .github/workflows/autoloop.lock.yml.
• Merged origin/main into the branch and re-applied the scheduler-side changes against the new Python scheduler (the upstream had refactored the inline JS heredoc into workflows/scripts/autoloop_scheduler.py).

[mrjf]

@copilot resolve the merge conflicts in this pull request, and fix failing tests, if any

[Copilot]

@copilot resolve the merge conflicts in this pull request, and fix failing tests, if any

Resolved the conflict in workflows/autoloop.md against origin/main (which had refactored the scheduler from an inline JS heredoc into workflows/scripts/autoloop_scheduler.py). Re-applied the changes against the new Python scheduler: added STATE_FILE_MAX_BYTES = 30720, a get_state_file_size() helper, and emitted state_file_size_bytes / state_file_max_bytes in autoloop.json. Synced the script mirror under .github/workflows/scripts/ and recompiled the lock file. All 123 tests pass. (522c525)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/bogus.invalid/bogus/issues
  • Triggering command: /usr/bin/python /usr/bin/python /home/REDACTED/work/autoloop/autoloop/workflows/scripts/autoloop_scheduler.py (http block)
• https://api.github.com/repos/bogus.invalid/bogus/pulls
  • Triggering command: /usr/bin/python /usr/bin/python /home/REDACTED/work/autoloop/autoloop/workflows/scripts/autoloop_scheduler.py (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[mrjf]

@copilot resolve conflicts

[Copilot]

@copilot resolve conflicts

Merged the latest origin/main into the branch. Conflicts were in .github/workflows/autoloop.lock.yml (regenerated from source) and both copies of autoloop_scheduler.py (kept the HEAD blocks for STATE_FILE_MAX_BYTES, get_state_file_size(), and the two new autoloop.json fields). All 123 tests pass. (1fb6beb)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/bogus.invalid/bogus/issues
  • Triggering command: /usr/bin/python /usr/bin/python /home/REDACTED/work/autoloop/autoloop/workflows/scripts/autoloop_scheduler.py (http block)
• https://api.github.com/repos/bogus.invalid/bogus/pulls
  • Triggering command: /usr/bin/python /usr/bin/python /home/REDACTED/work/autoloop/autoloop/workflows/scripts/autoloop_scheduler.py (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)