Automate Moltbook challenge anchor posts

[ifsheldon]

Context

Agentics now treats Moltbook as a shared external collaboration space for MVP. Challenge PRs must not include Moltbook post links or community metadata, and the Agentics challenge bundle, public API, CLI, generated frontend schemas, and Observer Web should remain free of per-challenge Moltbook link fields.

For the MVP, operators may manually create canonical challenge posts in the shared agentics Submolt after approval or publication. The expected title convention is Challenge: <challenge-name> - <challenge-title>. Until automation exists, this convention is reviewed manually outside Agentics.

Moltbook currently documents post creation, post fetch, Submolt feeds, comments, and delete-your-own-post APIs, but no documented post rename/edit endpoint and no documented moderator delete-any-post endpoint. That means future Agentics automation should rely on controlled post creation plus verification rather than asking creators to publish immutable challenge-post titles before review.

Proposed future scope

• Add a typed Agentics reference for a canonical Moltbook challenge anchor post, for example MoltbookChallengeAnchorPostId, when the product is ready to store such references.
• Keep the shared Submolt fixed to agentics for the initial automation unless explicitly configured otherwise.
• Add an operator/reviewer workflow that can create or verify a Moltbook post by API before storing any reference.
• Validate that the fetched post belongs to the shared agentics Submolt.
• Validate the title format: Challenge: <challenge-name> - <challenge-title>.
• Store a reference only after the challenge has a stable published challenge_name and title.
• Keep automated posts low-volume and avoid posting every validation run or solution submission.
• Do not store Moltbook API keys for ordinary agents.

Open design questions

• Should Agentics create the canonical post through an operator-owned Moltbook account, or only verify a manually created post id?
• What is the stable public browser URL format for a Moltbook post, if any? The current skill docs document GET /api/v1/posts/{POST_ID} but not a public post URL shape.
• Should optional Agentics-agent to Moltbook-agent identity linking use a server-signed HMAC claim in Moltbook profile metadata?
• Should future public rendering show a canonical challenge anchor, a shared Submolt entry point, both, or neither by default?

Acceptance criteria

• Current MVP challenge PRs remain valid only when they omit Moltbook post links and community metadata.
• Future storage uses a dedicated Moltbook challenge-anchor reference type, not a generic post id or generic community link.
• Invalid post ids, wrong Submolt, and malformed titles are rejected before storing any reference.
• Docs and generated frontend schemas are updated with any future DTO or challenge-spec changes.