feat: amicode-managed Julia setup via juliaup (#8, layers 1-3) - #151
Merged
Conversation
julia_setup.ts: parse Manifest minor, detect juliaup + channel, gate (shouldOfferJuliaSetup), resolveChannelJulia (channel binary for the --julia plumbing, no global-default clobber), buildSetupSteps (consented juliaup install -> juliaup add <minor> -> instantiate). 13 unit tests.
…rs 2-3) extension.ts: runJuliaSetup + amicode.setupJulia command + first-run gate (shouldOfferJuliaSetup), mirroring the vault-setup flow. Runs the juliaup install -> juliaup add <minor> -> instantiate steps in a visible terminal (the consent surface). install.sh: offer juliaup install when Julia is absent, add the pinned-minor channel, and route its own calls through 'julia +<minor>' (no global-default clobber).
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.
#8: amicode manages the Julia toolchain via juliaup instead of dying and
telling the user to do it by hand. Pins the juliaup channel to the Manifest's
minor (
1.12→ latest patch, e.g. 1.12.6 vs the pinned 1.12.3 — a patchdrift install.sh already treats as fine), never touching the user's global
default.
What
substrate/julia_setup.ts(core, 13 unit tests) — parse Manifest minor,detect juliaup + channel,
shouldOfferJuliaSetup()gate,resolveChannelJulia()(channel binary for the existing
--juliaplumbing),buildSetupSteps()(juliaup install →
juliaup add <minor>→ instantiate).extension.ts—runJuliaSetup+amicode.setupJuliacommand + first-rungate, mirroring the feat: Run Inspector aesthetic pass — status badge, metric cards, branded chrome #13 vault-setup flow. Runs the steps in a visible
terminal (the consent surface for the network installer).
install.sh— offers a juliaup install when Julia is absent, adds thepinned-minor channel, and routes its own calls through
julia +<minor>.Behavior
julia(what the agent runs today) resolves to it → solves work with no further wiring.
1.12channel;routing the runtime explicitly through it is the follow-up below.
Verified
tscclean; fast suite 598 pass / 4 skip;bash -n install.shclean;13 julia_setup unit tests.
Follow-up (layer 4, deliberately scoped out)
Route the solve runtime through the managed channel for the already-has-juliaup
case: add a
{{JULIA_BINARY}}substitution (like{{JULIA_PROJECT}}) to AGENTS.md'samico-run … --julialaunch + instantiate lines, resolved viaresolveChannelJulia.Touches the agent prompt + solve path, so it wants its own e2e-validated PR.
Also future: entitlement-gated package management (the paid Piccolissimo set) —
today only the pinned public Manifest is instantiated.