Skip to content

scorekit settings pin + 2026-07-24 audit follow-ups - #40

Merged
jamiesun merged 2 commits into
mainfrom
scorekit-pin-and-audit-followups
Jul 24, 2026
Merged

scorekit settings pin + 2026-07-24 audit follow-ups#40
jamiesun merged 2 commits into
mainfrom
scorekit-pin-and-audit-followups

Conversation

@jamiesun

Copy link
Copy Markdown
Contributor

Two changesets, one commit each.

feat(scorekit): settings-pinned binary path

  • New Settings → scorekit binary field: an absolute-path pin resolved after SCOREBENCH_SCOREKIT but before PATH/well-known prefixes, so machines with several scorekit versions can pick one without env-var gymnastics.
  • Startup handshake reports which discovery channel won; tested range widens to >=0.3.0, <0.5.0; the pin is seeded at startup and re-seeded on every settings save.
  • Shape-only validation keeps a later-deleted binary from making settings unloadable; existence is checked at locate time.
  • README, docs-site, roadmap acceptance matrix updated (locate_settings_pin_wins_over_path_and_well_known, locate_settings_pin_must_be_executable).

chore: close 2026-07-24 audit findings

  • set-version.mjs now writes all five version sources (tauri.conf.json, package.json, package-lock.json, Cargo.toml, Cargo.lock); lagging manifests synced from 0.1.0 to 0.3.3.
  • check-tag-version.mjs (release tag gate) fails early on cross-source version drift.
  • esbuild declared as a devDependency for the demo:* scripts.
  • Roadmap commitments made falsifiable: personal_instructions parsing scheduled for removal in 0.5.0; shared weather-helper extraction recorded as a hard prerequisite for the next M9 imagery.
  • docs/verification.md dated entry with evidence.

Verification

cargo fmt --check clean · cargo clippy --all-targets --all-features -- -D warnings clean · cargo test 121 + 1 boundary test passed · npm test 141 tests passed · npm run check 0 errors/warnings.

jamiesun and others added 2 commits July 24, 2026 14:58
Add Settings → scorekit binary: an absolute-path pin that beats PATH and
well-known prefixes (SCOREBENCH_SCOREKIT still overrides), so machines
with several scorekit versions can choose one without env-var gymnastics.
The startup handshake reports which discovery channel won, the tested
range widens to >=0.3.0, <0.5.0, and the pin is re-seeded on every
settings save. Docs and acceptance matrix updated.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- set-version.mjs writes all five version sources (tauri.conf.json,
  package.json, package-lock.json, Cargo.toml, Cargo.lock); synced the
  lagging manifests to 0.3.3
- check-tag-version.mjs fails on cross-source version drift before
  comparing the release tag
- esbuild declared as a devDependency for the demo:* scripts
- roadmap: personal_instructions parsing scheduled for removal in
  0.5.0; shared weather-helper extraction marked a hard prerequisite
  for the next M9 imagery
- verification.md dated entry with gate evidence

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@jamiesun
jamiesun merged commit 62955c1 into main Jul 24, 2026
4 checks passed
@jamiesun
jamiesun deleted the scorekit-pin-and-audit-followups branch July 24, 2026 07:00
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