Repository navigation
docs: verify alpha data gates and expose uppercase PLAN - #12
Merged
Merged
Conversation
IsaacHuo
added a commit
that referenced
this pull request
Oct 25, 2026
Prepare 0.1.0-alpha.1 after the data/permission gates in PR #12. VERSION, npm root/lock identity and OpenAPI metadata agree; API shapes, the dependency graph, SQLite version 1 and archive v1/v2 compatibility are unchanged. The dated changelog, bilingual startup instructions, security scope and third-party notices define a Windows-first metadata-research source preview with no installer or bundled runtime binaries. Two candidate failures were repaired before merge: - A Fandol font range failed certificate validation through the rotating CTAN endpoint. A fixed MIT CTAN mirror serves the same 4,947,904 bytes and existing SHA-256; TLS verification stays enabled. Real HTTPS verification and subsequent CI preparation/compilation passed. - Concurrent upload callbacks appended to stale material selections, losing a selected input. They now merge with the latest conversation selection. The strengthened browser scenario holds both upload responses until both files exist: it failed before the fix and passed after, preserving selections through reload and run creation. Windows validation (Node.js 24.19.0 / npm 11.17.0): check (57 tests), build, 13 browser scenarios, actionlint 1.7.12, Gitleaks 8.30.1, npm audit (zero vulnerabilities), identity/OpenAPI/dependency-graph/source-exclusion checks and whitespace checks passed. Typecheck/build and the full browser suite were repeated after the selection repair. Actual candidate source tar excludes research data, credentials, dependencies/build/test artifacts, local Skills/hooks, Supervisor-Skills and prepared TeX/fonts. No new live model calls; existing bundle-size advisories remain. Merge only after exact-head required-checks and resolved reviews. Publish only after the exact main push CI and release dry-run pass, using the existing immutable-tag prerelease workflow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The alpha data and permission audit maps each gate to existing Platform, Store, Documents, runtime and service tests. The focused seven-file suite passed 30 tests on Windows (Node.js 24.19.0), with no live provider calls or schema changes. Preview limits remain explicit.
Rename the root plan to uppercase PLAN.md as requested, show the current phase and ordered ENG-00–06 acceptance exits at the top, preserve both historical ledgers, update all links and synchronize English/Chinese README navigation. STATUS is now a short current handoff; detailed ENG-03 CI and historical evidence stay in verification.md.
Validation: Markdown lint (36 files), repository/link validation (159 files), git diff --check and the 30-test gate suite passed. PR #11 was merged only after Windows/Linux/browser/actionlint/Gitleaks/required-checks passed; its 57-test/13-browser evidence remains separate. This PR changes documentation only. Required checks on this exact head remain the merge gate.