Repository navigation
Re-pin prism-code to 0.9.2, and keep it current with an hourly re-pin - #234
Draft
humuhumu33 wants to merge 2 commits into
Draft
humuhumu33 wants to merge 2 commits into
humuhumu33 wants to merge 2 commits into
Conversation
… files byte for byte Since 0.9.0 the checker, renderer and reader import stateful.mjs and render-stateful.mjs, and the archive reader imports uorc.mjs, so the copy list names them. complete.mjs and spec-schema.mjs, the draft form of prism/spec/1, are carried and not yet called. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… pull request Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch has not been deployed
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
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.
What this does
The shell carried prism-code's journey and browser files at 0.8.0. npm's
latestis 0.9.2. This re-pins to it, and adds a way to stay current without giving up the pin.1. Re-pin to prism-code 0.9.2
PRISM_CODEis"0.9.2"in the three tools that name it:studio/tools/prism_journey.mjs,kernel.mjsandprism_template.mjs.node tools/prism_journey.mjscopied the files: 39 are now 0.9.2's, byte for byte.stateful.mjsandrender-stateful.mjs: since 0.9.0 the checker, the renderer, the strict reader and the session compiler import them (prism/spec/2). Without them the shell's copy ofspec.mjsdoes not load.uorc.mjs: since 0.9.0archive.mjsandattestations.mjsimport it (holo v5).complete.mjsandspec-schema.mjs: the draft form of prism/spec/1, where a model writes onlytitle,fields,rulesandotherwiseand Prism derives the rest the same way every time. They are carried and not yet called by the shell.What the shell gains by the copy alone, with no code of its own changed: the comparison word of a condition is read for the kind of field it compares (0.9.2), refusals that say which part is wrong, and the speed fix for large specs (the spec document judges each candidate request once).
2. Stay current, automatically, with the pin kept
studio/tools/prism_code_update.mjsre-pins all three tools to npm'slatest, copies the files, and holds the result to two things: every file is that version's, and every import the copied files make resolves inside the shell. Run on the 0.8.0 tree it refuses a bare bump and names what is missing ("shell/prism/spec.mjsimports./stateful.mjs: add it to FILES"), which is what this pull request then added by hand..github/workflows/prism-code-update.ymlruns it each hour and opens a pull request when npm has a newer release. As intemplate-update.yml, the job that installs the package has read permission only and hands over an inert patch; the job that can write applies it and runs nothing from it. It merges nothing.It is a re-pin on a schedule, not an unpinned import at run time: the byte-for-byte gate is what makes a spec mean here what it means to
npx prism-code, and it stays.Checked
Locally (Windows, Node 22.21.0), on this branch and on unmodified
mainfor comparison, with the same results on both:node tools/prism_journey.mjs --check: 39 files, byte for byte.node tools/prism_template.mjs --check: Forge's commit is prism-code 0.9.2's on templatea7a3041, byte for byte.node tools/builder/pack.mjs --check, andtools/builder_commit.test.mjs6 of 6.shell_parse,self_contained,live_lexlean --check,live_preview --check.live_app9,live_app_check4,live_app_prove4,live_notation8,approval_queue7,main_stateful_integration8: all pass.Not verified, and why this is a draft
AGENTS.mdrequires a capability to begin as a registered ID, a scenario and a failing test, and the model to be updated first. The re-pin is maintenance of an existing pin. The hourly workflow is a new capability, and I have not written its model record: the model is this project's, and I do not know which ID it should take. Either register it, or drop the second commit and keep the re-pin.kernel.mjsnow installs 0.9.2; the kernel pin, the experience gate and the browser lanes were not run here. 0.9.0 made holo v5 a breaking change, whichupstream.tomlalready tracks, so holo-bound identities may move.template-update.yml's two-job shape and its pinned actions.tools/backlog_workflows.test.mjstest 4 fails on this machine with and without this change (a temporary file it expects is missing).Not in this pull request
Calling the draft form from Forge (sending the draft schema, completing with
completeSpec, repairing withrepairMessage) is new code in the shell, not a version bump. Measured upstream with Qwen3 30B on 40 sentences: 40 of 40 drafts accepted first time at a 6.2 s median with a prompt that spells out the format.prism-code 0.9.3 is not published yet; when it is, the workflow added here proposes it.
🤖 Generated with Claude Code