Skip to content

Keep local notes out of the public tree; build and install linux-arm64 - #47

Merged
iamhyc merged 3 commits into
mainfrom
chore/clean-public-tree
Nov 8, 2026
Merged

iamhyc merged 3 commits into
mainfrom
chore/clean-public-tree

Conversation

@iamhyc

@iamhyc iamhyc commented Nov 8, 2026

Copy link
Copy Markdown
Member

What and why

Two things: the public tree carried local development notes, and the launcher promised a
platform the release never built.

Local notes out of the tree. scripts/debug/ (16 one-off reverse-engineering probes, two
carrying a plaintext p12 password), docs/agents/ and AGENTS.md describe a development
setup rather than the tool, and this repository is public. They are removed and gitignored so a
stray git add -A cannot bring them back. docs/published/ stays — those three files are
compiled into the binary by src/support/skill.rs.

Platforms agree. npm/package.json declared five platform packages while release.yml
built three, so npm i -g @hvolt/cli on an Intel Mac or an arm64 Linux host installed a
launcher whose binary never existed:

  • release.yml gains a linux-arm64 lane on ubuntu-24.04-arm, building
    aarch64-unknown-linux-gnu natively
  • install.sh maps aarch64/arm64 to that archive and names the real support list when it
    refuses a platform
  • @hvolt/cli-darwin-x64 is dropped rather than shipped empty

Both sides now list four: darwin-arm64, linux-arm64, linux-x64, win32-x64.

Checks

  • cargo fmt --all --check is clean
  • cargo clippy --all-targets -- -D warnings finishes without warnings
  • cargo test passes
  • Behaviour changes come with a test
  • Any claim about engine/SDK/device behaviour states how it was measured
  • --help text and comments naming a changed command are updated
  • CHANGELOG.md has an entry if the CLI surface or project format changed

Tested with

cargo fmt --all --check                       → FMT_OK
cargo clippy --all-targets -- -D warnings     → 0
cargo test                                    → 533 passed; 0 failed; 4 ignored
sh -n install.sh                              → syntax OK
node -p Object.keys(optionalDependencies)     → darwin-arm64 linux-arm64 linux-x64 win32-x64
npm pack --dry-run (@hvolt/cli)               → 4 files
grep -rn "docs/agents" --include=*.md         → only a 2026-11-04 report that records history

The arm64 artifact itself can only be confirmed by the release run; this PR does not cut one.

HANDOFF.md is an agent-side document. It has nothing to do with the tool and
it entered the tree by accident; the file stays on disk, untracked.
This repository is public. These describe a local development setup rather
than the tool, so they leave the tree:

- scripts/debug/ — 16 one-off reverse-engineering probes, two of which carry a
  plaintext p12 password
- docs/agents/ and AGENTS.md — agent-side notes

Both are gitignored so a stray 'git add -A' cannot bring them back.
docs/published/ stays: those three files are compiled into the binary by
src/support/skill.rs.
…kage

npm declared five platform packages while release.yml built three, so an
Intel Mac or an arm64 Linux host installed a launcher whose binary never
existed.

- release.yml: add a linux-arm64 lane on ubuntu-24.04-arm, building
  aarch64-unknown-linux-gnu natively
- install.sh: map aarch64/arm64 to that archive and name the real support
  list when it refuses
- npm: drop @hvolt/cli-darwin-x64 rather than ship a package with nothing
  behind it

Measured: npm pack --dry-run on @hvolt/cli lists 4 files; the launcher's
optionalDependencies and npm/platforms/ now agree at four entries.
@iamhyc
iamhyc merged commit aecbd5e into main Nov 8, 2026
4 checks passed
@iamhyc
iamhyc deleted the chore/clean-public-tree branch November 8, 2026 16:37
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