paqad-ai 1.26.1 → 1.26.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/dist/cli/index.js +894 -816
- package/dist/cli/index.js.map +1 -1
- package/dist/index.d.ts +14 -1
- package/dist/index.js +841 -762
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/runtime/hooks/verification-record.mjs +48 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# paqad-ai
|
|
2
2
|
|
|
3
|
+
## 1.26.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#196](https://github.com/Eliyce/paqad-ai/pull/196) [`e92a757`](https://github.com/Eliyce/paqad-ai/commit/e92a75707dd06973b84b33be1eb404ba3f91de54) Thanks [@HLasani](https://github.com/HLasani)! - fix: produce the evidence ledger on every provider, not Claude Code alone
|
|
8
|
+
|
|
9
|
+
The verification-completion run that writes `.paqad/ledger/` only fired from Claude Code's native `Stop` hook, so onboarded projects driven by Codex, Gemini, or any other host produced no evidence ledger even with `enterprise.evidence_ledger` enabled. The completion hook was rendered into Claude's config alone; every other adapter wrote inert hook metadata its host never executes.
|
|
10
|
+
|
|
11
|
+
Each hook-capable host now gets its native completion hook wired during onboarding, from one shared definition (`src/adapters/shared/native-completion-hook.ts`): Codex `Stop` in `.codex/hooks.json`, Gemini `AfterAgent` in `.gemini/settings.json`. They point at a new record-only runtime hook (`runtime/hooks/verification-record.mjs`) that writes the ledger but always exits 0 and stays silent, so a host that reads a Stop-hook's exit code or stdout never gets blocked or retried. No change to any host's entry file (`AGENTS.md` / `GEMINI.md`) — the fix lives entirely in the hook layer. Hosts without a native completion hook remain covered by the git/CI backstop. A new `docs/instructions/rules/coding/cross-provider-parity.md` rule and a cross-adapter parity test guard against a capability being wired for a single host again. Cursor and Windsurf native hooks are tracked as follow-up.
|
|
12
|
+
|
|
3
13
|
## 1.26.1
|
|
4
14
|
|
|
5
15
|
### Patch Changes
|