@aeptus/aexeo-emdash 0.1.2 → 0.3.0

package/CHANGELOG.md

@@ -6,6 +6,124 @@ and the project follows [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-05-01
+
+Adds an LLM-assisted authoring flow for the truth manifest
+(`facts.json`) — a structured assertion of who the organization is,
+what the products are, and the terminology to use/avoid. AI
+assistants and search crawlers read it for citation grounding;
+authoring it well is a content task, not engineering, but the
+manifest's failure mode (a published manifest with hallucinated
+content) is high-impact.
+
+The plugin frames the question, validates the answer, and persists
+the result. The editor's LLM generates. The split is enforced by
+the prompt template, which mandates an interview phase before
+producing JSON: the LLM must ask up to 4 prioritized questions
+(terminology > identity > product/org split > descriptors) so the
+failure mode shifts from confident hallucination to honest gaps.
+
+**Compatibility:** verified against emdash `0.7.0` and `0.8.0`.
+
+### Added
+
+- **`/facts` admin page.** New entry in the plugin's adminPages.
+  Three-section UI: status of stored manifest, generate-prompt
+  (copy to clipboard for pasting into the editor's LLM), and
+  paste-and-validate (textarea with Validate + Save buttons; Save
+  is gated on a clean validation).
+- **Manifest-aware truth scoring.** `scoreIntelligence` now accepts
+  an optional manifest argument; the plugin reads it from KV
+  (`facts:current`) before scoring and badges the dashboard widget's
+  truth stat with the actual signal source — `Truth (manifest+schema)`,
+  `Truth (schema only)`, etc. Closes the prior UX-honesty gap where
+  the truth score was computed in schema-only mode without telling
+  the editor.
+- **`FACTS001` / `FACTS003` findings** on /findings. Surface
+  "no manifest authored yet" and "manifest disagrees with on-page
+  schema.org" so editors discover the authoring flow through their
+  existing surface. Cached under `meta:facts-findings` and
+  refreshed on Refresh + on Save, so the data path reads at zero
+  WASM cost.
+- **Bridge surface:** `generateFactsPrompt(documents)` and
+  `validateFactsManifest(manifest, documents)` WASM exports.
+  `scoreIntelligence` gained an optional `manifest_json` parameter.
+
+### Changed
+
+- `wasm/aexeo_emdash_bridge_bg.d.ts` is now tracked in git
+  (gitignored everything else in `wasm/`). wasm-bindgen 0.2.118
+  doesn't emit a `_bg.d.ts` for the bundler target, so this file
+  is hand-maintained. The build script snapshots its contents
+  before each wasm-bindgen run and restores it (saving the new
+  emit under `.wasm-bindgen` for inspection) if a future toolchain
+  version begins emitting one — loud warning rather than silent
+  regression.
+
+### Notes for hosts upgrading from 0.2.x
+
+- A new sidebar entry "Truth manifest" appears under the plugin's
+  admin pages. No action required to enable.
+- The dashboard widget's truth-score label now reads
+  `Truth (schema only)` until a manifest is authored. Same number,
+  more honest framing — no behavioral change.
+- A new sitewide finding (`FACTS001`) appears on /findings until a
+  manifest is saved. Severity: warning. Authoring via the new
+  /facts page dismisses it.
+
+## [0.2.0] - 2026-04-28
+
+Adds the long-asked clickable routes on the findings page. Block
+Kit can't render external links in any element type, so /findings
+now ships as a React component registered via the plugin's
+`adminEntry`. /document and the dashboard widget continue to use
+Block Kit (no link needs there).
+
+**Compatibility:** verified against emdash `0.7.0` and `0.8.0`.
+
+### Added
+
+- **Clickable routes on /findings.** Each row's route links to the
+  emdash edit URL for that document
+  (`/_emdash/admin/content/<collection>/<id>`). Published documents
+  also get a "live ↗" link to the public URL
+  (`<emdash:site_url><route>`). Drafts surface their status
+  (`draft`, `scheduled`, etc.) inline so editorial state is visible
+  at a glance.
+- **`adminEntry` field** on the configured-mode plugin descriptor.
+  Points at `@aeptus/aexeo-emdash/admin`, which exports `pages`
+  registering the `<Findings/>` React component for `/findings`.
+  emdash's `usePluginPage` hook picks this up and renders the
+  React component in place of the Block Kit fallback.
+- **Two new HTTP routes** the React component consumes:
+  - `POST /_emdash/api/plugins/aexeo-seogeo/data` — read current
+    findings + per-route metadata + computed URLs (no
+    re-evaluation).
+  - `POST /_emdash/api/plugins/aexeo-seogeo/refresh` — sweep the
+    configured collections, write findings to KV, return the same
+    payload as `/data` plus a refresh summary.
+  Both routes return JSON in the shape exported as `FindingsPayload`
+  from `dist/data-route.d.ts`. The shape is the wire contract
+  between plugin and admin component and is intentionally
+  additive — fields will be appended in future versions, never
+  renamed or removed.
+- `react` declared as an optional peer dependency
+  (`^18.0.0 || ^19.0.0`). Optional because plugins that don't use
+  the React findings page (e.g. ones that override `adminEntry`)
+  don't need it; emdash hosts that DO render adminEntry components
+  always have React installed already.
+
+### Changed
+
+- `documentKey(route)` KV entries now store
+  `{ document, meta: { id, collection, status, slug, title } }`
+  instead of the bare `EmdashDocument`. The new metadata is what
+  the React component reads to construct edit / public URLs without
+  an extra DB round-trip per row. Pre-0.2.0 entries are
+  backwards-compatible — `readAllStoredDocuments` synthesizes a
+  minimal meta blob for legacy entries so a single corrupted-shape
+  row doesn't break the page.
+
 ## [0.1.2] - 2026-04-28
 
 Functional patch. Three bugs flagged by the aeptus web team after
@@ -100,7 +218,9 @@ First public release.
   `astro.config.mjs` for the WASM import to resolve to a
   precompiled `WebAssembly.Module`. Not optional.
 
-[Unreleased]: https://github.com/schiste/Aexeo/compare/aexeo-emdash-v0.1.2...HEAD
+[Unreleased]: https://github.com/schiste/Aexeo/compare/aexeo-emdash-v0.3.0...HEAD
+[0.3.0]: https://github.com/schiste/Aexeo/compare/aexeo-emdash-v0.2.0...aexeo-emdash-v0.3.0
+[0.2.0]: https://github.com/schiste/Aexeo/compare/aexeo-emdash-v0.1.2...aexeo-emdash-v0.2.0
 [0.1.2]: https://github.com/schiste/Aexeo/compare/aexeo-emdash-v0.1.1...aexeo-emdash-v0.1.2
 [0.1.1]: https://github.com/schiste/Aexeo/compare/aexeo-emdash-v0.1.0...aexeo-emdash-v0.1.1
 [0.1.0]: https://github.com/schiste/Aexeo/releases/tag/aexeo-emdash-v0.1.0

package/dist/adapter.d.ts

@@ -12,5 +12,17 @@ export interface EmdashContentItem {
         canonical?: string | null;
     };
 }
+export interface EmdashContentMeta {
+    id: string;
+    collection: string;
+    slug: string | null;
+    status: string;
+    title: string;
+}
+export interface AdaptedContent {
+    document: EmdashDocument;
+    meta: EmdashContentMeta;
+}
 export declare function contentItemToEmdashDocument(content: EmdashContentItem): EmdashDocument;
+export declare function adaptContentItem(content: EmdashContentItem): AdaptedContent;
 //# sourceMappingURL=adapter.d.ts.map

package/dist/adapter.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"adapter.d.ts","sourceRoot":"","sources":["../src/adapter.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,cAAc,EAAqB,MAAM,YAAY,CAAC;AAmBpE,MAAM,WAAW,iBAAiB;IAChC,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,GAAG,IAAI,CAAC;IACpB,MAAM,EAAE,MAAM,CAAC;IACf,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC9B,GAAG,CAAC,EAAE;QACJ,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;QACtB,WAAW,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;QAC5B,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;KAC3B,CAAC;CACH;AAED,wBAAgB,2BAA2B,CACzC,OAAO,EAAE,iBAAiB,GACzB,cAAc,CAyBhB"}
+{"version":3,"file":"adapter.d.ts","sourceRoot":"","sources":["../src/adapter.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,cAAc,EAAqB,MAAM,YAAY,CAAC;AAmBpE,MAAM,WAAW,iBAAiB;IAChC,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,GAAG,IAAI,CAAC;IACpB,MAAM,EAAE,MAAM,CAAC;IACf,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC9B,GAAG,CAAC,EAAE;QACJ,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;QACtB,WAAW,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;QAC5B,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;KAC3B,CAAC;CACH;AAOD,MAAM,WAAW,iBAAiB;IAChC,EAAE,EAAE,MAAM,CAAC;IACX,UAAU,EAAE,MAAM,CAAC;IACnB,IAAI,EAAE,MAAM,GAAG,IAAI,CAAC;IACpB,MAAM,EAAE,MAAM,CAAC;IAIf,KAAK,EAAE,MAAM,CAAC;CACf;AAED,MAAM,WAAW,cAAc;IAC7B,QAAQ,EAAE,cAAc,CAAC;IACzB,IAAI,EAAE,iBAAiB,CAAC;CACzB;AAED,wBAAgB,2BAA2B,CACzC,OAAO,EAAE,iBAAiB,GACzB,cAAc,CAEhB;AAED,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,iBAAiB,GAAG,cAAc,CAkC3E"}

package/dist/admin/Facts.d.ts

@@ -0,0 +1,3 @@
+import * as React from "react";
+export declare function Facts(): React.JSX.Element;
+//# sourceMappingURL=Facts.d.ts.map

package/dist/admin/Facts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"Facts.d.ts","sourceRoot":"","sources":["../../src/admin/Facts.tsx"],"names":[],"mappings":"AAgBA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAsC/B,wBAAgB,KAAK,IAAI,KAAK,CAAC,GAAG,CAAC,OAAO,CAyLzC"}

package/dist/admin/Findings.d.ts

@@ -0,0 +1,3 @@
+import * as React from "react";
+export declare function Findings(): React.JSX.Element;
+//# sourceMappingURL=Findings.d.ts.map

package/dist/admin/Findings.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"Findings.d.ts","sourceRoot":"","sources":["../../src/admin/Findings.tsx"],"names":[],"mappings":"AA2BA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAa/B,wBAAgB,QAAQ,IAAI,KAAK,CAAC,GAAG,CAAC,OAAO,CA2L5C"}

package/dist/admin.d.ts

@@ -0,0 +1,7 @@
+import { Facts } from "./admin/Facts.js";
+import { Findings } from "./admin/Findings.js";
+export declare const pages: {
+    "/findings": typeof Findings;
+    "/facts": typeof Facts;
+};
+//# sourceMappingURL=admin.d.ts.map

package/dist/admin.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"admin.d.ts","sourceRoot":"","sources":["../src/admin.tsx"],"names":[],"mappings":"AAgBA,OAAO,EAAE,KAAK,EAAE,MAAM,kBAAkB,CAAC;AACzC,OAAO,EAAE,QAAQ,EAAE,MAAM,qBAAqB,CAAC;AAE/C,eAAO,MAAM,KAAK;;;CAMjB,CAAC"}