Skip to content

v1.5.2

Choose a tag to compare

@devsolux devsolux released this 16 Oct 16:42
· 47 commits to main since this release

1.5.2 — 2026-10-16

SoundCraft joins the root-confined apps; card rechecks for the seven pins
moved since 1.5.1; fixes from a security, silent-failure, Python and
consistency review (release-workflow token split and merge pinning, refresh
guards, hash-locked probe SDK, setup and doctor hardening); and a CI fix that
removes the failing checks on the bot's "Refresh Craft release pins" pull
requests.

  • Release workflow: the verify jobs check out the exact commit the refresh
    job pushed, and the merge job merges only that commit
    (--match-head-commit) of a same-repository pull request (a fork could
    name its branch bot/releases). A missing pull request now fails the
    merge job instead of ending green, and the pull request body no longer
    claims verify results before they exist. make check enforces both rules.

  • scripts/refresh_releases.py stops instead of pinning when an app's latest
    release is older than its pin, when a pinned tag now points at another
    commit, or when an asset is re-published under an unchanged tag and name;
    it moves the reviewed date only with a pin, so an unchanged day opens no
    pull request (#5 was such a date-only change), and it restores the old
    manifest if the new one fails validation. New tests cover the guard.

  • make check pins the manifest's signers to this repository's release
    workflow on main and the Apple team DJ6XS33FX8, so a pull request cannot
    swap the trust root together with matching signatures.

  • setup: macOS verifiers run as /usr/sbin/spctl and /usr/bin/codesign,
    not from PATH; promote checks the candidate's bytes against the verified
    hash before replacing the live binary; every subprocess has a 30-minute
    timeout reported as an error; the state directory and binaries, like the
    lock and evidence, must lie outside the workspace; a Windows .cmd host
    shim refuses paths with characters cmd.exe would reinterpret and prints
    the manual command; a requested host CLI missing from PATH is warned about
    even when another host remains; an existing registration with the right
    command but extra env, cwd or another scope is reported with a warning;
    and the overall status is an allow-list of success states.

  • The SoundCraft version guard accepts only ASCII x.y.z followed by a space,
    parenthesis or the end, so 0.7.0-rc1 and non-ASCII digits are refused;
    setup treats such a pin as stale even at the manifest commit, so
    --upgrade rewrites the label instead of looping on the refusal.

  • setup --remove keeps the binary, pin and evidence when a registration it
    must keep still launches that binary (for example an older launch's
    arguments) and names the mcp remove commands, instead of leaving the host
    entry pointing at a deleted file; a registration that differs only in its
    arguments is now reported as such, not as "a different command".

  • verify-artifact --expected-sha256 "" fails instead of skipping the digest
    check; setup --all --app <x> is refused instead of quietly installing only
    <x>; --timeout accepts only the probe's (0, 120] seconds before anything
    is downloaded; a non-string workspace id or receipt path is a validation
    error, not a traceback.

  • Release workflow split: the job that downloads, unpacks and signs upstream
    archives and runs repository code now holds only contents: read and
    id-token: write; a separate publish job holds the write token, runs
    only git and gh (through gh auth setup-git, so no token in a URL),
    and receives the files through the pinned actions/upload-artifact v7.0.1
    and actions/download-artifact v8.0.1. The verify jobs also run
    scripts/build.py check on the published commit. A test keeps the split.

  • scripts/refresh_releases.py --accept <app> lets one app through the
    downgrade/re-publish guard after a maintainer reviewed it by hand.

  • The first run of the split release workflow (run 38932488545) moved
    VectorCraft to v0.12.0 and merged pull request #6 with no failing check.
    The card was rechecked at the new tag (same flags and 32 tools; new
    query/brief discovery, stroke options, vertical text, ai export) and
    corrected: the command_batch tool never rolls back, even with atomic;
    only the engine command command.batch puts the documents back.

  • CI: the 0b97a1f push broke ci.yml (an unquoted run: value containing
    :all: -r is a YAML mapping, so GitHub could not load the workflow and the
    run failed in 0 s); the value is quoted and make check now refuses any
    unquoted run: value with ": " in either workflow. CI's pull_request
    trigger ignores pull requests that change only config/releases.json,
    config/signatures.json and plugins/storytold/**: on the bot's
    "Refresh Craft release pins" pull requests (#1 to #5) GitHub never started a
    job and the run failed when the merge deleted bot/releases; the release
    workflow's own check, test and three-OS verify jobs gate them.

  • The probe SDK is hash-locked: requirements-probe.lock (uv universal
    resolution, 28 packages, every wheel's SHA-256, pywin32 for Windows only)
    ships with the plugin, and setup's probe venv, make setup-probe and the
    CI SDK job install only from it with --isolated --require-hashes --only-binary=:all:, so no source build runs and no PIP_* variable or pip
    configuration can redirect the index. make lock-probe regenerates it and
    make check refuses a pin without a hash or an mcp that disagrees with
    the SDK version.

  • codex/claude mcp get: only the host's own "No MCP server named" answer
    means "not registered"; any other failure is an error in register, an
    uninspectable entry that keeps the binary in --remove, and
    registration_unknown in setup --list, whose probe_evidence now shows
    the recorded probe status instead of "a file exists".

  • doctor: an unreadable host config makes a server registration_unknown
    instead of "not registered" or "not installed"; a corrupt lock is reported
    in host_config_errors instead of being read as empty; the printed setup
    command quotes its path and says python on Windows.

  • setup: an unacknowledged unconfined app is reported
    needs_acknowledgement and skipped while the other selected apps are still
    processed; lock updates are serialized with a <lock>.writing marker so
    parallel runs cannot drop each other's pins; --remove archives the
    candidate and call evidence instead of deleting it; preflight, probe
    and configure derive the output root from --work-root unless
    --output-root or CRAFT_OUTPUT_ROOT is given.

  • Docs: the READMEs say what the confined apps really read (the whole
    workspace) and write (outputs/); operations corrects the unconfined-app
    rule, adds not_installed to the doctor table and documents the workflow
    guarantees and the job-less CI runs on bot pull requests; verification and
    the source ledger are brought up to date; CONTRIBUTING lists
    make test-sdk; the plugin README names --acknowledge-unconfined and
    --replace for upgrades; .claude/CLAUDE.md mentions make github-pull.

  • config/apps.json launches SoundCraft with mcp --automation-read-root {work} --automation-write-root {outputs} (read_write), the flags its CLI
    ships since 0.7.0. ROOTED, the inactive launch templates, the catalog
    tests (five read_write, seven os_only), make setup-confined (six
    apps), the card, the safety list, the READMEs, operations and acceptance
    follow; SoundCraft no longer needs --acknowledge-unconfined.

  • SoundCraft before 0.7.0 silently ignores unknown mcp flags, so the new
    launch would run an older binary unconfined. preflight, and with it
    setup, probe and configure, now refuses a SoundCraft pin older than
    0.7.0 or without a readable version and names
    setup --app soundcraft --upgrade --replace; a new catalog test covers it.

  • Existing installs: run setup --app soundcraft --upgrade --replace. On the
    maintainer's Mac that moved SoundCraft from 0.6.1 to 0.7.0, probed it with
    the root arguments and replaced both host registrations (see the
    verification report). Denial of an outside path was not tested.

  • The scheduled run 38717981671 merged pull request #4 (CADCraft 0.7.0,
    EffectCraft 0.10.0, FilmCraft 0.8.0, GridCraft 0.7.0, LightCraft 0.8.0,
    PhotoCraft 0.9.0, SoundCraft 0.7.0), with the real setup passing on the
    Linux, Windows and macOS runners; run 38883983466 merged #5, which changed
    only the review date.

  • The seven cards were rechecked at the new tags; no catalog launch flag or
    smoke tool changed. CADCraft's card covers find_text, --lazy/--launch
    and the new AutoLISP, whose file functions reach any path, so the safety
    list now names it among scripts. GridCraft's card corrects .xls (partial
    BIFF8 import, not refused) and lists the new save refusals. PhotoCraft's
    covers the lossy-ORA copy rule, dpxBits and Krita import, LightCraft's
    rendereddng, and SoundCraft's the root flags 0.7.0 accepts (adopted
    above) plus bounce_mix overwriting. EffectCraft's and
    FilmCraft's only change their recheck dates. The source ledger records it.

  • AGENTS.md and .claude/CLAUDE.md: pull main first because the workflow
    merges on its own, finish every pin move with a card recheck and a ledger
    entry, treat a launch-flag change as a catalog change with local binary
    acceptance and --upgrade --replace, and push, tag or release only on the
    operator's request. The Skill notes that cards describe the pinned release
    and that an older installed binary's live tool list wins.