release: merge back 0.2.1-alpha.2 — binary pin amicode.3 + 0.2.1 manifest by aarontrowbridge · Pull Request #252 · harmoniqs/amicode

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridge · 2026-08-04T03:14:01Z

Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so main and release/0.2.0 diverged 6/6.

What main gets:

the repin to the fork's https://github.com/harmoniqs/opencode/releases/tag/v1.18.10-amicode.3|v1.18.10-amicode.3 runtime (thinking-block two-row fix, B7: researcher/librarian retrieval tools + slim prompts #114)
the manifest base version 0.2.1 (tag carries the channel suffix)
the LaTeX / buried-output / chrome-fixes release packaging

Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.

Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

…e editor The framed app renders LLM output with file:// links (vault notes, run artifacts) but cannot open local files; the extension host can. Adds an open-file bridge message kind to chat_bridge, gated: file:// URLs only, resolved path must be absolute, bounded (<=4096), and exist on disk. Wired through ChatPanel and the deck shell message forwarder.

feat(extension): open-file bridge — chat links open local files

… (internal) Repin the vendored opencode to the fork's v1.18.10-amicode.2 release (PR #110: one home per chrome surface, closes amicode#105; plus marked-math LaTeX rendering restored, buried working-context output in message parts, edit-row model). Also carries extension-side #240 (open-file bridge) and #241 (Notturno vocabulary). sha256s from the fork release notes; UI gate verified by the release workflow. Internal channel — GitHub Release only, not Marketplace.

…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

… (internal) The fork's PR #114: the working indicator no longer shatters beside long activity headings (two-row grid owns the H-mark; meta rendered from mount; a11y single-announce). sha256s from the fork release notes; manifest stays at base 0.2.1, tag carries -alpha.2.

aarontrowbridgeand others added 6 commits August 2, 2026 12:06

docs(context): Notturno — the scheduled agentic-work context
afa5ee9
Canonical vocabulary for the nightly/scheduled agentic jobs (GitHub Actions Slack automation today, local repo/Julia jobs as it grows); subsumes the dream cycle. Avoid: cron, scheduler, night shift.

Merge pull request#240from harmoniqs/feat/open-file-bridge
e273f9f
feat(extension): open-file bridge — chat links open local files

release: manifest carries the base version (0.2.1) — the tag carries …
28645fe
…the channel suffix The release version guard strips -alpha.N from the tag and requires equality with the manifest, so installed builds show the base version.

aarontrowbridge merged commit f4db868 into mainAug 4, 2026
8 checks passed