v0.1.10-buildweek — judging pin

Judging pin (current main)

Commit: 89b8e2348037ece69faf47b6e230a78c3bab6f44
Package version on this tip: @mizore66/faultline@0.1.4

Includes EXT-01, demo narration cleanup (#200), package bump to 0.1.4, and re-asserted SUBMISSION_FROZEN.

git checkout v0.1.10-buildweek
corepack enable
pnpm install --frozen-lockfile
pnpm fl judge-proof

npm registry publish (if still on 0.1.2): Actions → Release and publish → publish_only=true.

v0.1.9-buildweek — judging pin

This is the only release intended for judging

FaultLine Build Week submission pin. Fixes the restored-clean turn-tree staleness bug (HEAD-base staging + oracle equivalence property), includes executable-mode cache fingerprinting, CDX-09 Codex thread IDs in proof manifests, C-1 submission freeze guard, SEC-08 macOS full-chain cold-reader evidence, refreshed turn-snapshot/scale benchmarks, experimental Colima/plugin scaffolds, and carries Sol P0 hardening from v0.1.8.

Judge path

• Codespaces: https://codespaces.new/Mizore66/faultline?ref=v0.1.9-buildweek
• Clone: git checkout v0.1.9-buildweek → corepack enable → pnpm install --frozen-lockfile → pnpm fl judge-proof
• npm: npm i -g @mizore66/faultline@0.1.2

Verify the tag

git fetch --tags
git verify-tag v0.1.9-buildweek

Tag commit: 3ca1bb8adaebf163fe633642a0a4ba20dfb7810a

Historical / not for judging

Tag	Status
v0.1.8-buildweek	Historical previous pin (do not move)
v0.1.7-buildweek and earlier	Historical
v0.1.4	RETRACTED — do not cite

Do not move this tag. Continuous release on main remains paused until after submission.

FaultLine v0.1.4

FaultLine v0.1.4 at 89b8e2348037ece69faf47b6e230a78c3bab6f44 (same tip as judging pin). Publish to npm via Actions → Release and publish → publish_only=true.

FaultLine v0.1.3

Release from main after EXT-01 security review fixes (FL-SEC-001/002/003).

Install

npm i -g @mizore66/faultline@0.1.3
fl --help

Includes

• Hardened Git checkpoint capture (no repository-local fsmonitor RCE)
• Exit-consistent proof-bearing witness PASS/FAIL classification
• SHA-pinned root composite Action dependencies
• EXT-01 disposition record

Verify

git checkout v0.1.3
pnpm install --frozen-lockfile
pnpm test

Build Week submission pins (v*-buildweek) are separate from this npm semver tag. v0.1.8-buildweek / v0.1.9-buildweek are unchanged.

v0.1.8-buildweek — judging pin

This is the only release intended for judging

FaultLine Build Week submission pin. Includes Codespaces .devcontainer, Sol P0 security fixes (hardened repaired-worktree Git; streaming fingerprint size caps; content-bound prevention execution IDs), npm @mizore66/faultline@0.1.2, and a paused continuous-release bot so this freeze stays frozen.

Judge path

• Codespaces: https://codespaces.new/Mizore66/faultline?ref=v0.1.8-buildweek
• Clone: git checkout v0.1.8-buildweek → corepack enable → pnpm install --frozen-lockfile → pnpm fl judge-proof
• npm: npm i -g @mizore66/faultline@0.1.2

Verify the tag

git fetch --tags
git verify-tag v0.1.8-buildweek

Historical / not for judging

Tag	Status
v0.1.7-buildweek	Historical (missing .devcontainer)
v0.1.6 and earlier buildweek tags	Historical
v0.1.4	RETRACTED — do not cite

Do not move this tag. Continuous release on main is paused until after submission.

FaultLine v0.1.7-buildweek

Build Week submission pin. Pin refs live inside this tagged commit (SUB-02). SSH-signed tag (SEC-08).

Prefer this over v0.1.6-buildweek (that tag was cut one commit before its own pin bump).

Verify

git fetch --tags
git verify-tag v0.1.7-buildweek
git checkout v0.1.7-buildweek
pnpm install --frozen-lockfile
pnpm test
pnpm fl judge-proof --export-only

Tag commit: 9b3e3435c50bf650943e5b4e6d91df9d9d9f1f00
Engineering parent: 333f21d2779aa869958a840fb52c3be5d43f1726
v0.1.4 remains RETRACTED.

FaultLine v0.1.6-buildweek

Build Week submission pin with self-describing pin refs inside the tag commit.

Highlights

• COH-07/08/09: humanized witness review, TTY approve/freeze, standing approvals
• SUB-03: owned soak-integrity disclosure in submission kit
• RIG-09: clean 10k turn-tree snapshot path (CAPTURED)
• SEC-09 corpus expansion; RIG-07 Windows Docker gate; RIG-08 heterogeneous sample

Integrity

• v0.1.4-buildweek remains RETRACTED
• Revert: 457fabeb9d5ff2261cbbf1ced4673ff28c9074d0
• Honesty tests: tests/evidence-honesty.test.ts

Checkout

git checkout v0.1.6-buildweek
pnpm install --frozen-lockfile
pnpm fl judge-proof

FaultLine v0.1.5 Build Week

Summary

Evidence-integrity restore: remove fabricated multi-OS SIDE_CAR soak samples and revert TURN_PROOF promotion. Grade stays EXPERIMENTAL_TURN until real multi-OS organic/external soak exists (#152).

Validated commit

• SHA: 457fabeb9d5ff2261cbbf1ced4673ff28c9074d0
• CI: https://github.com/Mizore66/faultline/actions/runs/29734618279

Checkout

git checkout v0.1.5-buildweek

What changed vs v0.1.4

• Deleted scripted Linux/macOS SIDE_CAR ledgers and generator
• multiOsSoak.satisfied = false; TURN_PROOF reserved again
• Honesty regression tests for soak origins and SIDE_CAR sample allowlist
• Organic Windows Codex dogfood retained

RETRACTED — FaultLine v0.1.4 (do not use)

RETRACTED

This release is retracted. It contained a fabricated multi-OS SIDE_CAR soak sample that violated FaultLine's evidence-integrity rules.

Do not checkout or cite this tag for submission.

Correct pin

• Revert commit: 457fabeb9d5ff2261cbbf1ced4673ff28c9074d0
• Current submission pin: see latest v0.1.*-buildweek release (v0.1.5+ / forthcoming v0.1.6)
• Honesty tests: tests/evidence-honesty.test.ts

What was wrong

Scripted Linux/macOS ledgers were stamped SIDE_CAR for sessions that never occurred and used to self-grant TURN_PROOF promotion. That promotion and those samples were removed in the revert.

FaultLine v0.1.1

Automated release from main.

Install

npm i -g @mizore66/faultline@0.1.1
fl --help

Verify

git checkout v0.1.1
pnpm install --frozen-lockfile
pnpm test

Build Week submission pins (v*-buildweek) are separate from these npm semver tags.