go-authcrunch: Skill for Codex

Documents React Integration

This skill is intended for the external React application's agent to read from its AuthCrunch library checkout. Keep implementation in the task's authorized repository; reading this skill does not authorize edits to sibling checkouts. For an app-local AGENTS.md, add a route pointing to this skill at the actual library checkout location. Do not copy a machine-specific path into the app's source. The File Vault bundle now ships under pkg/authn/ui/documents and is served at <portal>/documents/ when Documents is enabled; its React source remains in the separately maintained UI repository.

Read the crypto/wire contract and use the portable crypto.mjs module. Vendor a reviewed version into the frontend's source or bundle it via an explicit build dependency. It is plain ESM using native Web Crypto with no third-party runtime dependencies. It is not currently served by a production asset route. Preserve the protocol and test against the interoperability vector. Use the shared Mermaid sequences and design rationale to follow enrollment/unlock, encrypted upload/download, sharing, revocation and reset. They distinguish local crypto and required React UX from implemented server behavior, and explain retries, key context and account-switch protection. Keep these sequences and the protocol aligned when changing a client workflow.

The OpenAPI source describes the API. Its rendered /#tag/documents catalogue documents every operation's fields, request/response messages, state transitions and retry behavior. Every operation has its own method/resource path, expected response schema, parameter/body examples and native Test Request console. No plaintext-upload endpoint, username-directory endpoint or public share link exists. The manager application and profile application are separate products.