Unpublish Submission (Admin)

Force-unpublish a previously-approved partner submission (HG operators only). Stamps the submission's flag audit columns AND removes the materialized blueprint from every public catalog read path. Existing tenant instances that already cloned the blueprint are unaffected. Idempotent — re-running preserves the original unpublished_at/unpublished_by_user_id and updates the reason. Requires an HG super-admin user; partner-org admins are rejected with forbidden_super_admin.

Parameters

Name	Type	Default	Description
submissionId Required	string	-	UUID of the previously-approved partner submission to force-unpublish.
reason Required	string	-	Short operator note explaining why this approval is being demoted (1–2000 chars). Stored on both the submission row (as the flag reason) and the blueprint row (as the unpublish reason) for audit.

Use Cases

• Remove a previously-approved submission's blueprint from every public catalog read path
• Take down a bad or unsafe published workflow (HG operators only) — idempotent

Example Usage

Force-unpublish with a reason

{
  "tool": "admin_unpublish_submission",
  "arguments": {
    "submissionId": "3f7c2b1a-9d4e-4c2a-8b1f-0a1b2c3d4e5f",
    "reason": "Reported to produce misleading output; demoting from catalog."
  }
}

Response Format

Field	Type	Description
submissionId	string	UUID of the unpublished submission.
blueprintId	string	UUID of the demoted agent_blueprints row.
unpublishedAt	string	When the demotion was first recorded (preserved on idempotent re-runs).
reason	string	The operator note stored on both the submission and blueprint rows.