paqad-ai 1.76.2 → 1.77.0

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 CHANGED
@@ -1,5 +1,54 @@
1
1
  # paqad-ai
2
2
 
3
+ ## 1.77.0
4
+
5
+ ### Minor Changes
6
+
7
+ - e262aaa: Rebuild the Site map dashboard canvas as an interactive city map (issue #489).
8
+
9
+ On real, edge-sparse maps (this repo's own: 92 surfaces, 0 transitions) the previous
10
+ canvas degenerated into an illegible vertical sliver, could not zoom to legibility, and
11
+ leaked pinch-zoom to the whole page. The canvas now runs on React Flow 12 with a
12
+ deterministic containment-first district layout of our own:
13
+
14
+ - **Districts carry the structure.** Areas render as tinted district rectangles with a
15
+ surface-card grid inside; a zero-transition map is a first-class citizen. Correct
16
+ gesture substrate (cursor-anchored zoom, pinch, non-passive wheel, scroll-pans-by-default
17
+ with a per-user setting, minimap) replaces the hand-rolled pan/zoom.
18
+ - **Journeys are metro lines.** Each journey draws as a colored polyline through its own
19
+ ordered stations (no transitions needed), with walk-mode camera flights, numbered
20
+ stations, interchange rings, semantic-zoom levels of detail, and a cmd/ctrl+K search that
21
+ flies to a surface, area, or journey. All motion respects `prefers-reduced-motion`.
22
+ - **The map wears its verification state.** Trust tier changes a surface's rendering
23
+ (solid/dashed/sketch, distinguishable without color), unverified surfaces sit under
24
+ honest fog, and a payload-derived insight line plus a gaps chip surface dead surfaces,
25
+ dangling targets, and broken journey references.
26
+ - **Team-shared curation.** Districts are draggable; the arrangement persists to
27
+ `docs/site-map/layout.yaml` through the dashboard's audited write path (refused in
28
+ `--read-only`), and a stored district is pinned and never auto-reflowed.
29
+
30
+ Everything still renders statically from `GET /api/site-map/map` with no LLM at view time;
31
+ the #466 data model, detail panel, honesty strip, list toggle, and SSE live-reload are
32
+ unchanged.
33
+
34
+ ### Patch Changes
35
+
36
+ - d5059ce: Drop the `npm warn deprecated prebuild-install@7.1.3` warning shown on `npm install -g paqad-ai`.
37
+
38
+ The warning came from the local-embeddings dependency `@xenova/transformers@2.17.2` (the last release under that scope), which pulled `sharp@^0.32` and its deprecated `prebuild-install`. Migrated to the renamed, maintained `@huggingface/transformers@^3.8.0`, which uses `sharp@^0.34` (no `prebuild-install`) and satisfies the `voyageai` peer range, so no new install warning is introduced. Model repo ids are unchanged and the pipelines pin `dtype: 'q8'`, preserving the previous quantized download size and embedding/rerank output.
39
+
40
+ ## 1.76.3
41
+
42
+ ### Patch Changes
43
+
44
+ - 457fcc0: fix(#472): reconcile the completion receipt so its headline and per-stage block agree
45
+
46
+ The end-of-change receipt (#325) composed two independent subsystems without reconciling them: the verdict headline (`formatVerdictSummary`, driven by `verdict.ok`, computed from gates only) and the per-stage evidence block (the stage-evidence fold). A feature-development change whose gates all passed but whose mandatory `review`/`checks` stages had no evidence rendered a self-contradicting receipt — `Safe to merge / N/N checks held` beside `🟡 review/checks — not recorded`. It happened whenever a mandatory-stage gap did not flip `verdict.ok` (for example `stages_mode=warn`, where the stage-evidence gate is `skipped`).
47
+
48
+ The receipt now reconciles **down** (the contract's own over-trust guard): when a feature-development change's gates all pass but a mandatory stage is not provably done, the developer-facing verdict word becomes **Inconclusive** and names the offending stages, so the headline agrees with the per-stage block. The true `🟢 N/N checks held for you.` line is kept, so gate evidence is still credited.
49
+
50
+ `verdict.ok` stays gate-derived, so git/CI exit codes and warn-mode non-blocking semantics are unchanged — Inconclusive is "do not over-trust", never a hard block. (Defect 2, the #409 narration advisory, was already fixed by #476; this closes Defect 1.)
51
+
3
52
  ## 1.76.2
4
53
 
5
54
  ### Patch Changes