devrites 3.2.4 → 3.2.6

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.4",
+  "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' \