# Local readiness checkpoint — 2026-09-11

Historical pre-upload snapshot: the table below records the local gate before authorization,
not current remote state. See [release verification](../RELEASING.md) for the later public
repository and hosted acceptance evidence. The personal application remains outside Git.

| Gate | Observed status |
| --- | --- |
| Original MoonBit-first implementation | Core, JSON protocol, CLI, examples implemented; no copied puzzle implementation |
| Duplication | Installed official assistant skill + registry + MoonCakes/GitHub scoped research; 29 API requests across selection/recheck |
| Formatting/API | moon fmt --check and generated interface drift check pass |
| wasm-gc / wasm / js | Strict check, release build, 43 tests each and executable tutorial pass |
| Native | Strict check passes; build/test/example UNVERIFIED: no system C compiler |
| Independent oracle | 20096 board/goal cases, 1164 replayed solutions, 15606 sound obstruction checks |
| CLI/examples | 11 process cases and eight request fixtures pass |
| Consumer | Separate local path dependency imports core/protocol and passes its smoke test |
| Documentation/license | README, API, architecture, tutorial, testing, MIT, notices, AI, security and contributing present |
| History | Real incremental commits with per-commit successful check/test records; generate audit with scripts/history-audit.py |
| Git isolation | Repo-local kekeshuo identity only; no global identity changes; no remote configured |
| GitHub/CI/Release | NOT created, pushed or run; waits for explicit account confirmation |
| Application | Draft outside repository; only participant name/contact and uncreated repository URL remain unknown |
| MoonCakes | NOT published; manual participant step after explicit release readiness |

Raw command evidence and application remain in the sibling participant directory, outside Git.
The portable history-audit script verifies commit SHAs, changed paths, authors and recorded checks;
its output also stays outside Git to avoid self-referential commit hashes and participant data.
The foundation commit is conservatively excluded from the valid-count threshold even though it
contains actual design/license/research work. No empty or formatting-only commits are used.

## Remote completion still required

1. Confirm intended account kekeshuo after the local gate; authenticate through the official
   browser/CLI flow if needed. Never send credentials in chat or switch another window's account.
2. Recheck active CLI identity, API login, intended owner/repository and repo-local author email.
3. Create the confirmed public repository, push only this isolated repo, and verify push permission
   and public GitHub commit-author mapping. Local author text alone is not contribution proof.
4. Observe all four hosted CI jobs, including native runtime, fix failures if any, and create a
   release only at the tested commit. Verify branch/tag/Release agreement.
5. Fill actual participant fields and repository URL, regenerate the outside-Git commit/completion
   audits, run the submission checker strictly, then update the permanent registry accurately.

Official September deadline recorded by the installed skill is September 24, 2026. The skill's
20 valid-commit threshold is extra; the fixed official rules do not specify a minimum commit count.