Skip to content

feat(plugins): admit Issue Workbench conversation and inbox grants - #1639

Closed
YukinaXSer wants to merge 3 commits into
zts212653:mainfrom
YukinaXSer:feat/issue-workbench-host-grants
Closed

YukinaXSer wants to merge 3 commits into
zts212653:mainfrom
YukinaXSer:feat/issue-workbench-host-grants

Conversation

@YukinaXSer

@YukinaXSer YukinaXSer commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Withdrawn and reverted — 2026-10-20. The owner requested plugin-only development in clowder-ai-plugins#80 and withdrawal of this Host expansion. Commit 459935be8a87578a34a74c375ed672ffef24e098 reverses both proposed commits. The complete resulting tree is identical to base c086765ddb7181722f03f9f53c7a7ee17a29f147; GitHub shows zero changed files. This PR is closed and was never merged. The same three-path change has also been reverted in the local source branch. No production configuration or user data was changed.

The following is the historical proposal, retained for provenance; it is no longer an active integration plan.


Issue Workbench's team module needs an explicit Host policy to read owner conversations, retain analysis and deliver inbox notifications. This change grants only the seven capabilities declared by dev.clowder.issue-workbench; overbroad manifests and other plugin identities gain no extra authority.

This is the narrow Host companion to clowder-ai-plugins#80. Both remain unmerged while the full installed/live-cat/two-account journey is incomplete.

  • Add the plugin identity to the existing policy table; preserve installation identity during grant reconciliation.
  • Add isolated artifact acceptance using actual archive admission, file inventory, package locator, module runtime and InstalledPluginOperations.
  • Verify the owner Settings status/summary envelope and Host rejection of publication without explicit confirmation, alongside native invocation identity checks.

Validation: the two policy regressions were observed RED then GREEN; API build and targeted tests passed. The packed candidate passed actual Host admission/reload/loading, owner status/summary, unconfirmed publication rejection, no-caller and unauthorized-repository refusal, real GitHub READ of #1628, disabled-call refusal and re-enable/read. The candidate/prepared digests are recorded separately. This script-only increment preserves the previously tested Host policy and carrier code.

All inventory/config is isolated; authority is an explicit test fixture. No production config, real GitHub assignee/comment/label or running production service changed. This does not prove user installation or live-cat invocation. Installed workbench surface, migration and real two-account acceptance remain open in #80.

Current companion HEAD: 2b76d01eb0893b8df54e6b46b26ce5ededeb80fb.
Author provenance: cat-xooblf7l / gpt-6-astra. Independent review remains required before merge.

Why: The Issue plugin module needs current owner conversation access, private records, and scheduled inbox delivery. Grant only the capabilities requested by this plugin identity, preserve existing installations during reconciliation, and provide an isolated real-Host artifact acceptance command.

Thread-Context: threadId=thread_mucwsgsjtlbabfcq catId=cat-xooblf7l
…cceptance

Why: isolated module tests alone cannot prove the actual Host Settings envelope and publication confirmation checks accept the workbench integration.
@YukinaXSer

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

To use Codex here, create a Codex account and connect to github.

Why: The owner explicitly requested withdrawal of this Host expansion and limited development to plugin PR 80. Remove the Issue-specific grants, regression tests and acceptance script while preserving commit history.

Reverts 9819504 and 2b76d01. The resulting full tree is identical to pre-expansion base c086765.

Thread-Context: threadId=thread_mucwsgsjtlbabfcq catId=cat-xooblf7l sourceMessageId=0001792509520767-000070-c6435188

[砚砚/gpt-6-astra🐾]
@YukinaXSer YukinaXSer closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant