@tomismeta/paperclip-aperture 0.4.5 → 0.4.6
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 +5 -2
- package/dist/manifest.js +1 -1
- package/dist/worker.js +9 -9
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -48,7 +48,7 @@ After install, open Paperclip and use the `Focus` entry in the sidebar.
|
|
|
48
48
|
|
|
49
49
|
## Troubleshooting
|
|
50
50
|
|
|
51
|
-
- If the sidebar shows a bordered placeholder instead of the `Focus` entry, upgrade to Paperclip `2026.525.0` or newer and reinstall this plugin. `0.4.5
|
|
51
|
+
- If the sidebar shows a bordered placeholder instead of the `Focus` entry, upgrade to Paperclip `2026.525.0` or newer and reinstall this plugin. `0.4.5+` preserves the original Focus sidebar icon and uses the current host invocation scope.
|
|
52
52
|
- `paperclipApiBase` is only needed for approval overlays. Use the Paperclip origin such as `https://HOST` or `http://127.0.0.1:3100`; leaving it empty disables approval overlay reads without disabling Focus.
|
|
53
53
|
- On Windows, `spawn npm ENOENT` during `npx paperclipai plugin install @tomismeta/paperclip-aperture` comes from the Paperclip host installer failing to spawn npm. This package does not spawn npm during install. Make sure the Paperclip process can resolve `npm.cmd`, or upgrade Paperclip once the Windows installer fix is available.
|
|
54
54
|
|
|
@@ -130,9 +130,10 @@ For `0.4.x`, the boundary works like this:
|
|
|
130
130
|
- 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
|
|
131
131
|
- typed Paperclip issue blocker relations are preserved as Focus context/provenance/metadata so Aperture has better dependency facts without the plugin inventing dependency routing
|
|
132
132
|
- `activity.logged` document events invalidate stale reconciled state so document-backed review blockers refresh promptly without a full browser-side merge layer
|
|
133
|
+
- Paperclip `agent.error_cleared` events invalidate reconciled agent state, and redacted deleted comments are ignored when Focus chooses the latest operator signal
|
|
133
134
|
- 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
|
|
134
135
|
|
|
135
|
-
The plugin requires Paperclip `2026.525.0` or newer and has been validated against [`@tomismeta/aperture-core@0.7.0`](https://www.npmjs.com/package/@tomismeta/aperture-core) and [`@paperclipai/plugin-sdk@2026.
|
|
136
|
+
The plugin requires Paperclip `2026.525.0` or newer and has been validated against [`@tomismeta/aperture-core@0.7.0`](https://www.npmjs.com/package/@tomismeta/aperture-core) and [`@paperclipai/plugin-sdk@2026.609.0`](https://www.npmjs.com/package/@paperclipai/plugin-sdk).
|
|
136
137
|
|
|
137
138
|
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.
|
|
138
139
|
|
|
@@ -177,6 +178,8 @@ Then open `http://127.0.0.1:3100/APE/aperture` and verify:
|
|
|
177
178
|
- approval actions update Focus correctly when `paperclipApiBase` is configured
|
|
178
179
|
- resolved blocker comments downgrade stale `Now` items
|
|
179
180
|
- attached issue documents downgrade stale `share the memo/spec` review blockers into monitor-only follow-up
|
|
181
|
+
- deleted issue comments do not displace the latest visible operator signal
|
|
182
|
+
- clearing an agent error removes stale agent-error focus cards
|
|
180
183
|
- the active card exposes `Why now`
|
|
181
184
|
- expanded queued rows expose `Why next`
|
|
182
185
|
|
package/dist/manifest.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
var e={id:"tomismeta.paperclip-aperture",apiVersion:1,version:"0.4.
|
|
1
|
+
var e={id:"tomismeta.paperclip-aperture",apiVersion:1,version:"0.4.6",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};
|