devrites 3.2.5 → 3.2.6

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to DevRites are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and DevRites adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Releases are generated automatically by [semantic-release](https://semantic-release.gitbook.io/) from Conventional Commits on `main`.
 
+## [3.2.6](https://github.com/ViktorsBaikers/DevRites/compare/v3.2.5...v3.2.6) (2026-07-25)
+
+### Changed
+
+* **devrites:** remove package-existence gate ([4cbcbe9](https://github.com/ViktorsBaikers/DevRites/commit/4cbcbe9002eaf97f8f921e13e97b4dcfc6b61b34))
+
 ## [3.2.5](https://github.com/ViktorsBaikers/DevRites/compare/v3.2.4...v3.2.5) (2026-07-25)
 
 ### Fixed

package/README.md

@@ -25,7 +25,7 @@ final commit, push, and tag, and it requires a typed `GO` confirmation.
 Unattended runs may create local WIP checkpoint commits along the way, but only
 Ship collapses and pushes them.
 
-**Status:** [`v3.2.5`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v3.2.5): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v3.2.6`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v3.2.6): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 ## Quick start
 

package/docs/cli.md

@@ -21,7 +21,6 @@ devrites-engine recovery route <class>             # typed owner/action; JSON re
 devrites-engine recovery check|record|clear ...    # durable three-failure budget; record/clear accept --class
 devrites-engine reconcile snapshot|check|close [slug] # retained writer baseline
 devrites-engine test-integrity [slug]    # reject weakened tests against that baseline
-devrites-engine package-existence [slug] # verify new imports are declared
 devrites-engine evidence-fresh [slug]    # proof freshness gate      (exit 0 fresh · 3 stale)
 devrites-engine check-acceptance <dir>   # acceptance gate           (exit 0 proven · 1 gap)
 devrites-engine ledger sync <dir>        # fold a feature's spec deltas into the living capability ledger

package/docs/command-map.md

@@ -41,7 +41,7 @@ these lanes so its owner is clear:
 
 | Lane | Commands | Owner |
 |---|---|---|
-| Workflow gates | `preamble`, `build-readiness`, `readiness-digest`, `spec-skeleton`, `spec-validate`, `check-acceptance`, `evidence-fresh`, `coverage`, `doubt-coverage`, `budget`, `test-integrity`, `mutation-gate`, `package-existence`, `review-integrity`, `footprint`, `reconcile`, `conventions`, `learnings`, `review-fingerprints`, `timeline`, `health`, `progress` | Called by the relevant `rite-*` workflow or shared reply contract. |
+| Workflow gates | `preamble`, `build-readiness`, `readiness-digest`, `spec-skeleton`, `spec-validate`, `check-acceptance`, `evidence-fresh`, `coverage`, `doubt-coverage`, `budget`, `test-integrity`, `mutation-gate`, `review-integrity`, `footprint`, `reconcile`, `conventions`, `learnings`, `review-fingerprints`, `timeline`, `health`, `progress` | Called by the relevant `rite-*` workflow or shared reply contract. |
 | Workspace utilities | `status`, `snapshot`, `analyze`, `archive-search`, `clarify-return`, `recovery`, `resolve`, `close-out`, `stuck`, `tick-afk`, `ledger`, `profile` | Called by a specific utility/phase when its condition is met. |
 | Low-level completeness API | `readiness`, `seal` | Available for scripts/CI and documented engine use. Feature rites use stricter phase-specific gates (`build-readiness`, `/rite-seal` phase contract) instead of auto-running these weaker aggregate checks. |
 | Install / operator / CI | `install`, `update`, `uninstall`, `doctor`, `migrate`, `validate-pack`, `harness-matrix`, `extensions`, `overrides`, `reviewers`, `hook`, `version` | Called by `npx devrites ...`, `/rite-doctor`, hooks, CI, or a human operator; do not auto-run during feature work just because the command exists. |

package/docs/orchestration.md

@@ -65,8 +65,7 @@ Each dispatch follows the retained-baseline sequence:
 2. The sole wright returns code/tests; the root validates its typed identity and
    exact changed-file set.
 3. `reconcile check` rejects anything outside the root allowlist.
-4. `test-integrity` and `package-existence` run against the same retained
-   baseline.
+4. `test-integrity` runs against the retained baseline.
 5. After proof and decision checks pass, `reconcile close` retires the private
    window; only then does the root write canonical records.
 

package/engine/commands.go

@@ -34,7 +34,7 @@ func rootModeFor(command string, args []string) rootMode {
 	case "first-task", "spec-dedupe", "evidence-fresh", "coverage",
 		"doubt-coverage", "budget", "preamble", "progress",
 		"build-readiness", "readiness-digest", "analyze", "mutation-gate",
-		"test-integrity", "review-integrity", "package-existence",
+		"test-integrity", "review-integrity",
 		"archive-search", "config", "reviewers", "outside-voice", "docs-stale",
 		"secret-scan", "lanes", "overrides":
 		return rootLenient

package/engine/internal/lib/reconcile.go

@@ -34,7 +34,7 @@ const (
 // clean check, another snapshot re-arms only the dispatch state for a retry while
 // retaining the original source baseline.
 // `check` compares the captured state with the current state and retains the
-// immutable baseline for the later test-integrity and package-existence gates.
+// immutable baseline for the later test-integrity gate.
 // `close` explicitly ends the window and removes its private artifacts.
 //
 //	0  clean check, snapshot/close completed, or skipped (not a git repo)

package/engine/internal/lib/reconcile_test.go

@@ -408,15 +408,13 @@ func TestReconcileCheckFailsClosedWhenObjectDatabaseIsCorrupt(t *testing.T) {
 	}
 }
 
-func TestPostSliceGatesShareBaselineUntilClose(t *testing.T) {
+func TestPostSliceTestIntegrityUsesBaselineUntilClose(t *testing.T) {
 	gitRoot := newGitRepo(t)
 	root := workspace(t, "feat")
-	writeFile(t, filepath.Join(gitRoot, "package.json"), "{}\n")
-	commitAll(t, gitRoot, "manifest")
+	writeFile(t, filepath.Join(gitRoot, "README.md"), "fixture\n")
+	commitAll(t, gitRoot, "baseline")
 
-	// These user deltas predate the slice. In particular, the undeclared import
-	// must not be blamed on the wright by package-existence.
-	writeFile(t, filepath.Join(gitRoot, "src/user-delta.ts"), `import ghost from "preexisting-user-package";`+"\n")
+	// This user delta predates the slice and must not be blamed on the wright.
 	writeFile(t, filepath.Join(gitRoot, "tests/user_delta_test.go"), "package tests\n\nfunc TestUserDelta(t *testing.T) { t.Fatal(\"baseline\") }\n")
 	writeWrightAllowlist(t, root, "feat", "seed.go")
 
@@ -432,12 +430,6 @@ func TestPostSliceGatesShareBaselineUntilClose(t *testing.T) {
 	if code := TestIntegrity(root, []string{"feat"}, &stdout, &stderr); code != 0 {
 		t.Fatalf("test-integrity = %d, want 0\nstdout: %s\nstderr: %s", code, stdout.String(), stderr.String())
 	}
-	stdout.Reset()
-	stderr.Reset()
-	if code := PackageExistence(root, []string{"feat"}, &stdout, &stderr); code != 0 {
-		t.Fatalf("package-existence = %d, want 0\nstdout: %s\nstderr: %s", code, stdout.String(), stderr.String())
-	}
-
 	if code, out := runReconcile(t, root, "close", "feat"); code != 0 {
 		t.Fatalf("close = %d, want 0\n%s", code, out)
 	}

package/engine/internal/lib/util.go

@@ -7,8 +7,8 @@ import (
 )
 
 // gitToplevel returns the absolute path of the git working tree containing dir,
-// or "" when dir is not inside a repository. The git-backed gates (test-integrity,
-// package-existence, reconcile) skip rather than block when it is empty.
+// or "" when dir is not inside a repository. The git-backed gates
+// (test-integrity and reconcile) skip rather than block when it is empty.
 func gitToplevel(dir string) string {
 	out, err := exec.Command("git", "-C", dir, "rev-parse", "--show-toplevel").Output()
 	if err != nil {

package/engine/main.go

@@ -56,7 +56,6 @@ Usage:
   devrites-engine mutation-gate [slug]     Advisory: detect the mutation runner and scope it
   devrites-engine test-integrity [slug]    Gate: no test deleted, skipped, or de-asserted
   devrites-engine review-integrity [slug]  Gate: no adversarial review axis is silent (zero findings, no justification)
-  devrites-engine package-existence [slug] Gate: every new import is declared in a manifest
   devrites-engine reconcile <sub> [slug]   A1 gate: snapshot|check|close the wright's source writes
   devrites-engine resolve <qid> "<ans>"    Resolve an open question; keep state.md consistent
   devrites-engine close-out <slug>         Archive a shipped feature and clear ACTIVE
@@ -239,8 +238,6 @@ func run(args []string, stdin io.Reader, stdout, stderr io.Writer) int {
 		return lib.TestIntegrity(root, args[1:], stdout, stderr)
 	case "review-integrity":
 		return lib.ReviewIntegrity(root, args[1:], stdout, stderr)
-	case "package-existence":
-		return lib.PackageExistence(root, args[1:], stdout, stderr)
 	case "reconcile":
 		return lib.Reconcile(root, args[1:], stdout, stderr)
 	case "resolve":

package/engine/root_routing_test.go

@@ -45,7 +45,6 @@ func TestRootModeForCoversReadAndWriteSurfaces(t *testing.T) {
 		{name: "mutation gate", command: "mutation-gate", want: rootLenient},
 		{name: "test integrity", command: "test-integrity", want: rootLenient},
 		{name: "review integrity", command: "review-integrity", want: rootLenient},
-		{name: "package existence", command: "package-existence", want: rootLenient},
 		{name: "reconcile snapshot", command: "reconcile", args: []string{"snapshot"}, want: rootStrict},
 		{name: "reconcile check", command: "reconcile", args: []string{"check"}, want: rootStrict},
 		{name: "reconcile close", command: "reconcile", args: []string{"close"}, want: rootStrict},

package/pack/.claude/skills/rite-build/reference/forge.md

@@ -166,8 +166,8 @@ decision.
 
 Hand the winner's structured artifact to the normal cycle. Run immediate
 reconciliation, doubt every stood decision, and complete test-integrity,
-package-existence, targeted, browser, and other slice proof. Only after every
-required gate is green:
+targeted, browser, and other slice proof. Only after every required gate is
+green:
 
 ```bash
 devrites-engine forge record "$RUN_ID" verification verified \

package/pack/.claude/skills/rite-build/reference/phase-contract.md

@@ -73,14 +73,13 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    (reported in its `Principles` field, or that you detect against `.devrites/principles.md`) is
    handled here like an irreversible-risk item: block, route to a human-approved scoped
    exception in the register or stop; never doubt-and-accept a principle violation into the slice.
-5. **Run retained-baseline integrity gates, then recover any objective red.**
+5. **Run the retained-baseline integrity gate, then recover any objective red.**
    ```bash
    devrites-engine test-integrity; echo "test-integrity rc=$?"
-   devrites-engine package-existence; echo "package-existence rc=$?"
    ```
-   If the wright's `Gates` were red (targeted tests / types / lint), either integrity gate
-   failed, or it
-   couldn't verify: do **not** mark the slice `built`, and **do not fix the code yourself**.
+   If the wright's `Gates` were red (targeted tests / types / lint), `test-integrity`
+   failed, or proof could not be verified: do **not** mark the slice `built`, and **do not
+   fix the code yourself**.
    Classify each causal fingerprint through
    [`cleanup-and-classify.md`](../../devrites-debug-recovery/reference/cleanup-and-classify.md),
    run `devrites-engine recovery route <class>`, and follow the `recovery-route/v1`
@@ -95,9 +94,9 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    `recovery clear --class <class> "<root cause>" <slug>` only after green. Before every
    re-dispatch, update the root-owned allowlist only for an accepted in-slice path and run
    `reconcile snapshot`: after a clean check this refreshes canonical-state scope while
-   retaining the original source baseline. Repeat reconcile and both integrity gates on every
-   return. This owns red
-   gates, missing coverage, browser/runtime failures, and workflow-tool defects.
+   retaining the original source baseline. Repeat reconcile and the integrity gate on every
+   return. This owns red gates, missing coverage, browser/runtime failures, and
+   workflow-tool defects.
    After recovery:
    - green → continue to record;
    - product-contract/acceptance ambiguity or irreversible risk → open the genuine human gate
@@ -106,22 +105,14 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    - exhausted objective failure → preserve reproduction/dead ends, set `Status: blocked` and
      `Next step: /rite-plan unblock`, then STOP without a question or `/rite-resolve`.
 6. **Close the retained baseline, then record. You are the canonical writer.**
-   Reconciliation ran immediately on return and the two integrity gates ran in step 5.
+   Reconciliation ran immediately on return and `test-integrity` ran in step 5.
    **Exit 3 → hard STOP:** a test was deleted, skipped, or de-asserted since the slice base: the
    slice went green by weakening its tests, a Critical protocol violation. Revert the weakening and
    re-dispatch the wright; do **not** mark the slice `built`.
 
-   The package-existence gate (anti-hallucination) requires every new third-party import
-   to appear in a project manifest:
-   **Exit 3 → STOP:** an imported package is not declared in any manifest (`package.json`, `go.mod`,
-   `requirements.txt`, `pyproject.toml`, `Pipfile`, `Cargo.toml`): the classic shape of a
-   hallucinated or typo-squatted dependency. Confirm the name on the registry and declare it via the
-   package manager, or remove the import; do **not** mark the slice `built`. The gate is deterministic
-   and fail-open (not a git repo / no manifest / stdlib-only import → rc 0). If the nearest
-   manifest declares the package, treat the mismatch as a workflow-tool defect under bounded
-   recovery, not a plan repair or retry-authorization question. Once every gate and doubt
-   verdict is accepted, a forged slice records successful verification and runs
-   manifest-only cleanup per [`forge.md`](forge.md). Then close the private window:
+   Once every gate and doubt verdict is accepted, a forged slice records successful
+   verification and runs manifest-only cleanup per [`forge.md`](forge.md). Then close the
+   private window:
    ```bash
    devrites-engine reconcile close
    ```

package/pack/.claude/skills/rite-build/reference/wright-dispatch.md

@@ -66,15 +66,12 @@ and exact changed-file set. Before the root writes any canonical record, run:
 ```bash
 devrites-engine reconcile check; echo "reconcile rc=$?"
 devrites-engine test-integrity; echo "test-integrity rc=$?"
-devrites-engine package-existence; echo "package-existence rc=$?"
 ```
 
 - Reconcile `5`: reject the result. Preserve pre-snapshot user work; restore only the
   unauthorized slice delta; never widen scope from the writer's self-report.
 - Test integrity `3`: a test was deleted, muted, focused, or de-asserted. Treat it as a
   Critical protocol failure and correct it through the wright.
-- Package existence `3`: verify the exact package/version and fix the bounded workflow
-  or dependency defect through recovery. It is not a reason to ask for retry approval.
 - A setup/corrupt-baseline error blocks acceptance; never fall back silently to `HEAD`.
 
 The clean reconcile check records that source has not changed since inspection. The
@@ -105,13 +102,13 @@ Before every retry:
 
 That refresh requires the prior clean check, re-fingerprints root-owned state, and keeps
 the original source baseline. Re-dispatch with the exact output, attempt count, and dead
-ends. Then repeat reconcile and both integrity gates from zero. Clear recovery only after
+ends. Then repeat reconcile and `test-integrity` from zero. Clear recovery only after
 green with `recovery clear --class <class> "<root cause>" <slug>`. An exhausted objective
 failure becomes a technical blocker with its reproduction, not a `rite-resolve` question.
 
 ## Close and record
 
-When reconciliation, integrity, package, proof, and doubt gates all pass:
+When reconciliation, integrity, proof, and doubt gates all pass:
 
 ```bash
 devrites-engine reconcile close

package/pack/.claude/skills/rite-prove/reference/acceptance-proof.md

@@ -21,7 +21,6 @@ mutation tool when present. Run:
 ```bash
 devrites-engine test-integrity
 devrites-engine mutation-gate
-devrites-engine package-existence
 ```
 
 A test that stays green on broken code is unproven. Pure transforms also get a

package/pack/.claude/skills/rite-seal/reference/final-evidence.md

@@ -53,7 +53,6 @@ gates:
 ```bash
 devrites-engine test-integrity; echo "test-integrity rc=$?"   # exit 3 = a test deleted/skipped/loosened → Critical NO-GO
 devrites-engine mutation-gate   # changed-files mutation score — band the verdict; survivors are unproven behaviours
-devrites-engine package-existence; echo "package-existence rc=$?"   # exit 3 = a new import isn't declared in any manifest (hallucinated/typo-squatted dep) → Critical NO-GO
 ```
 A test weakened since the slice base is a **Critical NO-GO**: the suite went green by lowering the
 bar, not by the code being right. Record the mutation score in `seal.md`; under

package/pack/generated/claude/skills/rite-build/reference/forge.md

@@ -166,8 +166,8 @@ decision.
 
 Hand the winner's structured artifact to the normal cycle. Run immediate
 reconciliation, doubt every stood decision, and complete test-integrity,
-package-existence, targeted, browser, and other slice proof. Only after every
-required gate is green:
+targeted, browser, and other slice proof. Only after every required gate is
+green:
 
 ```bash
 devrites-engine forge record "$RUN_ID" verification verified \

package/pack/generated/claude/skills/rite-build/reference/phase-contract.md

@@ -73,14 +73,13 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    (reported in its `Principles` field, or that you detect against `.devrites/principles.md`) is
    handled here like an irreversible-risk item: block, route to a human-approved scoped
    exception in the register or stop; never doubt-and-accept a principle violation into the slice.
-5. **Run retained-baseline integrity gates, then recover any objective red.**
+5. **Run the retained-baseline integrity gate, then recover any objective red.**
    ```bash
    devrites-engine test-integrity; echo "test-integrity rc=$?"
-   devrites-engine package-existence; echo "package-existence rc=$?"
    ```
-   If the wright's `Gates` were red (targeted tests / types / lint), either integrity gate
-   failed, or it
-   couldn't verify: do **not** mark the slice `built`, and **do not fix the code yourself**.
+   If the wright's `Gates` were red (targeted tests / types / lint), `test-integrity`
+   failed, or proof could not be verified: do **not** mark the slice `built`, and **do not
+   fix the code yourself**.
    Classify each causal fingerprint through
    [`cleanup-and-classify.md`](../../devrites-debug-recovery/reference/cleanup-and-classify.md),
    run `devrites-engine recovery route <class>`, and follow the `recovery-route/v1`
@@ -95,9 +94,9 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    `recovery clear --class <class> "<root cause>" <slug>` only after green. Before every
    re-dispatch, update the root-owned allowlist only for an accepted in-slice path and run
    `reconcile snapshot`: after a clean check this refreshes canonical-state scope while
-   retaining the original source baseline. Repeat reconcile and both integrity gates on every
-   return. This owns red
-   gates, missing coverage, browser/runtime failures, and workflow-tool defects.
+   retaining the original source baseline. Repeat reconcile and the integrity gate on every
+   return. This owns red gates, missing coverage, browser/runtime failures, and
+   workflow-tool defects.
    After recovery:
    - green → continue to record;
    - product-contract/acceptance ambiguity or irreversible risk → open the genuine human gate
@@ -106,22 +105,14 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    - exhausted objective failure → preserve reproduction/dead ends, set `Status: blocked` and
      `Next step: /rite-plan unblock`, then STOP without a question or `/rite-resolve`.
 6. **Close the retained baseline, then record. You are the canonical writer.**
-   Reconciliation ran immediately on return and the two integrity gates ran in step 5.
+   Reconciliation ran immediately on return and `test-integrity` ran in step 5.
    **Exit 3 → hard STOP:** a test was deleted, skipped, or de-asserted since the slice base: the
    slice went green by weakening its tests, a Critical protocol violation. Revert the weakening and
    re-dispatch the wright; do **not** mark the slice `built`.
 
-   The package-existence gate (anti-hallucination) requires every new third-party import
-   to appear in a project manifest:
-   **Exit 3 → STOP:** an imported package is not declared in any manifest (`package.json`, `go.mod`,
-   `requirements.txt`, `pyproject.toml`, `Pipfile`, `Cargo.toml`): the classic shape of a
-   hallucinated or typo-squatted dependency. Confirm the name on the registry and declare it via the
-   package manager, or remove the import; do **not** mark the slice `built`. The gate is deterministic
-   and fail-open (not a git repo / no manifest / stdlib-only import → rc 0). If the nearest
-   manifest declares the package, treat the mismatch as a workflow-tool defect under bounded
-   recovery, not a plan repair or retry-authorization question. Once every gate and doubt
-   verdict is accepted, a forged slice records successful verification and runs
-   manifest-only cleanup per [`forge.md`](forge.md). Then close the private window:
+   Once every gate and doubt verdict is accepted, a forged slice records successful
+   verification and runs manifest-only cleanup per [`forge.md`](forge.md). Then close the
+   private window:
    ```bash
    devrites-engine reconcile close
    ```

package/pack/generated/claude/skills/rite-build/reference/wright-dispatch.md

@@ -66,15 +66,12 @@ and exact changed-file set. Before the root writes any canonical record, run:
 ```bash
 devrites-engine reconcile check; echo "reconcile rc=$?"
 devrites-engine test-integrity; echo "test-integrity rc=$?"
-devrites-engine package-existence; echo "package-existence rc=$?"
 ```
 
 - Reconcile `5`: reject the result. Preserve pre-snapshot user work; restore only the
   unauthorized slice delta; never widen scope from the writer's self-report.
 - Test integrity `3`: a test was deleted, muted, focused, or de-asserted. Treat it as a
   Critical protocol failure and correct it through the wright.
-- Package existence `3`: verify the exact package/version and fix the bounded workflow
-  or dependency defect through recovery. It is not a reason to ask for retry approval.
 - A setup/corrupt-baseline error blocks acceptance; never fall back silently to `HEAD`.
 
 The clean reconcile check records that source has not changed since inspection. The
@@ -105,13 +102,13 @@ Before every retry:
 
 That refresh requires the prior clean check, re-fingerprints root-owned state, and keeps
 the original source baseline. Re-dispatch with the exact output, attempt count, and dead
-ends. Then repeat reconcile and both integrity gates from zero. Clear recovery only after
+ends. Then repeat reconcile and `test-integrity` from zero. Clear recovery only after
 green with `recovery clear --class <class> "<root cause>" <slug>`. An exhausted objective
 failure becomes a technical blocker with its reproduction, not a `rite-resolve` question.
 
 ## Close and record
 
-When reconciliation, integrity, package, proof, and doubt gates all pass:
+When reconciliation, integrity, proof, and doubt gates all pass:
 
 ```bash
 devrites-engine reconcile close

package/pack/generated/claude/skills/rite-prove/reference/acceptance-proof.md

@@ -21,7 +21,6 @@ mutation tool when present. Run:
 ```bash
 devrites-engine test-integrity
 devrites-engine mutation-gate
-devrites-engine package-existence
 ```
 
 A test that stays green on broken code is unproven. Pure transforms also get a

package/pack/generated/claude/skills/rite-seal/reference/final-evidence.md

@@ -53,7 +53,6 @@ gates:
 ```bash
 devrites-engine test-integrity; echo "test-integrity rc=$?"   # exit 3 = a test deleted/skipped/loosened → Critical NO-GO
 devrites-engine mutation-gate   # changed-files mutation score — band the verdict; survivors are unproven behaviours
-devrites-engine package-existence; echo "package-existence rc=$?"   # exit 3 = a new import isn't declared in any manifest (hallucinated/typo-squatted dep) → Critical NO-GO
 ```
 A test weakened since the slice base is a **Critical NO-GO**: the suite went green by lowering the
 bar, not by the code being right. Record the mutation score in `seal.md`; under

package/pack/generated/codex/skills/rite-build/reference/forge.md

@@ -166,8 +166,8 @@ decision.
 
 Hand the winner's structured artifact to the normal cycle. Run immediate
 reconciliation, doubt every stood decision, and complete test-integrity,
-package-existence, targeted, browser, and other slice proof. Only after every
-required gate is green:
+targeted, browser, and other slice proof. Only after every required gate is
+green:
 
 ```bash
 devrites-engine forge record "$RUN_ID" verification verified \

package/pack/generated/codex/skills/rite-build/reference/phase-contract.md

@@ -73,14 +73,13 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    (reported in its `Principles` field, or that you detect against `.devrites/principles.md`) is
    handled here like an irreversible-risk item: block, route to a human-approved scoped
    exception in the register or stop; never doubt-and-accept a principle violation into the slice.
-5. **Run retained-baseline integrity gates, then recover any objective red.**
+5. **Run the retained-baseline integrity gate, then recover any objective red.**
    ```bash
    devrites-engine test-integrity; echo "test-integrity rc=$?"
-   devrites-engine package-existence; echo "package-existence rc=$?"
    ```
-   If the wright's `Gates` were red (targeted tests / types / lint), either integrity gate
-   failed, or it
-   couldn't verify: do **not** mark the slice `built`, and **do not fix the code yourself**.
+   If the wright's `Gates` were red (targeted tests / types / lint), `test-integrity`
+   failed, or proof could not be verified: do **not** mark the slice `built`, and **do not
+   fix the code yourself**.
    Classify each causal fingerprint through
    [`cleanup-and-classify.md`](../../devrites-debug-recovery/reference/cleanup-and-classify.md),
    run `devrites-engine recovery route <class>`, and follow the `recovery-route/v1`
@@ -95,9 +94,9 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    `recovery clear --class <class> "<root cause>" <slug>` only after green. Before every
    re-dispatch, update the root-owned allowlist only for an accepted in-slice path and run
    `reconcile snapshot`: after a clean check this refreshes canonical-state scope while
-   retaining the original source baseline. Repeat reconcile and both integrity gates on every
-   return. This owns red
-   gates, missing coverage, browser/runtime failures, and workflow-tool defects.
+   retaining the original source baseline. Repeat reconcile and the integrity gate on every
+   return. This owns red gates, missing coverage, browser/runtime failures, and
+   workflow-tool defects.
    After recovery:
    - green → continue to record;
    - product-contract/acceptance ambiguity or irreversible risk → open the genuine human gate
@@ -106,22 +105,14 @@ See also [`one-slice-cycle.md`](one-slice-cycle.md).
    - exhausted objective failure → preserve reproduction/dead ends, set `Status: blocked` and
      `Next step: $rite-plan unblock`, then STOP without a question or `$rite-resolve`.
 6. **Close the retained baseline, then record. You are the canonical writer.**
-   Reconciliation ran immediately on return and the two integrity gates ran in step 5.
+   Reconciliation ran immediately on return and `test-integrity` ran in step 5.
    **Exit 3 → hard STOP:** a test was deleted, skipped, or de-asserted since the slice base: the
    slice went green by weakening its tests, a Critical protocol violation. Revert the weakening and
    re-dispatch the wright; do **not** mark the slice `built`.
 
-   The package-existence gate (anti-hallucination) requires every new third-party import
-   to appear in a project manifest:
-   **Exit 3 → STOP:** an imported package is not declared in any manifest (`package.json`, `go.mod`,
-   `requirements.txt`, `pyproject.toml`, `Pipfile`, `Cargo.toml`): the classic shape of a
-   hallucinated or typo-squatted dependency. Confirm the name on the registry and declare it via the
-   package manager, or remove the import; do **not** mark the slice `built`. The gate is deterministic
-   and fail-open (not a git repo / no manifest / stdlib-only import → rc 0). If the nearest
-   manifest declares the package, treat the mismatch as a workflow-tool defect under bounded
-   recovery, not a plan repair or retry-authorization question. Once every gate and doubt
-   verdict is accepted, a forged slice records successful verification and runs
-   manifest-only cleanup per [`forge.md`](forge.md). Then close the private window:
+   Once every gate and doubt verdict is accepted, a forged slice records successful
+   verification and runs manifest-only cleanup per [`forge.md`](forge.md). Then close the
+   private window:
    ```bash
    devrites-engine reconcile close
    ```

package/pack/generated/codex/skills/rite-build/reference/wright-dispatch.md

@@ -66,15 +66,12 @@ and exact changed-file set. Before the root writes any canonical record, run:
 ```bash
 devrites-engine reconcile check; echo "reconcile rc=$?"
 devrites-engine test-integrity; echo "test-integrity rc=$?"
-devrites-engine package-existence; echo "package-existence rc=$?"
 ```
 
 - Reconcile `5`: reject the result. Preserve pre-snapshot user work; restore only the
   unauthorized slice delta; never widen scope from the writer's self-report.
 - Test integrity `3`: a test was deleted, muted, focused, or de-asserted. Treat it as a
   Critical protocol failure and correct it through the wright.
-- Package existence `3`: verify the exact package/version and fix the bounded workflow
-  or dependency defect through recovery. It is not a reason to ask for retry approval.
 - A setup/corrupt-baseline error blocks acceptance; never fall back silently to `HEAD`.
 
 The clean reconcile check records that source has not changed since inspection. The
@@ -105,13 +102,13 @@ Before every retry:
 
 That refresh requires the prior clean check, re-fingerprints root-owned state, and keeps
 the original source baseline. Re-dispatch with the exact output, attempt count, and dead
-ends. Then repeat reconcile and both integrity gates from zero. Clear recovery only after
+ends. Then repeat reconcile and `test-integrity` from zero. Clear recovery only after
 green with `recovery clear --class <class> "<root cause>" <slug>`. An exhausted objective
 failure becomes a technical blocker with its reproduction, not a `rite-resolve` question.
 
 ## Close and record
 
-When reconciliation, integrity, package, proof, and doubt gates all pass:
+When reconciliation, integrity, proof, and doubt gates all pass:
 
 ```bash
 devrites-engine reconcile close

package/pack/generated/codex/skills/rite-prove/reference/acceptance-proof.md

@@ -21,7 +21,6 @@ mutation tool when present. Run:
 ```bash
 devrites-engine test-integrity
 devrites-engine mutation-gate
-devrites-engine package-existence
 ```
 
 A test that stays green on broken code is unproven. Pure transforms also get a

package/pack/generated/codex/skills/rite-seal/reference/final-evidence.md

@@ -53,7 +53,6 @@ gates:
 ```bash
 devrites-engine test-integrity; echo "test-integrity rc=$?"   # exit 3 = a test deleted/skipped/loosened → Critical NO-GO
 devrites-engine mutation-gate   # changed-files mutation score — band the verdict; survivors are unproven behaviours
-devrites-engine package-existence; echo "package-existence rc=$?"   # exit 3 = a new import isn't declared in any manifest (hallucinated/typo-squatted dep) → Critical NO-GO
 ```
 A test weakened since the slice base is a **Critical NO-GO**: the suite went green by lowering the
 bar, not by the code being right. Record the mutation score in `seal.md`; under

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "3.2.5",
+  "version": "3.2.6",
   "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code and Codex",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",

package/scripts/build-release-tarball.sh

@@ -59,6 +59,7 @@ for item in "${PAYLOAD[@]}"; do
   if [[ -e "$item" ]]; then
     if [[ "$item" == "engine" ]] && git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
       while IFS= read -r -d '' path; do
+        [[ -e "$path" ]] || continue
         if [[ "$path" == engine/testdata/golden/* ]]; then
           continue
         fi

package/scripts/validate.sh

@@ -302,7 +302,6 @@ DELETED_HELPER_HITS="$(grep -rnI \
   -e 'footprint\.sh' \
   -e 'learnings\.sh' \
   -e 'mutation-gate\.sh' \
-  -e 'package-existence\.sh' \
   -e 'progress\.sh' \
   -e 'reconcile\.sh' \
   -e 'tick-afk\.sh' \