feat: lock=ignore, none-as-footgun-guard, fix integrity story & bundle scope check

[exo-nikita]

Three concerns from the high-level audit, addressed together because they all touch the constructor's per-dir block in state.js and the Config getters.

1. Drop the tautological hash check (lock=none + bundle=load)

The previous code populated this.hashes from sha512(bundle source) and
then asserted that the same hash matched sha512(source) in getFile —
zero protection, while reading like an integrity check.

The intent for lock=none + bundle=load is correct: the bundle is the
source of truth, and shipping hashes-of-the-same-sources in the same file
is redundant. Express that directly: stop populating hashes from the
bundle, and skip the hash assertion in getFile when !useLockfile.
lock=frozen + bundle=load still verifies (lockfile's hashes vs bundle's
source).

2. Verify bundle scope on load

The lockfile loader does if (frozen) assert.equal(json.config.scope, this.config.scope). Mirror that for bundle loading — a bundle saved with scope=full loaded under scope=node_modules (or vice versa) is now rejected in frozen mode.

3. lock=ignore mode; none becomes a footgun guard

Today lock=none silently skips an existing stasis.lock.json, and bundle=ignore behaves the same as bundle=none (both throw on file presence). Repurpose none as the implicit default that refuses to silently ignore an existing lockfile/bundle, and add ignore as the explicit "I know, leave it alone" mode for both lock and bundle:

mode \ on disk	file present	file absent
lock=none (default)	reject (NEW)	OK
lock=ignore (NEW)	tolerate, don't load, don't write	OK
bundle=none (default)	reject (unchanged)	OK
bundle=ignore	tolerate (FIX — previously rejected like none)	OK

useLockfile now also excludes ignore (parallel to bundle). bundle=load now allows lock=ignore alongside lock=frozen / lock=none. CLI banner adds ignore to --lock and updates the bundle=load error message. =none is intentionally not in the help — it's the implicit default, and surfacing it would defeat the footgun guard.

Tests (104/104 passing)

• Config: lock=ignore getters; bundle=load works with lock=ignore.
• CLI:
  • lock=none rejects an existing lockfile (explicit and implicit-default forms).
  • lock=ignore tolerates an existing lockfile and doesn't touch it.
  • lock=ignore + bundle=load serves from the bundle without lockfile interaction.
  • bundle=none rejects an existing bundle file.
  • bundle=ignore tolerates an existing bundle and leaves it untouched (regression for the previous "ignore behaves like none" bug).
  • lock=frozen + bundle=load rejects a bundle with a mismatching scope.
  • --bundle=load --lock=replace is rejected (added an explicit test alongside the existing lock=add one).

Test plan

• pnpm test — 104/104 pass
• pnpm lint — clean
• Manual end-to-end: lock=frozen+bundle=load blocks tampered bundle with ERR_ASSERTION; lock=ignore+bundle=load runs the tampered payload (intentional, documented); lock=none with an existing lockfile fails with Unexpected …/stasis.lock.json with config.lock = 'none'.

---

Generated by Claude Code