@tomismeta/paperclip-aperture 0.4.8 → 0.5.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/README.md +8 -2
- package/dist/manifest.js +1 -1
- package/dist/worker.js +27 -11
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -121,7 +121,7 @@ This plugin treats Paperclip as the host runtime and UI shell, while embedding [
|
|
|
121
121
|
|
|
122
122
|
It is an SDK-first integration with explicit plugin-side host policy. Aperture Core handles continuity, replay, and global attention mechanics; the plugin adds Paperclip-specific candidate generation, approval overlays, and operator language where the host can know more than Core alone.
|
|
123
123
|
|
|
124
|
-
For `0.
|
|
124
|
+
For `0.5.x`, the boundary works like this:
|
|
125
125
|
|
|
126
126
|
- the plugin worker owns Aperture ingestion, replay, review state, display composition, reconciliation caching, and Paperclip-native policy overlays
|
|
127
127
|
- 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
|
|
@@ -132,10 +132,16 @@ For `0.4.x`, the boundary works like this:
|
|
|
132
132
|
- typed Paperclip issue blocker relations and watchdog summaries are preserved as Focus context/provenance/metadata so Aperture has better dependency facts without the plugin inventing dependency routing
|
|
133
133
|
- `activity.logged` document events invalidate stale reconciled state so document-backed review blockers refresh promptly without a full browser-side merge layer
|
|
134
134
|
- Paperclip `agent.error_cleared` events invalidate reconciled agent state, and redacted deleted comments are ignored when Focus chooses the latest operator signal
|
|
135
|
+
- native Paperclip issue document and relation events invalidate reconciled state directly, with `activity.logged` retained as a compatibility fallback
|
|
136
|
+
- document-scoped issue comments remain contextual status updates rather than being treated as top-level follow-up requests
|
|
137
|
+
- validated Paperclip run diagnostics can become Core 0.9 `SourceEvidence`; arbitrary prose and malformed evidence are ignored
|
|
135
138
|
- subscribed event callbacks stay memory-only and flush pending Aperture state from the next scoped data/action bridge call, keeping host invocation scope boundaries intact without losing replay durability after Focus refreshes
|
|
136
139
|
- 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
|
|
140
|
+
- Aperture Core `0.9.x` semantic and judgment hardening is consumed through this existing `ApertureCore` integration; the plugin does not run the Core `./kernel` subpath as a second runtime judgment system
|
|
137
141
|
|
|
138
|
-
The plugin requires Paperclip `2026.525.0` or newer and has been validated against [`@tomismeta/aperture-core@0.
|
|
142
|
+
The plugin requires Paperclip `2026.525.0` or newer and has been validated against the published [`@tomismeta/aperture-core@0.9.0`](https://www.npmjs.com/package/@tomismeta/aperture-core/v/0.9.0) artifact and [`@paperclipai/plugin-sdk@2026.722.0`](https://www.npmjs.com/package/@paperclipai/plugin-sdk/v/2026.722.0). The plugin resolves configuration per Paperclip company so settings do not bleed across company contexts.
|
|
143
|
+
|
|
144
|
+
Paperclip `2026.722.0` has an upstream installer issue where the running server may report host version `0.0.0` during plugin minimum-version validation. If installation fails with that message, upgrade to a Paperclip server release containing the host-version fix; do not lower the plugin's declared minimum host version.
|
|
139
145
|
|
|
140
146
|
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.
|
|
141
147
|
|
package/dist/manifest.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
var e={id:"tomismeta.paperclip-aperture",apiVersion:1,version:"0.
|
|
1
|
+
var e={id:"tomismeta.paperclip-aperture",apiVersion:1,version:"0.5.0",minimumHostVersion:"2026.525.0",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"}]}},t=e;export{t as default};
|