[autoloop-progress] docs: update Go migration progress page to iteration 24#26
Merged
mrjf merged 2 commits intoMay 13, 2026
Merged
Conversation
- Advance status table to iteration 24 (best metric 9.89%, ~7,092 migrated lines) - Expand migration progress table through iter 24 with workflow run links - Expand migrated modules table to all 24 modules from migration-status.json - Add branch-reset caveat explaining iter-13 JSON baseline vs iter-24 reality - Refresh manifest-ops benchmark with fresh python3 run (923x check_collision at scale) - Add Go build/test validation signals table - Update Next up from memory Future Directions - Update last-updated timestamp to 2026-05-13 15:14 UTC Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
added
automation
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
docs/src/content/docs/progress/autoloop-go-migration.mdxwith data sourced frommemory/autoloop:python-to-go-migration.md,benchmarks/migration-status.jsononautoloop/python-to-go-migration, and a fresh local run ofscripts/benchmark_manifest_ops.py.What changed
Latest status — advanced from iteration 4 (1.15%) to iteration 24 (best metric 9.89%, ~7,092 of 71,696 original Python lines).
Migration progress table — expanded from 4 rows to a full summary of all 24 iterations with workflow run links for iters 1–4, 13, 22, 23, and 24.
Migrated modules table — expanded from 11 modules to all 24 modules recorded in
benchmarks/migration-status.json(the iter-13 stable baseline). A new caution callout explains the branch-reset caveat: iteration 24 additionally committed 30 Go packages on the branch that are not yet reflected in the JSON.Benchmark signals — refreshed
scripts/benchmark_manifest_ops.pynumbers from a livepython3run (e.g.check_collisionreaches 923x speedup at large-monorepo scale). Added a note on the expectedcleanup_empty_parentsregression at scale. Added a Go build/test validation signals table drawn from Autoloop memory.Next up — replaced stale utils targets (already migrated) with the current
Future Directionslist from the memory file:install/pipeline.py,install/sources.py,install/services.py,policy/discovery.py,deps/github_downloader.py, and the branch-reset structural issue.Last updated —
2026-05-13 15:14 UTC.Sources used
memory/autoloop:python-to-go-migration.mdautoloop/python-to-go-migration:benchmarks/migration-status.jsonscripts/benchmark_manifest_ops.py(python3 local run)How to test
The build should succeed with no broken link warnings on the updated page.