Skip to content

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
mainfrom
chore/prism-code-0-9-2
Draft

humuhumu33 wants to merge 2 commits into
mainfrom
chore/prism-code-0-9-2

Conversation

@humuhumu33

Copy link
Copy Markdown
Contributor

What this does

The shell carried prism-code's journey and browser files at 0.8.0. npm's latest is 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_CODE is "0.9.2" in the three tools that name it: studio/tools/prism_journey.mjs, kernel.mjs and prism_template.mjs.
  • node tools/prism_journey.mjs copied the files: 39 are now 0.9.2's, byte for byte.
  • The copy list grew, because the version did:
    • stateful.mjs and render-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 of spec.mjs does not load.
    • uorc.mjs: since 0.9.0 archive.mjs and attestations.mjs import it (holo v5).
    • complete.mjs and spec-schema.mjs: the draft form of prism/spec/1, where a model writes only title, fields, rules and otherwise and 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.mjs re-pins all three tools to npm's latest, 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.mjs imports ./stateful.mjs: add it to FILES"), which is what this pull request then added by hand.
  • .github/workflows/prism-code-update.yml runs it each hour and opens a pull request when npm has a newer release. As in template-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 main for 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 template a7a3041, byte for byte.
  • node tools/builder/pack.mjs --check, and tools/builder_commit.test.mjs 6 of 6.
  • shell_parse, self_contained, live_lexlean --check, live_preview --check.
  • live_app 9, live_app_check 4, live_app_prove 4, live_notation 8, approval_queue 7, main_stateful_integration 8: all pass.

Not verified, and why this is a draft

  • The repository's own rules. AGENTS.md requires 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.
  • The browser gates and the kernel. kernel.mjs now 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, which upstream.toml already tracks, so holo-bound identities may move.
  • The workflow itself has not run. It follows template-update.yml's two-job shape and its pinned actions.
  • tools/backlog_workflows.test.mjs test 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 with repairMessage) 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

humuhumu33 and others added 2 commits November 16, 2026 13:06
… 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

No deployments
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