@meadow-studio/platform 0.1.1 → 0.1.3

package/docs/PLATFORM_GUIDE.md

@@ -90,11 +90,30 @@ records, and release history. The generated foundation currently uses:
 - Vitest unit tests and coverage thresholds;
 - Playwright phone and tablet screenshot comparisons;
 - a repository-local app-development skill linked from `AGENTS.md`;
+- a pinned `@meadow-studio/design` dependency and its shared fonts and semantic tokens;
 - GitHub Actions for quality, web, visual, Android, and unsigned iOS builds; and
 - exact dependency versions and immutable GitHub Action revisions.
 
-Ionic and Meadow Design are not part of the foundation. Either may be adopted by an app as an explicit
-app-owned choice.
+Generated app scripts also build and install local iOS and Android debug apps with either the
+development or production web configuration. `npm run deploy:ios` and `npm run deploy:android`
+default to development. Deployments remember the last successful device separately for each app
+and platform; `-- --select` opens the device picker again. `meadow sync` keeps the deploy scripts
+aligned with the enabled native targets; signed store distribution remains a separate release step.
+
+Meadow Design is the default starting point for new app UI. The app adapts its semantic tokens,
+components, illustrations, and layouts to its product direction; the platform runtime remains
+independent of the design package. An established app can retain a different design system. Ionic
+remains an app-owned choice.
+
+The generated settings page follows Stay Light's structure: short, muted section headings above
+individual Meadow list items, with trailing values and no card wrappers around groups. Generated
+agent instructions and the app-development skill preserve that structure when preferences are
+added, unless the user explicitly requests a different layout. Meadow Design documents the
+composition in its Settings recipe; each app still owns its preferences, content, and theme.
+
+New apps also receive a Stay Light-style launch view: their title and short description are shown
+with a logo that arrives over 1.6 seconds. The generated logo is a placeholder for each product to
+replace; visual tests bypass the launch view to capture stable app pages.
 
 ## Ownership boundary
 
@@ -136,7 +155,7 @@ needs rather than hypothetical completeness.
 | Analytics | `MeadowAnalyticsService` persists explicit consent, requires a configured production environment, allowlists events/properties, and delivers native events through Firebase without exposing provider types. | The app owns its event catalogue, tracking moments, consent UI/copy, disclosures, and Firebase project. Web, development, and test delivery remain off. |
 | Crash reporting | `MeadowCrashReportingService` persists separate explicit consent and provides failure-safe handled-error and breadcrumb APIs over native Firebase Crashlytics. Generated native projects start collection off and eagerly enforce environment and consent state at startup. | The app owns consent UI/copy and decides which non-sensitive diagnostic context is appropriate. Final Firebase console and iOS symbol-upload verification remain release checks. |
 | App rating | `MeadowAppRatingService` calls the system store surface on native platforms with concurrency, version, cooldown, and rolling-year safeguards. | The app decides the meaningful success moment; Apple and Google decide whether a prompt appears. |
-| Infrastructure UI | `@meadow-studio/platform/ui` provides app-build information and privacy/support links with app-overridable labels and CSS variables. | It is not a design system; feature UI stays with the app or optional Meadow Design. |
+| Infrastructure UI | `@meadow-studio/platform/ui` provides app-build information and privacy/support links with app-overridable labels and CSS variables. | Feature UI uses Meadow Design by default and remains app-owned in its composition and product behavior. |
 | Local data | `meadow add local-data` generates migrated SQLite, transactions, a typed document store, browser IndexedDB persistence, tests, and safety checks. Browser persistence and Android compilation are validated; a clean iOS simulator compile of this optional recipe remains pending. | Tables, domain mapping, data sensitivity decisions, and deletion/reset behavior remain app-owned. |
 | Local notifications | `meadow add notifications` pins and synchronizes the native provider. `MeadowNotificationService` exposes permission state, an explicit permission request, one-off and calendar schedules, replace/cancel/pending operations, Android channels, normalized failures, and tap actions. Web and disabled apps safely report the capability as unavailable. Clean generated Android and iOS simulator builds passed; on-device delivery remains app release verification. | The app owns permission explanation and trigger, copy, IDs, timing rules, channels, tap navigation, and analytics. Meadow never prompts as a scheduling side effect and uses inexact Android alarms by default. |
 | Firebase setup | The base app includes Analytics and Crashlytics dependencies; `meadow configure firebase` validates the files needed by enabled platforms, synchronizes native projects, installs Android build plugins, and registers `GoogleService-Info.plist` as an iOS app resource. `meadow doctor` checks dependencies, files, plugins, bundled resources, and opt-in defaults. | The app owns its Firebase project and must verify an event and test crash on a device before release. iOS dSYM upload configuration remains app-specific release setup. |

package/docs/PROJECT_BRIEF.md

@@ -47,8 +47,8 @@ App          → The unique product/domain logic
 
 Meadow Design and Meadow Platform are separate concerns.
 
-Meadow Design is an optional reusable design system. It is not part of the generated platform
-foundation, and applications such as 24h Pushups can own a completely different visual language.
+Meadow Design is the default reusable design system in newly generated apps. It remains a separate
+package from the platform runtime, and an app may intentionally use a different visual system.
 
 Meadow Platform provides reusable application infrastructure, integrations, configuration, tooling,
 and release guardrails, with further automation added only when real release work proves its value.
@@ -58,8 +58,8 @@ Individual apps should contain as little generic infrastructure as reasonably po
 ## Repository Strategy
 
 Meadow Platform and Meadow Design live as independent projects in the same private repository. They
-have separate package manifests, builds, tests, and ownership boundaries. Meadow Design remains
-optional for every application; the platform does not depend on it.
+have separate package manifests, builds, tests, and ownership boundaries. The app generator pins
+Meadow Design by default, but the platform runtime does not depend on it.
 
 Individual apps live in their own repositories. Each repository keeps the mobile app at its root
 and a separate, app-owned `website/` project for its public app reference, support, and legal pages.
@@ -175,7 +175,8 @@ The current shared app foundation uses:
 - TypeScript
 - Firebase Analytics and Crashlytics
 
-Ionic and Meadow Design are app-owned choices, not Meadow Platform dependencies.
+Ionic remains an app-owned choice. Generated apps start with Meadow Design, while the platform
+runtime remains independent of that design package. Apps own their final visual language.
 
 Stay Light is the first major reference application.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meadow-studio/platform",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "publishConfig": {
     "access": "public",
     "registry": "https://registry.npmjs.org/"