Research and evidence · original check dates in each entry
Research, with its limits visible
A dated record of what is documented, what we observed and what we have not tested. This is an evidence index—not a popularity ranking.
2 November 2026 · original evidence dates retained. Local scripts still need intended-host evidence keeps prerequisites explicit and distinguishes availability from unobserved selection/loading/output; no new technical finding, tested remedy or host result.
31 October 2026 · original evidence dates retained. Local scripts: prerequisites are not runtime evidence retains explicit prerequisites and unobserved selection/loading/output limits; no new technical finding, tested remedy or host result.
30 October 2026 · original evidence dates retained. Local scripts: keep runtime prerequisites explicit links the prerequisite and unobserved-output boundaries; no new technical finding, tested remedy or host result.
29 October 2026 · original evidence dates retained. Local scripts: retain the original prerequisites and limits links the prerequisite and unobserved-output boundaries; no new technical finding, tested remedy or host result.
28 October 2026 · original evidence dates retained. Local scripts: keep the original prerequisites and limits links the prerequisite and unobserved-output boundaries; no new technical finding, tested remedy or host result.
27 October 2026 · original 5 October dependency evidence applies. Local scripts: retain explicit runtime prerequisites keeps interpreter, resource and permission needs explicit. The hypothetical design supplies no deployment/refresh guarantee; no new tested packaging remedy or host result is established.
24 October 2026 · original 21 October assessment applies. Meeting-note skill: keep the supplied-notes description retains the description, package summary and workflow. Selection, body/reference loading and output remain unobserved; no new source study or product test.
23 October 2026 · original 21 October assessment applies. Meeting-note skill: keep the supplied-notes description retains its supplied-input cues and unobserved selection/loading/output limits. A carry-forward of existing evidence, not a new source study.
22 October 2026 · original 21 October assessment applies. Meeting-note skill: retain the description and its limits links the existing supplied-notes cues and unobserved selection/loading/output limits. No new source check or product test.
21 October 2026 · narrow description assessment. Meeting-note skill: retain the existing description finds the supplied-notes input and recap categories already present for two prompt specifications. Textual coverage is not observed selection; all ten host cases remain unperformed. Only the cited description-guidance passages receive today's check.
20 October 2026 · original 19 October inspection applies. HTTP status lookup: keep the requirement distinct links the reference/procedure/static-contract choice and its unobserved-output and customer-state limits. No new source check or product test.
19 October 2026 · reference / procedure / static callable contract
HTTP status lookup: reference, procedure or callable contract?
For HTTP 429/503 meanings, original references supply information, a proposed focused skill reuses a procedure, and the inspected remote tool adds a named static contract—not fresher knowledge or customer state. Public operation is a separate commitment.
Compact worked choice. Source-design inspection only; ordinary outputs unobserved, skill unbuilt and tutorial not invoked. The conservative 12:52:57–12:54:10 UTC inspection bracket is not a source-change date; tutorial tests remain author claims.
18 October 2026 · carry-forward, not a new source check. Plugin evidence: original dates and limits retained links the 17 October note and its original studies; their scopes and untested outcomes apply.
17 October 2026 · carry-forward, not a new source check. Plugin evidence: original dates and limits retained links the 16 October note and its original studies; their scopes and untested outcomes apply.
16 October 2026 · carry-forward, not a new source check. Plugin evidence: original dates and limits retained links the 15 October summary and its original studies; their scopes and untested outcomes apply.
15 October 2026 · summary of existing dated evidence, not a new source check. Before calling a plugin ready: four separate evidence questions separates installed capability, saved OAuth configuration, replacement publication and intended-recipient output. Original source dates, scopes and untested limitations apply.
13 October 2026 · guide to existing dated evidence, not a new source check. Find the right plugin decision—and its evidence limits links OAuth setup, pending review, directory visibility, CLI capability and teammate access to their scoped decisions, with four unresolved documentation conflicts. The original source dates and untested limitations still apply.
12 October 2026 · public remote-MCP publication versus placement
Missing directory placement is not a publication diagnosis
Confirm chosen Publish, then use the exact publication name or directory URL from the submission portal. Enhanced main-page placement is discretionary and cannot be requested. Missing tiles alone prove neither failure nor harmless unfeatured status.
- Practical output
- Four compact publication/placement actions. Proposed default/order/note/stop and genuine ordinary-service alternative are synthesis/untested, not a tested fix or acquisition verdict.
- Documentary scope
- Two undated canonical primary pages independently inspected in 17:59:58–18:00:46 UTC bracket, not HTTP/publication/source-change times. Exact handles newly inspected; approval/Publish and selected placement reconfirmed. Remote-MCP public flow only; support 11 and recipient 8 October reused, not re-fetched. Changed with evidence: none.
- Unknown / not performed
- Actual account/control/Publish/name/URL/search/recipient/install/provider/selection/output/value UNKNOWN; account, search/link, support, installation and use checks were not performed. Genuine failures remain actionable.
11 October 2026 · pending package / remote-MCP replacement decision
A pending review is not a second-release queue
Prepare locally while a still-truthful/useful package is reviewed, or deliberately wait/cancel before replacement. Keep an existing remote-MCP published version during replacement review, then publish the approved replacement directly—not remove-first merely to update.
- Practical output
- Four compact review-choice actions. Conditional default/order/note and genuine website/manual alternative are our synthesis, untested—not a bypass.
- Documentary scope
- Two undated canonical primary pages independently inspected 21:02:27–21:03:02 UTC, not HTTP/publication/change dates. One-active-review/direct replacement newly inspected; same-version draft versus complete new-ZIP scope retained; package versus post-publication tool checks reconfirmed. Every resubmission starts a new review; no SLA/priority/expedition/approval promise. Changed with evidence: none.
- Unknown / not performed
- Actual account/control/status/cancellation transaction/queue/result/listing/recipient/loaded continuity UNKNOWN. Upload, cancellation, appeals, portal/authentication, scans, deployment, installation, use and retesting were not performed. Canonical remote-MCP replacement instruction is not universal continuity.
10 October 2026 · portable public remote-MCP documentary correction
Provided OAuth client: locate the ID, protect the secret, verify saved state
The documented location is now established: named-server configuration in root mcp.json, a conditional secret in Connect and display-only advanced settings. Source/upload is not proof that saved credentials changed. This supersedes the 9 October location-unknown claim, not the unverified report’s unknown cause/fix.
- Practical output
- Four compact package/secret/saved-state steps, with supporting callback/user/reviewer disclosures retaining 9 October. Stop/owner/redacted-packet advice is our synthesis, not a tested fix.
- Documentary scope
- Three undated canonical primary pages independently inspected 13:01:35–13:02:04 UTC, not HTTP/publication/change times. Exact namespace/case, conditional field and retained-registration limit newly inspected; provider/gates reconfirmed. Method-reference optionality versus declaration instruction preserved; omitted behavior unestablished. Changed with evidence: none.
- Unknown / not performed
- Actual upload format/account/control/configuration, provider validity/callback, saved connection/lock, cause/correction/result remain UNKNOWN. All provider/portal/upload/connect/scan/use/review/approval/Publish/contact untested.
9 October 2026 · public remote-MCP draft / ChatGPT authentication detail
Missing an OAuth client-ID setting? Establish the contract and next owner
Historical 9 October inspection: confirm the registration contract and exact callback before provider repair or portal clarification. Exact location was then unresolved; the 10 October documentary correction above now answers it. Actual report cause/fix remains unknown.
- Practical output
- Original dated contract/callback/owner decision; supporting details remain on Submit, while 10 October replaces the exact-location uncertainty. Our triage order/redacted packet, not an official universal fix or required form.
- Documentary scope
- Four undated primary pages independently inspected 12:58:17–12:59:54 UTC. Public connection handles and registration/callback purpose newly inspected; separate user/reviewer/public gates reconfirmed. Conditional retained-DCR advice is not the reported blocker’s diagnosis. Changed with evidence: none.
- Unknown / not performed
- No actual account/provider state, error, client ID/secret, callback, screenshot or result supplied. Portal/provider/connection/scan/use/review/approval/Publish/contact untested. One unverified problem report, not a confirmed defect or measured demand.
8 October 2026 · Enterprise creator-to-teammate documentary continuity
Before replacing an onboarding GPT link: establish teammate continuity
Preserve real work before conversion; separate private replacement, sharing/permission, recipient installation/selection and useful familiar output. Update one controlled entry only after adequate evidence.
- Practical output
- Five compact steps and a genuine hold/alternative branch; destination plus install/select guidance, real prompt, maintainer and differences. Our controlled-entry synthesis, not automatic redirect.
- Documentary scope
- Illustrative published instructions/reference team-writing GPT → intended workspace teammates in ChatGPT web / Chat. Four undated primary pages independently inspected 13:01:50–13:03:01 UTC. Private-first/access limits reconfirmed; recipient route, editor/owning permissions and handoff precision newly inspected. Changed with evidence: none.
- Not performed or established
- No real affected account/task/reference/output, migration, sharing/reach, install/select/use, update or retest. All actuals untested and unobserved. No verified all-plan calendar, old-link redirect, bookmark/QR repair or outside/public continuity guarantee; absence of verification is not a prohibition.
7 October 2026 · configured-marketplace Codex CLI documentary diagnostic
Installed/enabled, but the capability is missing: inspect the boundary
Preserve the failure, inspect source/state, then only the skill or current-session MCP branch. Presence and actual useful output remain separate.
- Practical output
- One short command block and four linear steps, supported-control or redacted escalation.
- Documentary scope
- Four undated primary pages inspected 12:56:43–12:57:06 UTC. Concrete inspection handles/field limits newly inspected; new-session prerequisite and separate quality/auth gates reconfirmed. Changed with evidence: none; no universal cure or cross-surface transfer.
- Not performed
- No CLI command, installation/toggle/restart, selection/tool invocation, actual output, diagnosis, repair or retest. Loaded provenance UNKNOWN; ten host actuals untested.
6 October 2026 · public-channel gate + active-advice correction
Can a hook-bearing local bundle enter public submission?
Not as-is under the current documented ZIP restriction. Local support and optionality do not establish public eligibility.
- Practical output
- Early gate and one channel-choice card; the 5 October core-plus-helper design applies only conditionally to local use.
- Documentary scope
- Submission, Packaging, Errors and bounded conversion sections. Explicit hook/registered-mapping exclusion newly inspected; conversion submission-path hook adaptation remains in genuine tension. No exception, source precedence, changed rule or observed rejection established.
- Not performed
- No useful public variant or adapted ZIP was built; host, portal-parsing, scan, review and approval behavior were not tested.
5 October 2026 · documented prerequisites + hypothetical dependency design
Can a public plugin rely on a local startup hook?
Reject an installation-to-compliance promise. Put required policy/input handling in the proposed core and keep a local SessionStart helper optional; narrow, clarify, redesign or stop when essential local/enforced behavior is required. 6 October correction: that hook-bearing design is conditional local scope, not an eligible public ZIP.
- Practical output
- One before/after, compact non-executable dependency sketch, truthful release copy and added questions in the existing architecture worksheet.
- Documentary scope
- Five official pages' hook/dependency sections. Selected settings and cloud-Work exclusion reconfirmed; discovery/trust/orchestration/coverage and conversion-guide caution newly inspected. Changed with evidence: none. Local/cloud/synced qualification is not a full surface refresh.
- Not performed
- Entire fictional review/resources/stop procedure hypothetical and untested. No actual policy, host, helper, installation, trust result, model output, enforced gate or binary approval. Future evidence unobserved and untested.
4 October 2026 · source-backed contracts + original hypothetical design
Separate private-data summaries from external sends
Do not bury optional send inside a read-only summary. Split and enforce the actual human consent boundary, ship read/unsaved-preview only, or obtain precise clarification.
- Practical output
- Before → redesign, three non-executable contracts, exact fictional confirmation and an inspectable provider-owned human-only approval design.
- Current documentary scope
- Four official pages plus only the error reference's paired annotation entries. Reconfirmed principles; finer contract/persistence/retry precision newly inspected. Changed with evidence: none. Annotation-field conflict narrowly checked 4 October, unresolved.
- Not performed
- Entire workflow/protocol/copy hypothetical and untested. No host/provider/send, approval, scan/review, safety result. Incidental logging scope, actual approval fidelity and provider recovery remain unresolved.
3 October 2026 · source-backed boundary + hypothetical design review
Can a plugin serve SaaS customers without selling upgrades?
One fictional read-only project-status flow replaces an external digital upsell with linkless entitlement information. Identity, resource access and feature entitlement remain separate.
- Practical output
- Before → boundary → replacement, six source-mapped copy/next-decision cases, conditional destination review and business falsification questions.
- Current documentary check
- Five official pages, bounded sections. Existing SaaS boundary reconfirmed; saved-method API/UI detail newly inspected. No changed rule or release date established. Physical-goods checkout scope remains conflicting / unresolved.
- Not performed
- All six cases are hypothetical, untested design—not observed tests or a compliance score. No live destination, account, host, API, checkout, payment, portal or support test; no demand was measured.
2 October 2026 · change evidence, not a rollout claim
I changed my plugin. What actually changed for adopters?
An original four-state model and runnable offline recorder: reproduce a same-version instruction edit, then identify independent loaded-copy, public-package and live-backend evidence.
- Practical output
- Recorder, worked JSON and blank next-evidence worksheet; synthetic revisions, not new sample releases.
- Observed engineering
- 48 subprocess commands plus one invariant: 49 recorder assertions passed. Exact download independently reproduced. Not plugin behavior, safety or update delivery.
- Current documentary check
- Five primary resources; consequential rules reconfirmed, no substantive rule change/date established. Endpoint contradiction persists; pending-review retention is not guaranteed by the inspected text.
- Not performed
- Host/session, public portal/listing and remote deployment/authorized behavior tests: all untested, observed fields UNKNOWN. Reader declarations never substitute for observations.
1 October 2026 · current documentation + exercised offline tooling
Offline release evidence is useful—but it is not a host result
An original runnable 19-file release-rehearsal kit for preserved Meeting Evidence 0.1.0: finite profile/ZIP checks, genuine failure → repair and ten separate blank host specifications.
- Observed engineering
- 32 subprocess commands plus one deterministic invariant: all 33 TOOLING assertions passed. Independent downloadable-kit reproduction succeeded. Not model performance or a safety result.
- Consequential clarification
- Portable schema, Codex logo/composerIcon validation and primary public icon are distinct scopes. The unchanged two-file sample is not established Codex-ready. No substantive policy change was established.
- Not performed
- Host acceptance, installation, activation/quality/security tests, portal validation/scans, review/approval/chosen plugin publication.
29 September 2026 · documentation + read-only observation
OpenAI plugins: package, access and publication
Current architecture/surface map, four task-selected examples, an original two-file package and its narrow static check, present policy constraints, and a qualified chronology.
- Established
- Package versus execution layers; current IDE exclusion; local/public milestone distinction; current digital-commerce restrictions and skills-only public update limit.
- Not established
- Universal-directory launch date; authenticated example behavior; exact account tiers/parity/scopes; review timing; search placement, adoption or revenue.
Evidence language
- Documented: a primary user/developer source describes the capability or rule.
- Listing observed: a read-only directory search returned an entry in this account context, not necessarily in yours.
- Offline engineering: observed checker/recorder commands, diagnostics and selected byte/structure differences—not model semantics, loaded/public bytes, deployment or safety.
- Reader declaration: intended channel, review/version/deploy label or service-change description supplied as context—not an observation.
- Host-tested: requires actual accepted package/install/invoke/output inspection with recorded conditions. None of our sample workflows qualifies; ten 1 October cases remain untested.
- Hypothetical, untested design: proposed copy and flows grounded in documented constraints, not observed output, test success or platform approval.
- Analysis: our inference from documented control points, not a provider forecast or measured benefit.
What still needs a supported host
- One skills-only workflow and one authorized connected task; capture client/version/account, prompts, invocation, actual output and failures.
- Authentic redacted screenshots and a captioned explainer after useful text is available. No fabricated interface images.
- Recheck docs/catalog changes and obtain clarification on annotation fields and endpoint moves; investigate migration continuity only within the relevant account scope.
Links and prices may change. The checked date is not an announcement date or a checkout quote. Machine-readable retrieval guidance explains citation/availability conventions.
Read each study at its dated scope
The 29 September study covers architecture, listings, access, prices and chronology. The 1 October study inspected nine consequential primary sources and exercised offline tooling; it did not recheck those catalog/pricing/migration/chronology claims or test a product workflow.
- Documentation conflicts
- Annotation-justification and MCP endpoint-update guidance remain unresolved. Current IDE exclusion takes precedence over historical launch language; package variants and Canva entitlement limits stay explicit.
- Evidence to collect, not results
- Actual skill and connected-workflow records, precise client/account/version conditions, redacted outputs/screenshots and policy clarification remain future work.
Full architecture and four dated task records · Exercised offline checks and separate blank host contract · Submission conflicts and readiness
The 2 October study narrowly refreshed update/session/MCP claims and added original change-record tooling. In that 2 October study, annotation-justification retained its 1 October paired check; only the later 4 October annotation pairing advances it. Catalog, prices, migration, workspace sync and chronology retain their saved September dates. Current source comparison and exclusions.
The 3 October study narrowly inspected commerce and identity/resource/entitlement sections. General checkout wording and physical-goods saved-method API/UI guidance remain conflicting / unresolved, with no digital exception or universal enabling inferred. Payout/placement and other September observations were not refreshed; endpoint conflict stays 2 October; the later annotation-only pairing advances that conflict to 4 October without refreshing readiness. Current comparison and clock-bracket basis.
The 4 October study inspected action contracts, pure versus stateful effects, independent hints and server-enforced consent. Its 12:59:24–12:59:55 UTC clock bracket is not per-request HTTP time. Logging's incidental-infrastructure annotation scope and real human approval/status recovery remain unresolved; no new rule or implemented operation was established.
The 5 October hook/dependency check brackets current calls at 13:02:45–13:03:15 UTC, not HTTP timestamps or a rule-change date. Only H01–H09 advance: annotation conflict remains 4 October, endpoint 2 October, checkout 3 October; unrefreshed catalog/prices/migration/chronology/surface/worksheet claims keep saved dates. Current definition trust is not established all-byte dependency provenance; policy instructions are not reliable enforcement. Exact source headings and comparison basis.