Increase repo-memory max-file-size to 30KB and add state file trimming instructions

The autoloop push_repo_memory job was failing because the state file
build-tsb-pandas-typescript-migration.md (10695 bytes) exceeded the
default 10240 byte limit. Increase limit to 30720 bytes and add agent
instructions to collapse older iteration history to keep files compact.

Agent-Logs-Url: https://github.com/githubnext/tsessebe/sessions/d3d310d3-fb04-4119-bdaf-f09ae201065d

Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>

Author: Copilot

.github/workflows/autoloop.lock.yml

@@ -77,6 +77,7 @@ tools:
   repo-memory:
     branch-name: memory/autoloop
     file-glob: ["*.md"]
+    max-file-size: 30720
 
 imports:
   - shared/reporting.md
@@ -1122,6 +1123,7 @@ After each iteration, prepend an entry to the **📊 Iteration History** section
 - **Always** update the state file after each iteration, regardless of outcome.
 - **Update the Machine State table first** — the scheduling pre-step depends on it.
 - **Prepend** iteration history entries (newest first).
+- **Keep the state file compact.** The state file must stay under 30 KB. When prepending a new iteration entry, collapse older iteration entries (beyond the most recent 10) into compressed summary lines (e.g. `### Iters 50–100 — ✅ (metrics 20→55): brief summary`). Also prune Lessons Learned to only the most recent and relevant entries.
 - **Accumulate** Lessons Learned — add new insights, don't overwrite existing ones.
 - **Add to Foreclosed Avenues** only when an approach is conclusively ruled out (not just rejected once).
 - **Respect Current Priorities** — if a maintainer has written priorities, follow them in your next proposal.