← GPTs to PluginCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to GPTs to Plugin
Snapshot Sep 30, 2026 · 23:17 UTC · version 0.1.2+codex.20260921090000
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Resume plugin dashboard uploads and scans safely after stalls, timeouts, or browser interruptions.",
"included_files": [],
"name": "reliable-dashboard-recovery",
"skill_md_contents": "---\nname: reliable-dashboard-recovery\ndescription: Resume plugin dashboard uploads and scans safely after stalls, timeouts, or browser interruptions.\n---\n\n# Reliable Dashboard Recovery\n\nUse this skill whenever a plugin upload, dashboard navigation, validation save, or asynchronous scan appears stuck.\n\n## Checkpoint record\n\nBefore every dashboard mutation, record:\n\n- target plugin ID and whether it is an update or a new plugin;\n- package SHA-256, version, and local ZIP path;\n- current dashboard URL and submission ID when visible;\n- stage: upload, metadata, prompts, skills, scan, compliance, or submission;\n- retry count and last observed status.\n\nNever resume an update if the target plugin ID cannot be verified. Never use a new-plugin flow as an implicit substitute for an update flow.\n\n## Recovery loop\n\n1. Inspect the current page and status without clicking anything.\n2. Wait using bounded backoff: 2, 4, 8, 15, 30, then 60 seconds.\n3. Refresh or reopen the same submission URL and inspect again.\n4. Check the plugin list for an already-created draft with the same package name, version, or package hash.\n5. Resume the next incomplete stage. Do not repeat completed stages.\n6. Retry at most three times per stage. If the same failure repeats, classify it as a browser, permission, authentication, or platform issue and request the smallest required user action.\n\n## Safe retry rules\n\n- An upload button click is not evidence of upload completion.\n- A disabled button is not evidence of failure.\n- An unchanged `Uploading` or `Scanning` label requires polling and a fresh inspection, not an immediate duplicate upload.\n- If a draft exists, edit or resume that draft rather than creating another one.\n- Keep the compliance attestations and final publish/submit click user-confirmed.\n\n## Completion evidence\n\nReport only visible evidence: plugin ID, version, submission ID, terminal scan status, issue list, and whether the final submission remains pending. If any of these are unavailable, say exactly which evidence is missing.\n"
}SHA-256 of public snapshot: 5227df09b6c1d135fa9c0babaefdec076c6336681e41e148ebdd0e4be2622eb3