You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(app-bundle): re-extract overlay at v1.18.10-amicode.23 #1725
Problem — The app-bundle overlay is pinned at v1.18.10-amicode.19 (extracted 2026-09-03); the fork lineage has since advanced through .20–.23. Notably .23 carries the digit-led single-$ inline-math fix (harmoniqs/opencode#376, closes harmoniqs/opencode#375), so chat LaTeX like .53\times10^{-5}$ stays raw in the bundled app until the overlay catches up. Approach — Run extract_overlay.mjs --tag v1.18.10-amicode.23 (rewrites overlay files + manifest hashes together), require drift_gate.mjs exit 0, and run the marked math tests in the materialized tree to prove the bundle carries the fix.
Acceptance Criteria
manifest.json pins fork_tag: v1.18.10-amicode.23 with matching fork_sha
drift_gate.mjs exits 0 (overlay bytes == fork at the pinned tag)
Materialized-tree math tests pass, including the digit-led regression cases from opencode#376
No hand-edits to overlay files (extraction is the only writer)
Notes
The delta vs the .19 pin includes the intervening fork merges .20–.22 (pdfjs-dist / session-work-column infra for amicode#721) — not just the math fix. That is the designed extraction flow: the overlay tracks the fork tag wholesale.
Follows harmoniqs/opencode#375/#376. After merge: scripts/rebuild_amicode_locally.sh + window reload to verify the original failing snippet renders.
Activity