Agent Plugins portable: external follow-ups carried over from #307 (Cursor feedback, dogfood re-run, spec watch)

[ScriptedAlchemy]

Tracks the external / time-gated follow-ups carried over from #307 (Agent Plugins 1.0.0 portable adoption). The engineering deliverable in #307 is complete and merged (#373 65c05a617, #406 98751df4a); these items cannot be closed from inside this repository and are parked here so #307 can close honestly.

Context pin: Agent Plugins 1.0.0, spec repo agentplugins/agent-plugins-spec @ ff8ab5e392cc87bd88d87c060815a87490e51003 (2026-08-19); vendored schemas + provenance in packages/agent-bundle/src/adapters/schemas/portable/ (re-verified 2026-09-02, a 1.1.0 working draft exists upstream since 2026-08-15 with no published schemas).

• Report the three placeholder-expansion gaps to Cursor (product feedback) with the audit evidence in docs/audits/2026-09-02-agent-plugins-cursor-ide-proof.md: ${PLUGIN_ROOT} not expanded in cwd, ${PLUGIN_ROOT} not expanded in args, omitted cwd defaults to $HOME instead of the plugin root (spec §7.2.1 / §9.2 MUSTs). Observed on Cursor 3.18.25 stable 280eca2911f1.
• Re-run the IDE dogfood when a Cursor release notes Agent Plugins placeholder expansion; upgrade the portable-1.0.0.json capability evidence (stdio MCP launch rows) from "discovered, not launchable" to launched once spec-conformant servers start.
• Watch the specification repository for post-1.0.0 revisions; when 1.1.0 schemas are published, re-pin under schemas/portable/ with a dated PROVENANCE.json update, bump the portable adapterRevision, and refresh the pins in tests/adapter-metadata.test.ts (same cadence as the Effect RC re-pin chore).

[ScriptedAlchemy]

Final-sweep verification (2026-09-03): all three items are external or time-gated (Cursor product feedback, a future Cursor release, a future spec revision) and none can be closed from inside this repository; the engineering deliverable they trail (#307 via #373 and #406) is merged and the portable pins were re-verified 2026-09-02. Added the host-integration label so the tracker sits beside #422–#424. One note for whoever files the Cursor feedback: the audit evidence (docs/audits/2026-09-02-agent-plugins-cursor-ide-proof.md) and the three MUST citations (spec §7.2.1 / §9.2) are complete as written — nothing further is needed from this repo before sending it.

[ScriptedAlchemy]

Closing out from PR #443 (merged as 9bb5d0dc1). Evidence per item:

Item	Status	Evidence
Report the three ${PLUGIN_ROOT} gaps to Cursor	Recorded as internal observations; not submitted (maintainer decision 2026-09-03)	The write-up (renamed from …-feedback.md in #444) was removed in #467 (merged as 9d4fbd867) per maintainer decision; the surviving record is docs/audits/2026-09-03-agent-plugins-cursor-ide-proof.md. The removed note carried one section per gap with the §7.2.1 / §9.1 / §9.2 citations, observed payloads and paths, expected behaviour, a four-file minimal repro plugin, and two 1440×900 captures. Re-verified on the installed Cursor 3.18.25 (realCommit 280eca29…af3 — the same build as the 2026-09-02 observation; no newer stable release is installed or listed in the rendered changelog). All three gaps reproduce; the widened probe added three more (env values unexpanded §9.2, reserved PLUGIN_ROOT/PLUGIN_DATA absent §9.1, ./ commands resolved against the workspace §7.2.1). Nothing is fixed, so no capability row moved to supported; portable-1.0.0.json mcp.evidence carries the dated line.
Re-run the IDE dogfood	Done on the current build	docs/audits/2026-09-03-agent-plugins-cursor-ide-proof.md: isolated instance (dedicated HOME/--user-data-dir, Xvfb, 1440×900, no loading-state captures). Emitted install.mjs local mode installs (Installed → Already installed); --mode marketplace fails closed for Agent Plugins packs by design; `agent-bundle install cursor --mode local
Watch the specification repository	Checked 2026-09-03; pin stands; tracked	Live 1.0.0 schemas rehash to the pins (1805 / 3408 bytes); agentplugins/agent-plugins-spec main unchanged at ff8ab5e39, no tags or releases; spec/1.1.0.md is still "Working Draft" (in-repo schemas/1.1.0/* differ only in version strings; agent-plugins.org/schemas/1.1.0/* → 404). PROVENANCE.json re-verification dated 2026-09-03, and a dated spec-watch row now sits in the parked follow-ups ledger in docs/effect-conventions.md with the observed latest published version (1.0.0) and the re-pin trigger/action.

No external action: by maintainer decision (2026-09-03) the observations are not submitted to Cursor; they stay in-repo as the baseline for re-checking a newer Cursor build.

The two time-gated re-runs (a Cursor release noting Agent Plugins placeholder expansion; a published 1.1.0) are now recorded where they will be re-checked — the spec-watch ledger row and the dogfood note's §4 procedure — so this tracker closes; open a fresh issue when either trigger fires.

[ScriptedAlchemy]

2026-09-03 follow-up: by maintainer decision the ${PLUGIN_ROOT} report is not submitted to Cursor. PR #444 renamed it to an internal observations note and #467 (merged as 9d4fbd867) removed it entirely, per maintainer decision; the record is docs/audits/2026-09-03-agent-plugins-cursor-ide-proof.md and the portable-1.0.0.json mcp.evidence line, and the portable rows stay degraded until a Cursor build that expands the placeholders is observed.