Repository navigation
feat(prism-code): system and auth command groups (Part of #446) - #621
Merged
Merged
Conversation
…iew's glossary (#347) The developer view of #346 is declared once, as the LexLean model bindings/src/Foundation/Views/V1/Developer.lex.tex: the Docker-aligned terms over the canonical terms they name, the other words of the surface and the deprecated aliases. Its certified export is vendored into xtask, and `cargo xtask check-developer-view` (part of `cargo xtask validate`) runs it over sdk/npm/prism-code/developer-surface.json, refusing a name outside the glossary, a canonical term the view renames, a Docker verb taken before Prism has its behaviour, and an undeclared alias. The model renders docs/developer-glossary.md. A prism-code test keeps developer-surface.json equal to the CLI help, the delegated verbs and the client. The check found two canonical terms on the surface, now renamed with deprecated aliases through 0.8 that each print one warning: `history` is `record`, and `--holo` (replay, dev) is `--image`. Verbs handed to prismpm keep prismpm's flags. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N4k8eo7mrfwURU1WM
…#347) check-developer-view compares docs/developer-glossary.md byte for byte with the page the model renders, so a CRLF checkout would report drift. Pin it to LF, as COMPLIANCE.md is. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N4k8eo7mrfwURU1WM
…nt (#347) The glossary maps the developer view's words onto the canonical terms and names the issues that build the waiting verbs, as docs/vocabulary.md maps the docs' terms onto the repository's names, so it is excluded with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N4k8eo7mrfwURU1WM
PACKAGE_LIMIT was one comment line that every change growing the package edited, so parallel v0.5 PRs would all conflict on it. The cap is now the sum of scripts/package-allowances/*.json, each holding a kib and a reason. The 19 allowances on the old line move over unchanged (1584 KiB in total, the same 1622016 bytes), and the package test reads the limit instead of repeating the number. Part of #441 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QVSkS6PGopegNeztG
prism-code system info|version|events|df|prune and prism-code auth
login|logout as src/cli/<module>.mjs modules exporting { verbs, help },
each verb async (argv, io) => exitCode, for the group dispatcher to wire.
- info and version name the toolchain and builder image the project's
prismpm.lock pins; events reads create/start/die/destroy from the
container store and follows it until --until; prune asks unless --force.
- login checks the credential with GET /v2/ (new registry client ping)
before storing it where Docker would; the password comes only from
--password-stdin or a non-echoing prompt, -p/--password are refused,
and no secret reaches stdout, stderr or an error.
- DK-44 owns test/system-auth-cli.test.mjs (15 tests).
- Package allowance: scripts/package-allowances/system-auth-cli.json, 20 KiB.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3P3wYbBfAqXcoqi2cd
…to claude/project-thread-4igtmt
… of #446) The follow test raced a slow runner against a 1.5 s --until: the run's start and die landed after it. Follow now also ends on io.signal, the test stops it once the run and removal are seen, and a separate test covers an --until still ahead. Without --since, events already in the store are not replayed, so only what happens from now on is new, as with docker events. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3P3wYbBfAqXcoqi2cd
# Conflicts: # sdk/npm/prism-code/scripts/check-package.mjs # sdk/npm/prism-code/test/package.test.mjs
The group files compose several modules, as the client does, so the whole folder is owned by client and check-modules rule 2 holds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3P3wYbBfAqXcoqi2cd
`prism-code <module> <verb>` dispatches through src/cli/index.mjs to one file per module, so each workstream adds verbs to its own file and never to bin/prism-code.mjs. `images build|inspect|pull|push|verify` and `containers run|rm|inspect` name the flat verbs, which stay. A group file may also give its verbs as functions with a verbatim `help` block, and `aliases` for top-level spellings (`login` for `auth login`). The developer surface reads a group line's verb as the word after the module, so `images push` is checked against the glossary as `push`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QVSkS6PGopegNeztG
… (Part of #446) Merges the group dispatcher branch (#625), adds system and auth to FILES in src/cli/index.mjs, and regenerates developer-surface.json; check-developer-view passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3P3wYbBfAqXcoqi2cd
…and own src/cli/ cli.json is compared with the verbs --help prints, so the two group words join it, and the generated skill table follows. src/cli/ is owned by the client, which composes the modules, with the same entry as #621. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QVSkS6PGopegNeztG
…to claude/project-thread-4igtmt
… skill (Part of #446) The docs test compares cli.json's verbs with the words --help prints, so system, auth, login and logout get rows (usage without pipes, which the skill's command table would escape), the alias help is one line per verb, and the skill and its package copy are regenerated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3P3wYbBfAqXcoqi2cd
…Part of #446) A client keeps each container it has read, so following through one client saw a container that was created and later started as created forever. events now lists through a new client each turn, and a record removed between listing and reading is read again on the next turn. The follow test now starts a container the stream has already seen. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3P3wYbBfAqXcoqi2cd
…-4igtmt # Conflicts: # STABILITY.md # sdk/npm/prism-code/CHANGELOG.md
…-4igtmt # Conflicts: # CHANGELOG.md # sdk/npm/prism-code/CHANGELOG.md
…-4igtmt # Conflicts: # sdk/npm/prism-code/bin/prism-code.mjs # sdk/npm/prism-code/developer-surface.json # sdk/npm/prism-code/src/cli/index.mjs # sdk/npm/prism-code/test/fixtures/package-files.json
afflom
pushed a commit
that referenced
this pull request
Nov 12, 2026
…ore (Part of #349) #621's system verbs were written before the store existed. df now counts images (and lists them with -v), info gives the stored count, and prune takes -a|--all and prints the images it deleted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3NmrRTpngJ3TFNocur
This was referenced Nov 12, 2026
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.
Requested by Alex · project thread
v0.5 workstream WS4: the CLI half of #446 (prism.system) and login/logout of #447 (prism.auth).
What
src/cli/system.mjs:prism-code system info|version|events|df|prune.infoandversionname the package, holo format, runtime, and the toolchain and builder image the project'sprismpm.lockpins (--project, the current folder by default). There is no daemon, soeventsreads create/start/die from the container records and reports a record that disappears as destroy. It follows the store until--untilor Ctrl-C, and takes--since/--untilas ISO 8601, Unix seconds or10m, plus--filter action=|event=|id=|container=.df -vlists the records.pruneasks on a terminal and needs--forcewithout one. Every verb takes--json.src/cli/auth.mjs:prism-code auth login|logout, exportingaliasesfor the top-levellogin/logout.loginchecks the credential with the registry (GET /v2/, through a newping()on the registry client) before it stores anything, asdocker logindoes. The password comes only from--password-stdinor a prompt that does not echo.-p,--passwordand--password=are refused without quoting them, and a stray positional word is counted, not printed.logoutwarns whenGHCR_TOKENstill supplies a token, without printing the token.{ verbs, help }. Each verb isasync (argv, io) => exitCode, and a usage error prints the group's help and returns 64. Per the lead's conventions,bin/prism-code.mjsis untouched; the lead wires these in when the group dispatcher lands.test/system-auth-cli.test.mjs(15 tests) with a conformance case, a feature scenario, andSPEC.md/CONFORMANCE.mdregenerated. The fake registry now challengesGET /v2/.scripts/package-allowances/system-auth-cli.json(20 KiB). This branch merges ci(prism-code): sum the package cap from one allowance file per change (Part of #441) #618's branch, so the cap is computed the new way. When ci(prism-code): sum the package cap from one allowance file per change (Part of #441) #618 lands, that part of the diff goes away.registry.authandstore.credential-input.Test
node --test test/system-auth-cli.test.mjs: 15/15 pass.npm test: everything passes exceptreference-archives.test.mjs, which fails locally on main too.cargo xtask validate-model: clean, 247 ids.cargo test -p repo-conformance --test conformance conformance_dk_44: passes.Generated by Claude Code