[niyonx]

Adds a PostOnce template in social-media/postonce so a NanoClaw group can discover social account capabilities and prepare drafts through the hosted PostOnce MCP server. The template includes a portable skill and credential-free MCP configuration. Its README discloses paid Creator/Pro access, own-key scopes, OneCLI setup, and the default runner's permission behavior. No model, provider, scheduled task, or shared credential is installed.

Validation:

• Registry checks pass for all seven templates; generated index is stable and the new-template version check passes.
• Pinned NanoClaw 2.3.0 native CLI stamps the literal social-media/postonce reference and preserves ownership boundaries.
• Actual NanoClaw container/provider wiring through OneCLI reaches hosted PostOnce: discovery, owned PNG upload with matching downloaded bytes, unpublished draft create/read and stable idempotent replay. The image draft reopens in PostOnce. Revocation yields HTTP 401; a replacement key restores the same unchanged draft, then fails after revocation.
• The optional native Codex provider/app-server was separately tested with gpt-5.6-sol at medium reasoning. It read the canonical skill and used configured MCP server postonce to read 29 active entries and the unchanged image draft. No cloud connector or model write was used in this positive test.
• A fresh isolated post-revocation model run encountered native MCP AuthRequired and truthfully reported unavailable, with no remote calls or cached account data. A separate transport probe confirmed HTTP 401.

The original media harness reported a false failure from JSON object property order; deep comparison of captured results confirmed identical fields, ID and timestamps. A first negative model experiment used a separately authorized account cloud connector after the configured MCP rejected authentication; it did not prove denial. The final negative run disabled supported apps/plugins/remote_plugin features only for that child process and used fresh state. Existing account connections were unchanged.

Gateway management used a fixed authentication fixture, sealed with 403 during model execution. Full mailbox/chat onboarding and social publishing were not tested. This contribution is original PostOnce material under the repository's MIT terms; submission does not claim approval or a template-library listing.

Additional native model validation: a fresh supported Codex OAuth session using the unchanged pinned image read the canonical skill, created an unpublished public-image draft, read the returned ID, updated it using the preceding read version and an explicit stable update key, then read it again. Independent native-event and database checks confirmed the revised caption, preserved PNG, inbox state and empty destinations. All calls used the configured PostOnce MCP server without cloud/plugin context. No forced replay or social publication was tested. Temporary API and provider vault credentials were removed and task services stopped. This remains an isolated native provider/app-server test, not full mailbox onboarding.

[niyonx]

Friendly ping: this still merges cleanly against main. Happy to change anything you'd like (category, naming, or the OneCLI setup steps). Thanks for maintaining the catalog.