Skip to content

native-boundary-validation.md

Latest commit

 

History

History
60 lines (48 loc) · 2.73 KB

native-boundary-validation.md

File metadata and controls

60 lines (48 loc) · 2.73 KB
Raw

Native package boundary validation

The host consumes the three archives pinned in vendor/zennotes/manifest.json. There is no main-repository checkout or private editor/store import in the build.

Package checks

npm ci
npm run boundaries:check
npm run typecheck
npm test
npm run build

Run the same checks in a fresh copy containing the package manifest/lock, vendor archives, source, public assets, tooling, TypeScript/Vite/Tailwind/PostCSS config, and native project. Omit node_modules and any historical source clone.

Disposable native runtime

Use a newly created simulator/emulator with no real account or vault. The fixture creates a uniquely named test vault and writes notes and attachments. Do not put this fixture in a release or install it on a personal device.

  1. Run npm run build:boundary-fixture. Only this explicit command adds tooling/native-boundary-fixture.ts to the app; ordinary npm run build does not.
  2. In a disposable checkout, copy dist-boundary-check/ into dist/, then run npx cap sync ios and build the native debug/simulator app as below.
  3. Install and launch on the disposable device. The fixture checks native typing, exact Unicode and trailing whitespace, search, task observation, attachments, note rename, comments, trash/restore, and whole-vault rename under the public workspace transition lock.
  4. Read Documents/boundary-validation.json in the app data container. It must report passed-awaiting-restart with 20 checks and no error.
  5. Terminate and relaunch the app without clearing its data. The report must now be restart-passed, including vault identity, selected note and exact bytes.
  6. Remove the disposable device when finished. Before a normal build, use npm run build and npx cap sync ios to replace the fixture assets.

The fixture uses public core APIs and the native filesystem bridge. It needs no account credentials. It does not prove live Cloud sync, iCloud account behavior, or every third-party storage provider; those remain separate release checks.

iOS native checks

From the repository root, on a configured Xcode installation:

xcodebuild build-for-testing -workspace ios/App/App.xcworkspace \
  -scheme AppCloudUITests -configuration Debug \
  -destination 'generic/platform=iOS Simulator' \
  -derivedDataPath /tmp/zn-boundary-ios-build CODE_SIGNING_ALLOWED=NO

Install the simulator app on a newly created simulator with simctl install. Use simctl get_app_container DEVICE md.zennotes data to locate the report. Do not run account-backed Cloud UI tests against a personal account as part of this fixture. iCloud remains native-host-owned and requires a separate test account/device validation; package adoption does not change its implementation.