v0.8.1

v0.8.1 release evidence

Status: local release candidate verified. The implementation and documentation are frozen after
the bounded local candidate gate. Exact-commit hosted CI/CodeQL/self-audit, signed immutable publication, npm
provenance, verified installation, immutable Action consumption, signed v1 promotion and durable
live verification remain pending. Published v0.8.0 facts stay in docs/release-state.json until
each v0.8.1 public object is independently observed.

Outcome

v0.8.1 makes existing correctness and release-trust boundaries enforceable without adding a
detector family.

• Persisted source roots and excluded directory basenames compile into one file-read policy shared
  by built-in source analysis, route/access review, Git diff snapshots and every selected external
  adapter. Restricted Gitleaks history remains explicit unknown rather than a broad read followed by
  output filtering.
• Root-level exact suppressions remain visible in every v3 renderer and never change evidence or
  baseline state. Unknown and evidence-integrity findings cannot be suppressed. CI/release and
  external-adapter entries require owner and expiry.
• The repository self-audit uses an explicit production-only scope and reviewed exact suppressions,
  fails on active HIGH or unavailable evidence and retains all dispositions in its artifact.
• Node package export patterns replace all right-hand-side wildcard occurrences literally;
  conditional-export divergence stays partial. Finite allowlisted usage counters remain numeric
  while credential strings, numeric credentials, arrays and non-finite values remain redacted.
• Release publication starts from trusted main: a read-only job verifies the signed annotated tag,
  signer policy, exact candidate and hosted checks before the separate release-environment job gains
  write/attestation permissions. Moving v1 has explicit pending and final states.
• Minimum main/tag/environment protection, Dependabot alerts/security updates, blocking dependency
  review and checksum-pinned ShellCheck are configured with a documented solo-maintainer
  administrator bypass.

The detector inventory remains 25 built-in risk rules, 3 evidence-integrity rules and 16 opt-in
external-adapter risk rules. This release does not claim production precision/recall,
exploitability, repository safety, independent review or WSL2 support.

Candidate verification

The single full local gate ran on implementation/evidence commit
b55e8a170f72378e742cfbe34adcb9ac00e06c2e:

npm run check
npm pack --dry-run --json
uv run --no-project --with pyyaml python \
  /Users/kenn/.codex/skills/.system/skill-creator/scripts/quick_validate.py .
git diff --check

Results:

• npm run check: passed; 88 test files passed, zero failed and one optional real-adapter test was
  skipped. Prerequisite surfaces recorded three passed, zero failed and one skipped. Bash 3.2,
  lint, schema, generated-file, public-contract, release-contract and distribution checks passed.
• Skill Creator validation: Skill is valid!; PyYAML was supplied in an isolated uv environment
  and no project dependency or lockfile changed.
• candidate SPDX 2.3 SBOM: /tmp/wass-v0.8.1-candidate.spdx.json, SHA-256
  fb1b1762efc849f77310fbbb8bc5aed795eb87210dc1def36851bd3b02aeda46. The path is intentionally
  outside the repository and is not a public release asset.
• npm pack --dry-run --json: 221 files, 672,551 packed bytes, 2,821,340 unpacked bytes, SHA-1
  2c9e06be7bd555a05fd8a8d8d908d3f54506f1d8, integrity
  sha512-SUonYq1kXt8/Noz0yR3qubR7rhI+ob70heTf5xJPJNMFNdC5eUP4c3GvQ42IsTPozNHCyO3/O8Z2J2sRlffu3w==.
• fixed-project journey refresh: Linkwarden 278 findings (exit 3/incomplete), Healthchecks 149
  (exit 0/complete), Open WebUI 162 (exit 3/incomplete), Uptime Kuma 122 (exit 3/incomplete) and
  Mealie 37 (exit 0/complete). Every pinned checkout remained clean. Incomplete evidence was not
  converted to pass.

The next commit only records this evidence. Its changed documentation contracts and whitespace are
checked locally; P11 runs the complete hosted matrix on the exact pushed commit. The optional real
adapter remains a required hosted check rather than a local pass claim.

Hosted candidate verification

The implementation/evidence candidate
66a549c1248cbf68d7f470443c3f072f5b75374c passed the exact-commit hosted gate:

• CI run 33319363473
  succeeded on macOS/Ubuntu with Node 22/24. Ubuntu/Node 22 installed the checksum-pinned adapters
  and passed real Gitleaks/OSV fixtures. ShellCheck and repository self-audit succeeded.
• CodeQL run 33319363476
  succeeded. Production alerts 9 and 10 closed through analysis as fixed. Alerts 1-7 and 11 were
  dismissed only as used in tests after their public ledger reached main; live open count was 0.
• The downloaded self-audit had zero active findings, zero unknown findings and one visible,
  expiring suppressed MEDIUM lead. report.json SHA-256 is
  b3028306b46edb2ba2e26d584f68d9b5bd925e55d75752bd9d3d83e774e74f46; this bounded report is not
  repository-safety evidence.
• Dependabot open alerts changed from the recorded 32-fixture inventory to 0 after the candidate
  manifest reached main; generated PR 8 closed without merge. Temporary no-diff PR 9 proved the
  pinned dependency-review Action in its supported event (run 33319628174, job 99279204655), then
  closed without merge; its branch and duplicate jobs were removed/cancelled.
• Strict main checks, no force-push/deletion, active v0.*/v1 tag rules and the protected-branch
  release environment were re-read. The solo-maintainer administrator bypass remains explicit and
  is not independent review.

This hosted-evidence documentation commit is itself accepted as release source only after its own
exact hosted checks pass. The release verifier rejects a tag whose source, main dispatch commit or
required check SHA differs.

Immutable publication evidence

Pending. After hosted gates pass, the SSH-signed annotated tag must verify locally with:

git -c gpg.ssh.allowedSignersFile=.github/release-signers verify-tag v0.8.1

The trusted-main Release workflow, npm OIDC publication, verified installer and immutable full-SHA
Action consumer remain separate gates. A local signature check uses repository policy and does not
independently prove GitHub account ownership.

Final promotion and public facts

Pending. The signed moving v1 alias must first enter tracked pending state under an exact prior-tag
lease, pass both immutable and moving-alias consumers, then finalize from the same promotion-run
evidence. Public URLs, object IDs, digests, npm metadata and workflow IDs will be written only after
they are retrieved and verified.