Skip to content

docs(amicode-patches): document how amicode consumes the fork (§5) - #15

Merged
jack-champagne merged 2 commits into
local/amicodefrom
jack/amicode-patches-ui-gate-doc
Jul 28, 2026
Merged

jack-champagne merged 2 commits into
local/amicodefrom
jack/amicode-patches-ui-gate-doc

Conversation

@jack-champagne

Copy link
Copy Markdown
Member

What

Adds §5 "How amicode consumes this fork" to AMICODE-PATCHES.md, documenting the amicode-side build workflow that harmoniqs/amicode#128 introduces:

  • Default vendoring is a pinned release (opencode.lock.json source: release) — teammates need no clone/bun.
  • Iterate via pnpm --filter amicode-v2 opencode:build (invokes script/build.ts with OPENCODE_CHANNEL=dev per gotcha 2, re-vendors).
  • Publish via a tagged release + pnpm --filter amicode-v2 opencode:pin <tag>.
  • assert_ui_gate.sh is the automated form of gotcha 2's grep.

Complements the existing gotcha 2 (the why — channel gate) with the how (consumption workflow), and reinforces §4: only a compiled binary shows amicode surfaces, since run-from-source proxies the public app.

Docs-only; no source changes.

🤖 Generated with Claude Code

jack-champagne and others added 2 commits July 28, 2026 16:32
Cross-references the new amicode-side build DX (harmoniqs/amicode): release-default
vendoring, `pnpm opencode:build` / `opencode:pin`, and assert_ui_gate.sh. Complements
gotcha 2 (the channel gate) with the consumption workflow, and reinforces § 4 — only a
compiled binary shows amicode surfaces (run-from-source proxies the public app).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jack-champagne
jack-champagne force-pushed the jack/amicode-patches-ui-gate-doc branch from f54efea to 9c1683d Compare July 28, 2026 20:33
@jack-champagne
jack-champagne merged commit 9f40952 into local/amicode Jul 28, 2026
1 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant