@tomismeta/paperclip-aperture 0.4.2 → 0.4.4

package/README.md

@@ -84,6 +84,8 @@ and agents                             attention now?    actually sees     to th
 - a sidebar entry, page, and dashboard widget
 - worker-side host read caching for issue/comment/document/agent reconciliation, with fresh summary/export reads when you need the latest host truth
 - bounded per-company Core sessions with health reporting so the worker does not grow without limit during normal multi-company use
+- replayable operator signal entries and overlay-response ledger entries so Focus actions remain auditable even when a frame came from the display adapter rather than Core
+- decision-owner metadata on reconciled/display frames so exports can distinguish Core judgment, Paperclip reconciliation, approval overlays, and final display promotion
 - a corpus-backed `issue-intelligence` regression check in CI so heuristic edits stay inspectable
 - rollback-safe local mutations that restore the last durable attention state if persistence fails
 - versioned persisted attention envelopes with an explicit migration path for older schemas
@@ -92,7 +94,7 @@ and agents                             attention now?    actually sees     to th
 
 Focus is meant to be more legible than a smart inbox.
 
-The current `0.3.x` explainability slice keeps reasoning attached to the cards you are already acting on:
+The current `0.4.x` explainability slice keeps reasoning attached to the cards you are already acting on:
 
 - `Why now` on the active card explains why the current item outranks the rest of the queue
 - `Why next` on queued rows explains why something is staged behind the current top item
@@ -118,14 +120,15 @@ For `0.4.x`, the boundary works like this:
 - the final Focus view is therefore Core-backed but not Core-only today: the plugin still owns some Paperclip-specific candidate and lane policy where the host has facts Core cannot infer by itself
 - Paperclip remains the system of record for issue and approval writes
 - approval transport now goes through a worker-side Paperclip adapter using the plugin SDK HTTP client, so the browser UI no longer talks to host approval APIs directly
-- the plugin intentionally publishes `ApertureEvent`s today, using a Paperclip-specific semantic mapping layer and ontology, rather than switching fully to `SourceEvent`
+- the plugin preserves Paperclip source facts as `SourceEvent`s where the Core contract supports them, while still exporting the normalized `ApertureEvent` used for replay/debug
 - that semantic layer includes reusable intent detectors, actor resolution against real company agents, downstream blocker extraction, explicit rule ids for matched issue heuristics, and shared operator-language generation inside the plugin
+- typed Paperclip issue blocker relations are preserved as Focus context/provenance/metadata so Aperture has better dependency facts without the plugin inventing dependency routing
 - `activity.logged` document events invalidate stale reconciled state so document-backed review blockers refresh promptly without a full browser-side merge layer
 - Focus exports the live Core snapshot, the reconciled/plugin-composed display snapshot, and bounded Core traces so replay/debug flows can inspect both the engine substrate and the final operator view
 
-The plugin has been validated against [`@tomismeta/aperture-core@0.6.0`](https://www.npmjs.com/package/@tomismeta/aperture-core) and [`@paperclipai/plugin-sdk@2026.403.0`](https://www.npmjs.com/package/@paperclipai/plugin-sdk).
+The plugin has been validated against [`@tomismeta/aperture-core@0.7.0`](https://www.npmjs.com/package/@tomismeta/aperture-core) and [`@paperclipai/plugin-sdk@2026.428.0`](https://www.npmjs.com/package/@paperclipai/plugin-sdk).
 
-If your Paperclip host is not running at the default local address, set the plugin config field `paperclipApiBase` so the worker-side approval adapter can reach the correct host API.
+Approval overlay transport is opt-in until the Paperclip plugin SDK exposes a first-class approval client. Set the plugin config field `paperclipApiBase` when the worker can reach the host approval API; leave it empty to run Focus without approval overlays in hosted or restricted-network environments.
 
 ## Development
 
@@ -158,12 +161,14 @@ npx paperclipai plugin uninstall tomismeta.paperclip-aperture --force
 npx paperclipai plugin install --local .
 ```
 
+If you want to smoke test approval overlays locally, set the plugin config field `paperclipApiBase` to `http://127.0.0.1:3100` before creating approval fixtures. Without that config, Focus intentionally skips approval API reads and stays quiet.
+
 Then open `http://127.0.0.1:3100/APE/aperture` and verify:
 
 - `Acknowledge` hides the active card and survives refresh
 - `Next` promotes into `Now`
 - issue comments post successfully from Focus
-- approval actions update Focus correctly
+- approval actions update Focus correctly when `paperclipApiBase` is configured
 - resolved blocker comments downgrade stale `Now` items
 - attached issue documents downgrade stale `share the memo/spec` review blockers into monitor-only follow-up
 - the active card exposes `Why now`
@@ -174,6 +179,7 @@ Then open `http://127.0.0.1:3100/APE/aperture` and verify:
 - Plugin on npm: [`@tomismeta/paperclip-aperture`](https://www.npmjs.com/package/@tomismeta/paperclip-aperture)
 - Roadmap and releasing: [docs/ROADMAP.md](./docs/ROADMAP.md)
 - Architecture remediation note: [docs/AUDIT-REMEDIATION-2026-04.md](./docs/AUDIT-REMEDIATION-2026-04.md)
+- May 2026 audit remediation note: [docs/AUDIT-REMEDIATION-2026-05.md](./docs/AUDIT-REMEDIATION-2026-05.md)
 - Contribution guide: [CONTRIBUTING.md](./CONTRIBUTING.md)
 - Aperture GitHub repo: [tomismeta/aperture](https://github.com/tomismeta/aperture)
 - Aperture Core on npm: [`@tomismeta/aperture-core`](https://www.npmjs.com/package/@tomismeta/aperture-core)

package/dist/manifest.js

@@ -1,80 +1 @@
-const manifest = {
-  id: "tomismeta.paperclip-aperture",
-  apiVersion: 1,
-  version: "0.4.2",
-  displayName: "Paperclip Aperture",
-  description: "The live attention layer for Paperclip, combining Aperture Core continuity with Paperclip-native operator policy.",
-  author: "@tomismeta",
-  categories: ["automation", "ui"],
-  capabilities: [
-    "events.subscribe",
-    "http.outbound",
-    "agents.read",
-    "issues.read",
-    "issue.comments.read",
-    "issue.comments.create",
-    "issue.documents.read",
-    "activity.log.write",
-    "plugin.state.read",
-    "plugin.state.write",
-    "telemetry.track",
-    "ui.dashboardWidget.register",
-    "ui.page.register",
-    "ui.sidebar.register"
-  ],
-  entrypoints: {
-    worker: "./dist/worker.js",
-    ui: "./dist/ui"
-  },
-  instanceConfigSchema: {
-    type: "object",
-    properties: {
-      captureIssueLifecycle: {
-        type: "boolean",
-        title: "Capture Issue Lifecycle",
-        default: true,
-        description: "Turn issue creation and update events into Aperture status signals."
-      },
-      captureRunFailures: {
-        type: "boolean",
-        title: "Capture Run Failures",
-        default: true,
-        description: "Turn failed agent runs into high-salience attention events."
-      },
-      paperclipApiBase: {
-        type: "string",
-        title: "Paperclip API Base",
-        default: "http://127.0.0.1:3100",
-        description: "Base URL the worker should use for Paperclip approval reads and writes when the plugin SDK lacks a first-class approval client."
-      }
-    }
-  },
-  ui: {
-    slots: [
-      {
-        type: "page",
-        id: "attention-page",
-        displayName: "Focus",
-        exportName: "AttentionPage",
-        routePath: "aperture"
-      },
-      {
-        type: "sidebar",
-        id: "attention-sidebar-link",
-        displayName: "Focus",
-        exportName: "AttentionSidebarLink"
-      },
-      {
-        type: "dashboardWidget",
-        id: "attention-widget",
-        displayName: "Focus",
-        exportName: "DashboardWidget"
-      }
-    ]
-  }
-};
-var manifest_default = manifest;
-export {
-  manifest_default as default
-};
-//# sourceMappingURL=manifest.js.map
+const e={id:"tomismeta.paperclip-aperture",apiVersion:1,version:"0.4.4",displayName:"Paperclip Aperture",description:"The live attention layer for Paperclip, combining Aperture Core continuity with Paperclip-native operator policy.",author:"@tomismeta",categories:["automation","ui"],capabilities:["events.subscribe","http.outbound","agents.read","issues.read","issue.relations.read","issue.comments.read","issue.comments.create","issue.documents.read","activity.log.write","plugin.state.read","plugin.state.write","telemetry.track","ui.dashboardWidget.register","ui.page.register","ui.sidebar.register"],entrypoints:{worker:"./dist/worker.js",ui:"./dist/ui"},instanceConfigSchema:{type:"object",properties:{captureIssueLifecycle:{type:"boolean",title:"Capture Issue Lifecycle",default:!0,description:"Turn issue creation and update events into Aperture status signals."},captureRunFailures:{type:"boolean",title:"Capture Run Failures",default:!0,description:"Turn failed agent runs into high-salience attention events."},paperclipApiBase:{type:"string",title:"Paperclip API Base",default:"",description:"Optional base URL for Paperclip approval reads and writes. Leave empty to disable approval API fetches when the plugin SDK lacks a first-class approval client."}}},ui:{slots:[{type:"page",id:"attention-page",displayName:"Focus",exportName:"AttentionPage",routePath:"aperture"},{type:"sidebar",id:"attention-sidebar-link",displayName:"Focus",exportName:"AttentionSidebarLink"},{type:"dashboardWidget",id:"attention-widget",displayName:"Focus",exportName:"DashboardWidget"}]}};var t=e;export{t as default};