@intentsolutions/audit-harness 0.1.0 → 1.1.6

package/LICENSE

@@ -1,21 +1,202 @@
-MIT License
-
-Copyright (c) 2026 Jeremy Longshore / Intent Solutions
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,15 @@
+@intentsolutions/audit-harness
+Copyright 2026 Jeremy Longshore / Intent Solutions
+
+This product includes software developed by
+Jeremy Longshore (https://intentsolutions.io).
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

package/README.md

@@ -1,5 +1,11 @@
 # @intentsolutions/audit-harness
 
+[![npm](https://img.shields.io/npm/v/@intentsolutions/audit-harness?color=cb3837&logo=npm)](https://www.npmjs.com/package/@intentsolutions/audit-harness)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE)
+[![Provenance](https://img.shields.io/badge/sigstore-provenance-066da5)](https://www.npmjs.com/package/@intentsolutions/audit-harness)
+
+Part of the **[Intent Eval Platform](https://github.com/intent-solutions-io/intent-eval-platform)** — the umbrella mapping the six repos that converge via a shared Evidence Bundle schema.
+
 Deterministic test-enforcement toolkit. Companion to the `audit-tests` and `implement-tests` Claude Code skills — but usable standalone in any repo that wants hash-pinned, escape-scanned, AI-proof quality gates.
 
 ## What it is
@@ -19,12 +25,36 @@ A small CLI wrapping 6 deterministic scripts:
 
 ## Install
 
+Pick the install flavor that matches your repo's ecosystem — all three publish the same CLI surface.
+
+**Node / JS / TS** (from npm):
+
 ```bash
 pnpm add -D @intentsolutions/audit-harness
 # or: npm install --save-dev @intentsolutions/audit-harness
 # or: yarn add --dev @intentsolutions/audit-harness
 ```
 
+**Python** (from PyPI):
+
+```bash
+pip install intent-audit-harness
+# or inside a project venv:
+python -m pip install intent-audit-harness
+```
+
+**Rust** (from crates.io):
+
+```bash
+cargo install intent-audit-harness
+```
+
+**Any other language** (Go, Ruby, PHP, Java, .NET, shell, etc.) — vendor the scripts:
+
+```bash
+curl -sSL https://raw.githubusercontent.com/jeremylongshore/intent-audit-harness/main/install.sh | bash
+```
+
 ## Quick usage
 
 ### Pre-commit hook (`.husky/pre-commit`)
@@ -75,7 +105,7 @@ See `audit-tests/references/philosophy.md` in the companion skill for the full r
 
 This harness sits inside a larger framework:
 
-```
+```text
 L7  Acceptance / RTM / Personas / Journeys     ← WHAT are we proving?
 L6  E2E / BDD / Visual regression              ← User-level guarantees
 L5  Perf / Security (SAST/DAST) / A11y / Chaos ← Non-functional
@@ -115,12 +145,14 @@ Most scripts are language-agnostic (shell + regex). CRAP has per-language backen
 
 ## License
 
-MIT — see [LICENSE](./LICENSE).
+Apache 2.0 — see [LICENSE](./LICENSE) and [NOTICE](./NOTICE).
+
+**Note:** versions `0.x` shipped under the MIT license. Starting with `v1.0.0`, the project is licensed under Apache 2.0. Existing `0.x` releases on npm remain available under their original MIT terms; new releases (`>= 1.0.0`) are Apache 2.0.
 
 ## Related
 
-- [`audit-tests` Claude Code skill](https://github.com/jeremylongshore/audit-harness#related) — diagnostic pipeline that uses this harness
-- [`implement-tests` Claude Code skill](https://github.com/jeremylongshore/audit-harness#related) — filesystem-mutating installer that installs this harness as part of L1/L3 setup
+- [`audit-tests` Claude Code skill](https://github.com/jeremylongshore/intent-audit-harness#related) — diagnostic pipeline that uses this harness
+- [`implement-tests` Claude Code skill](https://github.com/jeremylongshore/intent-audit-harness#related) — filesystem-mutating installer that installs this harness as part of L1/L3 setup
 
 ## Versioning
 

package/bin/audit-harness.js

@@ -13,16 +13,31 @@ const { existsSync } = require('node:fs');
 const SCRIPTS = resolve(__dirname, '..', 'scripts');
 
 const COMMANDS = {
-  'verify':       { script: 'harness-hash.sh',  args: ['--verify'] },
-  'init':         { script: 'harness-hash.sh',  args: ['--init'] },
-  'list':         { script: 'harness-hash.sh',  args: ['--list'] },
-  'escape-scan':  { script: 'escape-scan.sh',   args: [] },
-  'arch':         { script: 'arch-check.sh',    args: [] },
-  'bias':         { script: 'bias-count.sh',    args: [] },
-  'gherkin-lint': { script: 'gherkin-lint.sh',  args: [] },
-  'crap':         { script: 'crap-score.py',    args: [] },
+  'verify':        { script: 'harness-hash.sh',  args: ['--verify'] },
+  'init':          { script: 'harness-hash.sh',  args: ['--init'] },
+  'list':          { script: 'harness-hash.sh',  args: ['--list'] },
+  'escape-scan':   { script: 'escape-scan.sh',   args: [] },
+  'arch':          { script: 'arch-check.sh',    args: [] },
+  'bias':          { script: 'bias-count.sh',    args: [] },
+  'gherkin-lint':  { script: 'gherkin-lint.sh',  args: [] },
+  'crap':          { script: 'crap-score.py',    args: [] },
+  'emit-evidence': { script: 'emit-evidence.sh', args: [] },
+  'classify':      { script: 'classify.py',      args: [] },
+  'conform':       { script: 'conform.py',       args: [] },
+  'audit':         { script: 'audit.py',         args: [] },
+  'scan':          { script: 'scan.py',          args: [] },
+  'fp-rate':       { script: 'fp-rate.py',       args: [] },
+  'currency':      { script: 'currency.py',      args: [] },
+  'gen-layer-applicability': { script: 'gen-layer-applicability.py', args: [] },
 };
 
+// Gate commands that may be no-op'd by the AUDIT_HARNESS_DISABLE kill-switch.
+// classify is intentionally NOT here: it emits a meaningful kill-switched profile
+// itself (every gate enforcement=disabled). verify/init/list always run.
+const KILLABLE_GATES = new Set([
+  'escape-scan', 'arch', 'bias', 'gherkin-lint', 'crap', 'emit-evidence',
+]);
+
 function usage() {
   console.log(`audit-harness — deterministic test-enforcement toolkit
 
@@ -39,6 +54,63 @@ Commands:
   bias                     Count test-bias patterns (tautology, smoke-only, etc.)
   gherkin-lint             Advisory Gherkin quality check
   crap [args...]           CRAP complexity × coverage scorer (multi-language)
+  classify [repo]          Read-only repository classifier. Emits an audit-profile/v1
+                           value (JSON, stdout) describing the UNION of detected
+                           classifications + the resolved gate set. Never writes.
+  conform [repo]           Read-only conformance gate-runner. Validates each repo
+                           artifact (SKILL.md, .mcp.json, plugin/agent ...) against a
+                           content-addressed schema BUNDLED in this harness version
+                           and emits gate-result/v1 rows (JSON array, stdout). Never
+                           writes, never live-fetches. Advisory by default; --strict
+                           turns any conformance violation into FAIL (exit 1).
+                           OpenAPI -> spectral, Action -> yamllint (missing tool =
+                           INDETERMINATE advisory).
+  audit [repo]             Read-only testing-depth gate-runner. For each
+                           testing-depth gate in the profile, reports coverage
+                           PRESENCE per pyramid layer (unit/integration/e2e/perf/
+                           fuzz/...) + runs crap-score. Emits gate-result/v1 rows.
+                           --fast (default) presence only; --deep adds crap-score;
+                           --strict turns a gap into FAIL. Does NOT execute the
+                           repo's test suite — execution stays in the repo's CI.
+  scan [repo]              Read-only security/hygiene/skill-quality gate-runner.
+                           hygiene-readme is a local presence check; every tool-
+                           backed gate (gitleaks/osv-scanner/semgrep/syft/
+                           markdownlint/lychee) shells out (clean->PASS, findings->
+                           ADVISORY, tool absent->INDETERMINATE); skill-behavioral
+                           CONSUMES a j-rig verdict (--jrig-verdict PATH), never
+                           reimplementing judgment. Emits gate-result/v1 rows.
+                           Advisory by default; --strict turns findings into FAIL.
+  fp-rate                  Measure each gate's false-positive / false-negative rate
+                           over a labeled corpus (valid/ should be clean, malformed/
+                           should flag). The metric that gates advisory->blocking
+                           promotion. --max-fp-rate X exits 1 if any gate exceeds X.
+                           See docs/gate-promotion.md.
+  currency                 Advisory upstream-currency report. Reads the per-upstream
+                           pin relation (schemas/currency/pins.v1.json) and flags
+                           pins whose checked_at is past their staleness window.
+                           NO exit-code authority (always exit 0), no live-fetch,
+                           no auto-fix — it reports; /sync-testing-harness acts.
+  gen-layer-applicability  Project schemas/audit-profile/registry.v1.json into
+                           schemas/audit-profile/layer-applicability.md. --write to
+                           regenerate, --check to fail on drift (CI gate). The doc
+                           is a PROJECTION of the canonical registry datum.
+  emit-evidence            Wrap a gate-result JSON envelope in an in-toto
+                           Statement v1 (predicate https://evals.intentsolutions.io/gate-result/v1)
+                           Read JSON on stdin: <gate> --json | audit-harness emit-evidence
+
+Evidence Bundle (v0.3.0+):
+  All gates support --json to emit machine-readable gate-result envelopes
+  suitable for piping to emit-evidence. See SEMVER.md for compatibility rules
+  and intent-eval-lab/specs/evidence-bundle/v0.1.0-draft/SPEC.md for the
+  envelope schema.
+
+Safety levers:
+  AUDIT_HARNESS_DISABLE=1  Kill-switch. Gate commands no-op (exit 0, banner);
+                           classify still emits a profile with every gate disabled.
+  AUDIT_HARNESS_TIMEOUT=N  Per-command supervision: kill the gate after N seconds
+                           (exit 124) so a hung gate never blocks the pipeline.
+  .audit-harness.yml       Engineer-owned per-repo override (classify_pins, advisory,
+                           disable_gates, disable) honored by classify.
 
 Options:
   --version, -v            Print version
@@ -77,12 +149,39 @@ if (!existsSync(scriptPath)) {
   process.exit(2);
 }
 
+// Kill-switch: gate commands no-op; classify/verify/init/list still run.
+if (process.env.AUDIT_HARNESS_DISABLE === '1' && KILLABLE_GATES.has(cmd)) {
+  console.error(`audit-harness: KILL-SWITCH active (AUDIT_HARNESS_DISABLE=1) — '${cmd}' skipped`);
+  process.exit(0);
+}
+
 const isPython = entry.script.endsWith('.py');
 const interpreter = isPython ? 'python3' : 'bash';
 const finalArgs = [scriptPath, ...entry.args, ...rest];
 
+// Per-command supervision: a hung gate hits its timeout and is killed (exit 124)
+// rather than blocking the pipeline. 0/unset = no timeout.
+const timeoutSec = Number(process.env.AUDIT_HARNESS_TIMEOUT) || 0;
+
 const child = spawn(interpreter, finalArgs, { stdio: 'inherit' });
+
+let timedOut = false;
+let timer = null;
+if (timeoutSec > 0) {
+  timer = setTimeout(() => {
+    timedOut = true;
+    child.kill('SIGTERM');
+    setTimeout(() => child.kill('SIGKILL'), 2000).unref();
+  }, timeoutSec * 1000);
+  timer.unref();
+}
+
 child.on('exit', (code, signal) => {
+  if (timer) clearTimeout(timer);
+  if (timedOut) {
+    console.error(`audit-harness: ${entry.script} exceeded AUDIT_HARNESS_TIMEOUT=${timeoutSec}s — killed (INDETERMINATE)`);
+    process.exit(124);
+  }
   if (signal) {
     console.error(`audit-harness: ${entry.script} killed by ${signal}`);
     process.exit(128);
@@ -90,6 +189,7 @@ child.on('exit', (code, signal) => {
   process.exit(code ?? 0);
 });
 child.on('error', (err) => {
+  if (timer) clearTimeout(timer);
   console.error(`audit-harness: failed to spawn ${interpreter}: ${err.message}`);
   process.exit(2);
 });

package/docs/gate-promotion.md

@@ -0,0 +1,45 @@
+# Gate promotion — advisory → blocking
+
+Every gate in the [dimension→gate registry](../schemas/audit-profile/registry.v1.json) ships `enforcement: advisory`. Advisory means: the gate runs, emits its `gate-result/v1` row, logs any finding — and **exits 0**. It never reddens a build. Blocking (`enforcement: blocking`, exit 1 on violation) is **earned**, not default.
+
+This is deliberate. A gate that blocks before its false-positive rate is known erodes trust, and trust-erosion ends one way: someone appends `|| true` and the gate is dead. Advisory-first + earned-promotion keeps every blocking gate credible.
+
+## The rule
+
+A gate may be promoted to `blocking` for a repo when **all** hold:
+
+1. **Measured FP-rate below the bar.** Run the [FP-rate harness](../scripts/fp-rate.py) over a labeled corpus and confirm the gate's false-positive rate is **≤ 5%** (the default bar). A false positive is a *clean* input the gate wrongly flags — the failure mode that destroys trust.
+
+   ```bash
+   audit-harness fp-rate                      # human-readable report
+   audit-harness fp-rate --json               # machine-readable
+   audit-harness fp-rate --max-fp-rate 0.05   # exit 1 if any gate exceeds the bar
+   ```
+
+   The labeled corpus is `tests/fixtures/conform/{valid,malformed}/` (extend it: a gate is only as trustworthy as the corpus it was measured on — `valid/` inputs must stay clean, `malformed/` inputs must get flagged).
+
+2. **Engineer-pinned in the repo's policy.** Promotion is an engineer decision recorded in the target repo's hash-pinned `tests/TESTING.md` — never inferred by a tool, never proposed by an AI. The classifier reads the per-gate `enforcement` override from the engineer-owned `.audit-harness.yml` (`advisory:` / `disable_gates:` lists) and the policy in `tests/TESTING.md`; the registry default stays `advisory`.
+
+3. **Re-pinned manifest.** After editing the policy, re-init the hash manifest so the change travels with the code and `escape-scan` won't REFUSE a later legitimate edit:
+
+   ```bash
+   audit-harness init                         # re-pin after an engineer-reviewed policy edit
+   git add .harness-hash tests/TESTING.md     # commit policy + manifest together
+   ```
+
+## Why FP-rate, not FN-rate, is the promotion gate
+
+A false **negative** (a real problem the gate misses) is a coverage gap — annoying, but advisory output still surfaces it elsewhere and the gate can tighten over time. A false **positive** on a blocking gate halts a correct build, and the human response is to route around the gate permanently. So promotion is gated on FP-rate; FN-rate is reported for visibility but does not block promotion.
+
+## Demotion / kill-switch
+
+Promotion is reversible without ceremony:
+
+- Per-gate, per-repo: list the `gate_id` under `advisory:` or `disable_gates:` in `.audit-harness.yml`.
+- Whole-repo break-glass: `AUDIT_HARNESS_DISABLE=1` (gates no-op; `classify` emits an all-disabled profile; `conform` emits `[]`).
+
+A blocking gate that starts throwing false positives in the field should be demoted to advisory immediately, then re-measured before re-promotion.
+
+## Provenance
+
+Each emitted `gate-result/v1` row records the `policy_hash` (sha256 of the policy/schema the gate evaluated against), so any promotion decision is auditable back to the exact policy version that produced the measurement.

package/package.json

@@ -1,16 +1,16 @@
 {
   "name": "@intentsolutions/audit-harness",
-  "version": "0.1.0",
+  "version": "1.1.6",
   "description": "Deterministic test-enforcement harness — escape-scan, hash-pinning, CRAP, architecture checks, bias detection, Gherkin lint. Companion to the audit-tests and implement-tests Claude Code skills.",
-  "license": "MIT",
+  "license": "Apache-2.0",
   "author": "Jeremy Longshore <jeremy@intentsolutions.io>",
-  "homepage": "https://github.com/jeremylongshore/audit-harness",
+  "homepage": "https://github.com/jeremylongshore/intent-audit-harness",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/jeremylongshore/audit-harness.git"
+    "url": "git+https://github.com/jeremylongshore/intent-audit-harness.git"
   },
   "bugs": {
-    "url": "https://github.com/jeremylongshore/audit-harness/issues"
+    "url": "https://github.com/jeremylongshore/intent-audit-harness/issues"
   },
   "keywords": [
     "testing",
@@ -31,17 +31,21 @@
   "files": [
     "bin",
     "scripts",
+    "schemas",
+    "docs",
     "README.md",
     "LICENSE",
+    "NOTICE",
     "CHANGELOG.md"
   ],
+  "scripts": {
+    "test": "bash scripts/escape-scan.sh --staged || true",
+    "prepublishOnly": "node bin/audit-harness.js --version"
+  },
   "publishConfig": {
     "access": "public"
   },
   "engines": {
     "node": ">=18"
-  },
-  "scripts": {
-    "test": "bash scripts/escape-scan.sh --staged || true"
   }
-}
+}