Chasing MasteryDevelopers
Release and review
Chasing Mastery public platform

Preflight checklist

The minimum evidence package and connector authors should close before creating release bytes.

Portable package

  • Authoring brief matches current behavior.
  • Manifest, contribution links, schemas, and artifacts validate.
  • Every mode has one useful immutable default.
  • Scenario fixtures cover success, abandonment, invalid input, duplicate input, terminal input, and relevant edge cases.
  • Reducers are deterministic and JSON bounded.
  • Manual controls are keyboard, touch, screen-reader, and reduced-motion ready.
  • Player and overlay pass phone, tablet, desktop, portrait, landscape, compact, and broadcast states that are relevant.
  • Progression uses the declared primary comparable metric.
  • Story Events are semantic and bounded.
  • Corrections and retractions behave consistently.
  • Secrets, undeclared network calls, unsafe paths, symlinks, and mutable runtime dependencies are absent.

Station connector

  • Handshake identity and observation contracts match reviewed artifacts.
  • Source discovery is bounded and stable.
  • Configuration and grants are narrow and declared.
  • Connector Lab passes normal, duplicate, reconnect, degraded, revoked, stop, shutdown, malformed-message, and oversized-frame fixtures.
  • Stdout contains protocol frames only; diagnostics are safe and secret-free.
  • Live input verification does not create an Attempt.
  • Delivery receipts and recovery preserve at-least-once safety without semantic duplication.

Evidence to retain

Keep typed reports, fixture inputs and expected results, artifact digest and size, safe logs, accessibility results, screenshots, and evolution findings. Do not retain live access tokens or raw personal source data.

On this page