paqad-ai 1.26.2 → 1.28.0

package/CHANGELOG.md

@@ -1,5 +1,43 @@
 # paqad-ai
 
+## 1.28.0
+
+### Minor Changes
+
+- [#221](https://github.com/Eliyce/paqad-ai/pull/221) [`d0e93dd`](https://github.com/Eliyce/paqad-ai/commit/d0e93dd0d66dc27321ea7819b4736ff969ce072d) Thanks [@HLasani](https://github.com/HLasani)! - Add a global enable/disable toggle with graceful degradation ([#220](https://github.com/Eliyce/paqad-ai/issues/220))
+
+  Teams can now turn paqad fully off for a fair A/B baseline, and an
+  absent or disabled install can no longer hard-fail an IDE.
+
+  - **One off-signal, read everywhere.** A committed `paqad.enabled: false`
+    in `.paqad/project-profile.yaml`, or a per-run `PAQAD_DISABLED=1`
+    override (which wins), turns paqad off. Absent means on, so existing
+    projects are unchanged. The signal is read three dist-less ways that
+    agree: a TS predicate, a shell primitive, and an `.mjs` primitive.
+  - **Off is a pure no-op.** Both entry gates, the decision-pause gate, the
+    completion hooks, the verification backstop, and silent-update all
+    early-exit when off. No block, no `[paqad]` stdout injection, and zero
+    `.paqad/` writes, so a disabled turn leaves a clean tree.
+  - **No IDE dead-ends.** Every host entry file now carries a graceful
+    fallback clause: if the framework pointer cannot be resolved or paqad is
+    disabled, the agent proceeds as a normal assistant instead of blocking.
+  - **`paqad-ai enable` / `paqad-ai disable`** flip the durable flag with no
+    re-onboarding, and `paqad-ai doctor` reports the disabled (vanilla mode)
+    state as healthy.
+
+## 1.27.0
+
+### Minor Changes
+
+- [#207](https://github.com/Eliyce/paqad-ai/pull/207) [`c004f78`](https://github.com/Eliyce/paqad-ai/commit/c004f7805fd5af05ed9a03a6ccdb3072afb84143) Thanks [@HLasani](https://github.com/HLasani)! - Make an onboarded `.paqad/` directory lighter and the auto-update hook cross-platform.
+
+  - **Cross-platform silent-update.** The session-start auto-update hook is now a Node `silent-update.mjs` that runs from the framework install, instead of a `silent-update.sh` copied into every project. The shell version needed bash, python3, and GNU coreutils; the Node version needs only Node, so auto-update works on minimal images and Windows. On re-onboard the old `.sh` entry is pruned from the provider config and the committed copy is removed.
+  - **Stop churning the tracked manifest.** `onboarding-manifest.json` no longer carries `framework_version` (the one field that changed on every version bump). The file stays tracked for its auto-update policy and onboarded-sentinel role.
+  - **Drop zero-reader artifacts.** `.paqad/version`, `.paqad/classifier-config.json`, and `.paqad/next-steps.md` are no longer written (the next-steps guidance is printed to the terminal at the end of onboarding). Repos onboarded before this change have these untracked and removed on re-onboard.
+  - **Quieter module health.** Profiles are created on demand as modules accrue evidence instead of seeding an empty profile per module at onboard, and consumed evidence files are deleted after they fold into a profile, so they no longer grow unbounded.
+  - **Close .gitignore gaps.** Per-machine runtime state created on first use of a later workflow (`patterns/`, `crs/`, `attachments/`, `traceability/`, module-map drift/events, and more) is now ignored so it never churns a team repo.
+  - **Fewer false health warnings.** The decision-workspace check no longer requires the git-ignored audit log, and a missing module-health directory is treated as healthy.
+
 ## 1.26.2
 
 ### Patch Changes