@terreno/mcp 57.1.0 → 57.3.0

package/src/docs/versioned/0.27.0/tasks/offline-mode.md

@@ -1,139 +0,0 @@
-# Task List: Offline Mode
-
-*Structured task breakdown for automated implementation. Each task should be independently implementable and testable.*
-
-## Phase 1: RTK Core Offline Framework
-
-- [ ] **Task 1.1**: Formalize offline state and queue record types
-  - Description: Extend the offline slice state to represent connection quality, auth-blocked replay, queue record statuses, base timestamps, optimistic/server IDs, and persisted queue versioning. Keep the slice default inert until offline mode is mounted by a consuming app.
-  - Files: `rtk/src/offlineSlice.ts`, `rtk/src/useOfflineStatus.ts`, `rtk/src/index.ts`, related `rtk/src/*.test.ts`
-  - Depends on: none
-  - Acceptance: Unit tests cover enqueue/dequeue/status transitions, conflict storage, auth-blocked state, queue version defaults, and selectors for `online`, `spotty`, `offline`, queued mutations, conflicts, and replay-paused state.
-
-- [ ] **Task 1.2**: Replace endpoint-name-only offline gating with modelRouter config
-  - Description: Introduce a typed `OfflineModelRouterConfig` that maps model names and modelRouter operations to generated RTK Query endpoint names. Preserve a migration path for existing endpoint-name configuration only if it is already shipped behavior; otherwise replace it with the modelRouter config.
-  - Files: `rtk/src/offlineGate.ts`, `rtk/src/offlineMiddleware.ts`, `rtk/src/index.ts`, `rtk/src/offlineGate.test.ts`
-  - Depends on: Task 1.1
-  - Acceptance: Tests prove disabled/default config never defers mutations, enabled modelRouter endpoints are deferred while offline, unconfigured custom routes are not deferred, and array operations can be configured separately from create/update/delete.
-
-- [ ] **Task 1.3**: Add optimistic create ID strategy
-  - Description: Add default ObjectId-compatible ID generation for optimistic modelRouter creates, inject the generated ID into the configured request field, and support per-model overrides for `generateId`, request field, and server ID reconciliation strategy.
-  - Files: `rtk/src/offlineMiddleware.ts`, `rtk/src/offlineGate.ts`, `rtk/src/offlineIds.ts` (new if useful), `rtk/src/index.ts`, related tests
-  - Depends on: Task 1.2
-  - Acceptance: Tests verify default IDs are stable and ObjectId-shaped, custom generators are used, optimistic create cache entries use the same local ID as the queued mutation, and a server-returned replacement ID can be mapped when explicitly configured.
-
-- [ ] **Task 1.4**: Harden optimistic cache update strategies
-  - Description: Make optimistic cache updates explicit per modelRouter operation while providing safe defaults for create, update, delete, array push, array update, and array remove. Expose an override hook so app teams can customize cache updates for complex list filters or response shapes.
-  - Files: `rtk/src/offlineMiddleware.ts`, `rtk/src/offlineOptimistic.ts` (new if useful), `rtk/src/useOfflineStatus.ts`, related tests
-  - Depends on: Task 1.3
-  - Acceptance: Tests cover optimistic insert, patch, remove, and array mutations against RTK Query cache entries, including rollback or conflict marking when replay fails with a non-network/non-auth error.
-
-- [ ] **Task 1.5**: Pause replay on auth refresh failure without clearing cache
-  - Description: Separate token-refresh failure from explicit logout. If refresh cannot complete because the server/network is unavailable or refresh returns a retryable failure, mark replay as auth-blocked and keep RTK Query cache, queue, conflicts, and optimistic records intact. Reserve destructive cleanup for the actual logout action.
-  - Files: `rtk/src/emptyApi.ts`, `rtk/src/authSlice.ts`, `rtk/src/offlineMiddleware.ts`, `rtk/src/offlineSlice.ts`, related tests
-  - Depends on: Task 1.1
-  - Acceptance: Tests simulate expired access tokens with unreachable refresh endpoint and verify queued mutations are held, cache data remains, and replay resumes after auth is refreshed; explicit logout still clears tokens and configured offline/cache state.
-
-- [ ] **Task 1.6**: Implement keep-mine and use-server conflict resolution
-  - Description: Add conflict resolution actions/helpers. `useServer` should discard the queued mutation and patch cache to the server value. `keepMine` should update the queued mutation with the latest server timestamp, reapply the local optimistic value, and retry replay with fresh precondition headers.
-  - Files: `rtk/src/offlineSlice.ts`, `rtk/src/offlineMiddleware.ts`, `rtk/src/useOfflineStatus.ts`, `rtk/src/index.ts`, related tests
-  - Depends on: Task 1.4
-  - Acceptance: Tests cover `409 Conflict` replay responses, stored local/server values, resolving with `useServer`, resolving with `keepMine`, and preventing duplicate conflict records for the same queued mutation.
-
-## Phase 2: Connection Quality and UI
-
-- [ ] **Task 2.1**: Upgrade server status monitoring to connection quality
-  - Description: Extend `useServerStatus` to compute `online`, `spotty`, and `offline` from browser/native reachability events, health-check failures, latency, and recent failure rate. Make health URL, interval, timeout, latency threshold, failure count, and failure-rate thresholds configurable.
-  - Files: `rtk/src/useServerStatus.ts`, `rtk/src/offlineSlice.ts`, `rtk/src/index.ts`, related tests
-  - Depends on: Task 1.1
-  - Acceptance: Tests cover all three connection states, threshold overrides, transition from spotty back to online, transition to offline after configured consecutive failures, and no polling when status monitoring is disabled.
-
-- [ ] **Task 2.2**: Expose richer offline status hooks
-  - Description: Expand `useOfflineStatus` to return connection quality, queue length, syncing state, auth-blocked state, conflicts, local-only helpers, and conflict resolution callbacks while preserving low-level selectors for custom UI.
-  - Files: `rtk/src/useOfflineStatus.ts`, `rtk/src/offlineSlice.ts`, `rtk/src/index.ts`, related tests
-  - Depends on: Task 1.6, Task 2.1
-  - Acceptance: Hook tests or focused unit tests verify returned state and callbacks for queued, syncing, auth-blocked, conflicted, local-only, and healthy states.
-
-- [ ] **Task 2.3**: Update offline banner for online, spotty, offline, syncing, and auth-blocked states
-  - Description: Evolve `OfflineBanner` so apps can show offline, spotty connection, syncing queued changes, pending changes, and auth-blocked sync messaging. Keep props simple enough for custom state sources.
-  - Files: `ui/src/OfflineBanner.tsx`, `ui/src/index.tsx`, `ui/src/OfflineBanner.test.tsx` (new if absent), `demo/stories/OfflineBanner.stories.tsx` (new or update)
-  - Depends on: Task 2.1
-  - Acceptance: UI tests or stories cover hidden/online, spotty, offline, syncing, pending queue, and auth-blocked variants with clear copy and accessible test IDs.
-
-- [ ] **Task 2.4**: Add conflict resolution UI components
-  - Description: Add reusable conflict UI that renders unresolved conflicts and lets users choose "Keep mine" or "Use server". Keep it generic by accepting display renderers for local and server values.
-  - Files: `ui/src/OfflineConflictList.tsx` (new), `ui/src/OfflineConflictCard.tsx` (new), `ui/src/index.tsx`, `ui/src/*.test.tsx`, `demo/stories/OfflineConflict*.stories.tsx`
-  - Depends on: Task 2.2
-  - Acceptance: Tests or stories cover no-conflict, single-conflict, multiple-conflict, keep-mine click, use-server click, dismissed/resolved conflict filtering, and custom value rendering.
-
-## Phase 3: modelRouter Backend Contract
-
-- [ ] **Task 3.1**: Verify client-provided modelRouter create IDs
-  - Description: Add backend tests that prove modelRouter create accepts a client-provided ObjectId-compatible `_id` when the schema allows it and rejects invalid IDs through existing validation/error handling.
-  - Files: `api/src/api.ts`, `api/src/tests/*.test.ts` or existing modelRouter test file, `api/src/tests.ts`
-  - Depends on: Task 1.3
-  - Acceptance: API tests pass for create with client `_id`, returned document keeps that `_id`, duplicate IDs fail safely, and invalid IDs return a clear validation/error response.
-
-- [ ] **Task 3.2**: Formalize conflict response tests for modelRouter updates
-  - Description: Add/extend modelRouter tests for `If-Unmodified-Since` and `X-Unmodified-Since-ISO` headers to guarantee stale updates return `409 Conflict` with the current server document and fresh updates succeed.
-  - Files: `api/src/api.ts`, `api/src/tests/*.test.ts` or existing modelRouter test file
-  - Depends on: none
-  - Acceptance: API tests cover conflict by HTTP-date header, conflict by ISO header, success with current timestamp, missing timestamp behavior, and response body shape consumed by `@terreno/rtk`.
-
-- [ ] **Task 3.3**: Document the modelRouter offline contract
-  - Description: Add docs for modelRouter offline compatibility: supported CRUD/array endpoints, client-provided IDs, conflict headers, expected `409` response shape, permissions behavior, and explicit non-support for custom sync endpoints in v1.
-  - Files: `api/README.md` or package docs, `rtk/README.md` or package docs, `docs/implementationPlans/offline-mode.md`
-  - Depends on: Task 3.1, Task 3.2
-  - Acceptance: Docs show a modelRouter route configuration and matching frontend offline config, and clearly state that custom route sync is future work.
-
-## Phase 4: Example App Integration
-
-- [ ] **Task 4.1**: Enable offline mode for example todos
-  - Description: Wire the example frontend store to mount the offline reducer, persist the offline slice, configure todos modelRouter endpoints for offline create/update/delete, and keep API cache persistence consistent with the offline plan.
-  - Files: `example-frontend/store/index.ts`, `example-frontend/store/sdk.ts`, `example-frontend/app/_layout.tsx`, `example-frontend/package.json` if scripts need updates
-  - Depends on: Task 1.6, Task 2.2
-  - Acceptance: Example app can create, update, and delete todos while offline; queued todos survive app reload when persistence is enabled; replay syncs after the backend is reachable again.
-
-- [ ] **Task 4.2**: Integrate connection banner and sync state in the example app
-  - Description: Add root-level status monitoring and display `OfflineBanner` for offline, spotty, syncing, pending queue, and auth-blocked states. Ensure copy is visible without disrupting auth navigation.
-  - Files: `example-frontend/app/_layout.tsx`, `example-frontend/app/(tabs)/_layout.tsx`, `example-frontend/app/(tabs)/index.tsx`
-  - Depends on: Task 2.3, Task 4.1
-  - Acceptance: Manual test can trigger offline/spotty/syncing/auth-blocked states and see the correct banner copy and pending queue count.
-
-- [ ] **Task 4.3**: Add example conflict resolution flow
-  - Description: Show unresolved todo conflicts in the example app and wire "Keep mine" / "Use server" actions to the RTK conflict resolution helpers.
-  - Files: `example-frontend/app/(tabs)/index.tsx`, `example-frontend/components/*` if a local wrapper is useful
-  - Depends on: Task 2.4, Task 4.1
-  - Acceptance: Manual test can create a stale update conflict, see local/server values, choose "Use server" to accept server state, and choose "Keep mine" to replay local state.
-
-- [ ] **Task 4.4**: Add example backend support tests or fixtures for offline scenarios
-  - Description: Ensure the example backend todo model and route can support client IDs and conflict timestamps. Add tests or fixtures that make the example integration verifiable without modifying generated SDK files manually.
-  - Files: `example-backend/src/models/todo.ts`, `example-backend/src/api/todos.ts`, `example-backend/src/**/*.test.ts`
-  - Depends on: Task 3.1, Task 3.2
-  - Acceptance: Example backend tests pass and confirm todos work with the modelRouter offline contract.
-
-## Phase 5: Verification, Documentation, and Release Readiness
-
-- [ ] **Task 5.1**: Add package-level offline mode docs
-  - Description: Write consumer documentation for enabling offline mode, configuring modelRouter endpoints, selecting ID strategy, configuring connection quality, handling auth-blocked replay, and rendering conflict UI.
-  - Files: `rtk/README.md`, `ui/README.md` if present, `docs/implementationPlans/offline-mode.md`
-  - Depends on: Task 1.6, Task 2.4, Task 3.3
-  - Acceptance: Docs include copy-pasteable store setup, model config, status hook usage, `OfflineBanner`, and conflict resolution examples.
-
-- [ ] **Task 5.2**: Add end-to-end manual verification guide
-  - Description: Document the exact local steps to verify offline create/update/delete, replay, auth-blocked behavior, spotty status, and conflict resolution using example backend and frontend.
-  - Files: `docs/offline-mode-verification.md` (new) or relevant docs directory, `docs/implementationPlans/offline-mode.md`
-  - Depends on: Task 4.3
-  - Acceptance: Guide lists setup commands, offline simulation steps, expected UI states, and cleanup steps; it does not require editing generated SDK files manually.
-
-- [ ] **Task 5.3**: Run focused validation suite
-  - Description: Run and fix failures for the focused packages touched by offline mode.
-  - Files: no source changes expected unless validation finds failures
-  - Depends on: Task 5.1, Task 5.2
-  - Acceptance: `bun run rtk:compile` or equivalent package compile passes, `bun run ui:test` passes for new UI tests, `bun run api:test` passes for modelRouter tests, and example package checks used by the repo pass or have documented blockers.
-
-- [ ] **Task 5.4**: Regenerate SDK only if backend API surface changes
-  - Description: If implementation changes OpenAPI output for modelRouter conflict responses or example backend route schemas, regenerate `example-frontend/store/openApiSdk.ts` using the SDK generation workflow. If no OpenAPI surface changed, explicitly skip this task in the implementation PR notes.
-  - Files: `example-frontend/store/openApiSdk.ts`, `example-frontend/openapi-config.ts`
-  - Depends on: Task 3.3, Task 4.4
-  - Acceptance: Generated SDK is updated only from the backend OpenAPI spec and never edited manually; PR notes state whether SDK regeneration was required.

package/src/docs/versioned/0.27.0/tasks/syncdb-local-first.md

@@ -1,117 +0,0 @@
-# Task List: SyncDB Local-First Data Layer
-
-*Structured task breakdown for automated implementation. Each task should be independently implementable and testable.*
-
-## Phase 1: Foundation
-
-- [ ] **Task 1.1**: Scaffold `@terreno/syncdb` package
-  - Description: Create the package with core entrypoints, lifecycle interfaces, and typed configuration.
-  - Files: `syncdb/package.json` (new), `syncdb/src/index.ts` (new), `syncdb/src/types.ts` (new), `syncdb/README.md` (new)
-  - Depends on: none
-  - Acceptance: package compiles and exports `createSyncDbClient` and configuration types.
-
-- [ ] **Task 1.2**: Define storage and sync contracts
-  - Description: Add canonical interfaces for entities, outbox records, sync cursors, conflicts, and keyring entries.
-  - Files: `syncdb/src/storage/types.ts` (new), `syncdb/src/sync/types.ts` (new), `syncdb/src/crypto/types.ts` (new)
-  - Depends on: Task 1.1
-  - Acceptance: type checks enforce required fields and operations.
-
-## Phase 2: Local DB and Encryption
-
-- [ ] **Task 2.1**: Implement IndexedDB adapter with migrations
-  - Description: Add object stores for entities/outbox/cursors/conflicts/keyring and schema version migration support.
-  - Files: `syncdb/src/storage/indexedDb.ts` (new), `syncdb/src/storage/migrations.ts` (new), `syncdb/src/storage/indexedDb.test.ts` (new)
-  - Depends on: Task 1.2
-  - Acceptance: storage CRUD + migration tests pass.
-
-- [ ] **Task 2.2**: Implement key manager (Web Crypto)
-  - Description: Add DEK generation + wrap/unwrap logic and persistence integration.
-  - Files: `syncdb/src/crypto/keyManager.ts` (new), `syncdb/src/crypto/keyManager.test.ts` (new)
-  - Depends on: Task 1.2
-  - Acceptance: key lifecycle tests pass for generate/wrap/unwrap/reload.
-
-- [ ] **Task 2.3**: Encrypt IndexedDB payloads at rest
-  - Description: Add AES-GCM envelope encryption/decryption and integrate in storage read/write paths.
-  - Files: `syncdb/src/crypto/envelope.ts` (new), `syncdb/src/storage/secureStorage.ts` (new), `syncdb/src/crypto/envelope.test.ts` (new)
-  - Depends on: Task 2.1, Task 2.2
-  - Acceptance: tests verify no plaintext persistence and successful decrypt roundtrip.
-
-## Phase 3: Local Mutation Engine
-
-- [ ] **Task 3.1**: Add optimistic local mutation application
-  - Description: Apply local patches immediately and retain inverse patches for rollback.
-  - Files: `syncdb/src/mutations/optimistic.ts` (new), `syncdb/src/mutations/optimistic.test.ts` (new)
-  - Depends on: Task 2.3
-  - Acceptance: immediate local apply and rollback tests pass.
-
-- [ ] **Task 3.2**: Implement durable outbox state machine
-  - Description: Persist queued mutations and manage transitions `queued -> inFlight -> acked/conflicted/failed`.
-  - Files: `syncdb/src/mutations/outbox.ts` (new), `syncdb/src/mutations/outbox.test.ts` (new)
-  - Depends on: Task 3.1
-  - Acceptance: replay transition and retry logic tests pass.
-
-- [ ] **Task 3.3**: Implement conflict capture and resolution
-  - Description: Persist conflict records and support `useServer` and `keepMine` resolution paths.
-  - Files: `syncdb/src/mutations/conflicts.ts` (new), `syncdb/src/mutations/conflicts.test.ts` (new)
-  - Depends on: Task 3.2
-  - Acceptance: both resolution strategies correctly update local state and queue state.
-
-## Phase 4: Websocket Delta Sync
-
-- [ ] **Task 4.1**: Build sync transport client
-  - Description: Add websocket connect/auth/reconnect lifecycle and sync event channel handling.
-  - Files: `syncdb/src/sync/transport.ts` (new), `syncdb/src/sync/transport.test.ts` (new)
-  - Depends on: Task 1.2
-  - Acceptance: transport lifecycle tests pass including reconnect behavior.
-
-- [ ] **Task 4.2**: Implement cursor-aware delta applier
-  - Description: Apply deltas idempotently with monotonic cursor checks and gap handling.
-  - Files: `syncdb/src/sync/deltaApplier.ts` (new), `syncdb/src/sync/deltaApplier.test.ts` (new)
-  - Depends on: Task 2.3, Task 4.1
-  - Acceptance: ordered delta tests pass; duplicate/out-of-order deltas are safely handled.
-
-- [ ] **Task 4.3**: Wire ack/nack replay coordinator
-  - Description: Connect outbox replay to server ack/nack responses and conflict creation.
-  - Files: `syncdb/src/sync/replayCoordinator.ts` (new), `syncdb/src/sync/replayCoordinator.test.ts` (new)
-  - Depends on: Task 3.3, Task 4.2
-  - Acceptance: ack finalizes queued mutations; nack creates conflict records.
-
-## Phase 5: App Integration and Migration Bridge
-
-- [ ] **Task 5.1**: Implement React hooks and provider
-  - Description: Add `useEntity`, `useQuery`, `useMutation`, `useSyncStatus`, and context provider wiring.
-  - Files: `syncdb/src/react/provider.tsx` (new), `syncdb/src/react/hooks.ts` (new), `syncdb/src/react/hooks.test.tsx` (new)
-  - Depends on: Task 3.3, Task 4.3
-  - Acceptance: hooks update on local mutations and remote deltas.
-
-- [ ] **Task 5.2**: Add Redux migration bridge
-  - Description: Provide optional adapter for Redux-based consumers transitioning from `@terreno/rtk`.
-  - Files: `syncdb/src/bridge/reduxBridge.ts` (new), `syncdb/src/bridge/reduxBridge.test.ts` (new)
-  - Depends on: Task 5.1
-  - Acceptance: bridge supports selector and dispatch-driven mutation usage.
-
-- [ ] **Task 5.3**: Integrate `example-frontend` todos behind `USE_SYNCDB`
-  - Description: Switch todos flow to syncdb under a feature flag while keeping legacy path available.
-  - Files: `example-frontend/store/index.ts`, `example-frontend/store/sdk.ts`, `example-frontend/app/(tabs)/index.tsx`, `example-frontend/app/_layout.tsx`
-  - Depends on: Task 5.1, Task 5.2
-  - Acceptance: flagged path supports offline local create/update/delete and sync reconciliation.
-
-## Phase 6: Codegen and Validation
-
-- [ ] **Task 6.1**: Prototype `@terreno/syncdb-codegen`
-  - Description: Create codegen package that emits typed syncdb operation descriptors from OpenAPI.
-  - Files: `syncdb-codegen/package.json` (new), `syncdb-codegen/src/index.ts` (new), `syncdb-codegen/src/*.test.ts` (new)
-  - Depends on: Task 1.1
-  - Acceptance: generator produces valid descriptors for one sample domain.
-
-- [ ] **Task 6.2**: Author migration docs
-  - Description: Document migration path from `@terreno/rtk` to `@terreno/syncdb` and rollout strategy.
-  - Files: `syncdb/README.md`, `docs/implementationPlans/syncdb-local-first.md`
-  - Depends on: Task 5.3
-  - Acceptance: docs include setup, API usage, and feature-flag rollout playbook.
-
-- [ ] **Task 6.3**: Run validation suite
-  - Description: Execute compile, lint, and tests for touched packages and resolve regressions.
-  - Files: as needed in touched packages
-  - Depends on: Task 6.2
-  - Acceptance: relevant compile/lint/test commands pass with no blockers.

package/src/docs/versioned/0.27.0/tasks/upgrade-banner.md

@@ -1,73 +0,0 @@
-# Task List: Upgrade Banner
-
-*Structured task breakdown for automated implementation. Each task should be independently implementable and testable.*
-
-## Phase 1: Backend + Admin
-
-- [ ] **Task 1.1**: Create VersionConfig Mongoose model
-  - Description: Create the VersionConfig model with schema, interface, and TypeScript types in `@terreno/api`. Fields: webWarningVersion, webRequiredVersion, mobileWarningVersion, mobileRequiredVersion, warningMessage, requiredMessage, updateUrl. All version fields default to 0, messages have sensible defaults.
-  - Files: `api/src/models/versionConfig.ts` (create), `api/src/index.ts` (export)
-  - Depends on: none
-  - Acceptance: Model can be imported from `@terreno/api`, compiles cleanly, schema matches spec
-
-- [ ] **Task 1.2**: Add public `GET /version-check` endpoint
-  - Description: Add a built-in public route via VersionCheckPlugin (TerrenoPlugin) that handles `GET /version-check?version=N&platform=web|mobile`. Fetches the singleton VersionConfig, compares the client's build number against the platform-specific thresholds, and returns a JSON object including status and, when a config exists, version threshold fields: `{status, message?, updateUrl?, requiredVersion?, warningVersion?}`. Returns `{status: "ok"}` if no config document exists.
-  - Files: `api/src/versionCheckPlugin.ts` (create - exports VersionCheckPlugin)
-  - Depends on: Task 1.1
-  - Acceptance: Endpoint returns correct status for all combinations: no config → ok, version >= warning → ok, version < warning → warning, version < required → required. No auth required.
-
-- [ ] **Task 1.3**: Add admin `GET/PUT /admin/version-config` routes
-  - Description: Add admin-only routes for reading and upserting the singleton VersionConfig document. GET returns the current config (or defaults if none exists). PUT upserts the document. Both require `Permissions.IsAdmin`. Wire into AdminApp or as standalone admin routes.
-  - Files: `admin-backend/src/adminApp.ts` (modify) or `api/src/routes/versionCheck.ts` (extend)
-  - Depends on: Task 1.1
-  - Acceptance: Authenticated admin can GET and PUT the config. Non-admin gets 403. PUT creates if not exists, updates if exists.
-
-- [ ] **Task 1.4**: Add admin frontend Version Config screen
-  - Description: Create a custom admin screen in `@terreno/admin-frontend` for editing the singleton VersionConfig. Form with all fields, "Save" button that PUTs to `/admin/version-config`. Add it as a special entry in the admin model list or as a standalone screen.
-  - Files: `admin-frontend/src/AdminVersionConfig.tsx` (create), `admin-frontend/src/index.tsx` (export)
-  - Depends on: Task 1.3
-  - Acceptance: Admin can view and edit all version config fields. Save persists to backend. Form loads existing values on mount.
-
-- [ ] **Task 1.5**: Write unit tests for version check logic
-  - Description: Test the version check endpoint logic: no config returns ok, version comparisons for web and mobile platforms, edge cases (version = 0, version = threshold exactly, missing query params).
-  - Files: `api/src/__tests__/versionCheck.test.ts` (create)
-  - Depends on: Task 1.2
-  - Acceptance: All test cases pass covering ok/warning/required status for both platforms.
-
-- [ ] **Task 1.6**: Wire up example backend
-  - Description: Ensure the example backend includes the VersionConfig model and version-check endpoint. Verify the admin panel shows the version config screen.
-  - Files: `example-backend/src/server.ts` (modify if needed)
-  - Depends on: Task 1.3, Task 1.4
-  - Acceptance: Running the example backend exposes `/version-check` and `/admin/version-config`. Admin panel shows the config screen.
-
-## Phase 2: Client + CI
-
-- [ ] **Task 2.1**: Create `UpgradeRequiredScreen` component
-  - Description: Build a full-screen blocking component in `@terreno/ui`. Centered layout with warning icon, configurable message text, and an "Update" button. The button calls an `onUpdate` callback prop. No dismiss, no navigation escape. Props: `message: string`, `onUpdate: () => void`.
-  - Files: `ui/src/UpgradeRequiredScreen.tsx` (create), `ui/src/index.ts` (export)
-  - Depends on: none
-  - Acceptance: Component renders full-screen with message and button. Button triggers onUpdate. No way to dismiss or navigate away.
-
-- [ ] **Task 2.2**: Create `useUpgradeCheck` hook
-  - Description: Build a hook in `@terreno/rtk` that checks `GET /version-check` on mount. Gets build number from `Constants.expoConfig.extra.buildNumber`, platform from existing `IsWeb` util. On "warning": shows persistent toast with message + "Update" button + dismiss X. On "required": returns `{isRequired: true, requiredMessage, onUpdate}`. The `onUpdate` function handles platform logic: web → `window.location.reload()`, mobile → try `expo-updates` `fetchUpdateAsync()`/`reloadAsync()`, fall back to `Linking.openURL(updateUrl)`. Skips check if build number is undefined.
-  - Files: `rtk/src/useUpgradeCheck.ts` (create), `rtk/src/index.ts` (export)
-  - Depends on: Task 1.2
-  - Acceptance: Hook returns correct state for ok/warning/required. Toast appears for warning. isRequired flag set for required. onUpdate triggers appropriate platform action.
-
-- [ ] **Task 2.3**: Add `app.config.ts` build number injection
-  - Description: Create or update `app.config.ts` in the example frontend to dynamically set `expo.extra.buildNumber` from `git rev-list --count HEAD` at build time. Document the pattern for consuming apps.
-  - Files: `example-frontend/app.config.ts` (create/modify), `example-frontend/app.json` (may need adjustment)
-  - Depends on: none
-  - Acceptance: Running `expo start` or `expo build` sets `Constants.expoConfig.extra.buildNumber` to the current git commit count.
-
-- [ ] **Task 2.4**: Wire up example frontend
-  - Description: Add `useUpgradeCheck()` to the example frontend's root layout. When `isRequired` is true, render `UpgradeRequiredScreen` instead of normal app content.
-  - Files: `example-frontend/app/_layout.tsx` (modify)
-  - Depends on: Task 2.1, Task 2.2, Task 2.3
-  - Acceptance: Example app checks version on mount. Warning shows toast. Required shows blocking screen. Normal operation when version is ok or build number is missing.
-
-- [ ] **Task 2.5**: Document GitHub Actions build number pattern
-  - Description: Add a CI snippet or documentation showing how to inject the build number in GitHub Actions workflows using `git rev-list --count HEAD`. Include examples for both EAS Build and web deployments.
-  - Files: `docs/how-to/upgrade-banner.md` (create) or inline in example-frontend README
-  - Depends on: Task 2.3
-  - Acceptance: Clear instructions for consuming apps to set up automatic build numbering in CI.

package/src/docs/versioned/0.28.0/README.md

@@ -1,29 +0,0 @@
-# Terreno Documentation
-
-Documentation for the Terreno monorepo: shared packages for full-stack applications with React Native and Express/Mongoose.
-
-## Structure
-
-- **[Tutorials](tutorials/)** — Learning-oriented, hands-on lessons
-- **[How-to guides](how-to/)** — Problem-oriented, practical steps
-- **[Reference](reference/)** — Technical reference for APIs and packages
-- **[Explanation](explanation/)** — Concepts and context
-- **[Implementation Plans](implementationPlans/)** — Forward-looking plans for major features
-
-## Packages
-
-| Package | Description |
-|---------|-------------|
-| [@terreno/api](reference/api.md) | REST API framework (Express/Mongoose) |
-| [@terreno/ui](reference/ui.md) | React Native UI component library |
-| [@terreno/rtk](reference/rtk.md) | RTK Query utilities for API backends |
-| [@terreno/admin-backend](reference/admin-backend.md) | Admin panel backend plugin |
-| [@terreno/admin-frontend](reference/admin-frontend.md) | Admin panel frontend screens |
-| [@terreno/api-health](reference/api-health.md) | Health check endpoint plugin |
-| [@terreno/mcp](reference/mcp-server.md) | AI coding assistant integration (MCP) |
-
-## Quick links
-
-- [Getting started](tutorials/getting-started.md)
-- [AGENTS.md](../AGENTS.md) — Onboarding context for AI assistants
-- [.cursorrules](../.cursorrules) — Project and code style rules

package/src/docs/versioned/0.28.0/explanation/README.md

@@ -1,14 +0,0 @@
-# Explanation
-
-Understanding-oriented documentation: concepts, architecture, and context.
-
-## Contents
-
-- [AI-powered workflows](ai-workflows.md) — Autonomous documentation, testing, and maintenance workflows
-- [Authentication architecture](authentication.md) — How JWT, OAuth, and token refresh work
-- [Configuration system](configuration-system.md) — Runtime configuration with database persistence
-- [Dependency management](dependency-management.md) — Dependabot, auto-merge, and security practices
-- [GCP hosting architecture](gcp-hosting-architecture.md) — Static site hosting with GCS and Cloud CDN
-- [Modular API design](modular-api-design.md) — 🚧 Why TerrenoApp replaces setupServer
-- [modelRouter actions](model-router-actions.md) — Named collection and instance operations on modelRouter
-- [No barrel imports](no-barrel-imports.md) — Import concrete modules, not `index` re-export barrels