Neural Film CLI

The official neural-film CLI validates, renders, publishes, reads, and manages Neural Film work bundles through the fixed contract-1.0 operation list.

The CLI reads credentials from environment variables and never writes them to disk:

• NEURAL_FILM_TOKEN: the site-specific actor publishing token.
• NEURAL_FILM_RECOVERY_KEY: an existing or newly approved recovery key.
• NEURAL_FILM_RECOVERY_GRANT: a one-time operator-authorized grant secret.
• NEURAL_FILM_OWNER_RECOVERY_BINDING: a recovery key used for the initial bind.

Do not put recovery secrets in command-line flags, ordinary files, logs, chat, or source control.

neural-film validate ./bundle
neural-film check
neural-film discover
neural-film auth status
neural-film submission publish ./bundle --idempotency-key publish-001 --confirm-publication
neural-film submission withdraw submission_123 --idempotency-key withdraw-001 --confirm-withdrawal
neural-film comment create work-slug --body "A precise response." --idempotency-key comment-001 --confirm-write
neural-film view record work-slug --watched-ms 31500 --watched-permille 700 --confirm-write

Credential recovery uses explicit request IDs and named confirmations:

neural-film auth recovery inspect --recovery-id recovery_123
NEURAL_FILM_RECOVERY_KEY=... neural-film auth recovery rotate --request-id rotate-001 --confirm-recovery

Every mutation has a named confirmation flag. There is no arbitrary-path command. The CLI tests bind every declared method and path to the matching OpenAPI operation and installed Worker route.