release: merge back 0.2.1-alpha.2 — binary pin amicode.3 + 0.2.1 manifest - #252
Merged
Conversation
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.
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.
Same pattern as the 0.2.0 merge-back (#239). The release line carried alpha.1/alpha.2 after #239, so
mainandrelease/0.2.0diverged 6/6.What main gets:
Main's side of the divergence is the two-tier skill surfaces (#244) — disjoint files, expecting a clean merge.