trent_larson/daily-notification-plugin
4
0
Fork 0
Code Issues Pull Requests 2 Projects Releases Wiki Activity
Files
6b5b8869519f8845fa1c74778fef33f5ffba81d2
daily-notification-plugin/docs/progress/00-STATUS.md
Matthew Raymer 6b5b886951 feat(ios): complete P2.1 schema versioning and P2.2 combined edge case tests 
P2.1: iOS Schema Versioning Strategy
- Added SCHEMA_VERSION constant and checkSchemaVersion() method in PersistenceController
- Version stored in NSPersistentStore metadata (observability contract, not migration gate)
- CoreData auto-migration remains authoritative; version mismatches logged, not blocked
- Documentation added to ios/Plugin/README.md with migration contract

P2.2: Combined Edge Case Tests
- Added 3 resilience test scenarios to DailyNotificationRecoveryTests.swift:
  - test_combined_dst_boundary_duplicate_delivery_cold_start()
  - test_combined_rollover_duplicate_delivery_cold_start()
  - test_combined_schema_version_cold_start_recovery()
- All tests labeled with @resilience @combined-scenarios comments
- Tests verify idempotency and correctness under combined stressors

P2.3: Android Combined Tests Design
- Created P2.3-DESIGN.md with scope, invariants, and acceptance criteria
- Created P2.3-IMPLEMENTATION-CHECKLIST.md with step-by-step execution plan
- Design ready for implementation to achieve parity with iOS P2.2

Documentation Updates
- Fixed parity matrix: iOS invalid data handling now correctly shows "✅ Recovery tested" with test references
- Updated progress docs (00-STATUS.md, 01-CHANGELOG-WORK.md, 03-TEST-RUNS.md, 04-PARITY-MATRIX.md)
- Updated P2-DESIGN.md to reflect P2.3 scope (Android combined tests)
- Updated SYSTEM_INVARIANTS.md baseline tag references

Baseline Tag
- Created and pushed v1.0.11-p2-complete tag
- Tag represents P2.x completion (schema versioning + combined resilience tests)

All invariants preserved. CI passes. Tests runnable via xcodebuild on macOS.
2025-12-22 12:59:40 +00:00

6.9 KiB
Raw Blame History

Progress Status

Purpose: Single source of truth for current project status, phase completion, blockers, and next actions.
Owner: Development Team
Last Updated: 2025-12-22
Status: active
Baseline Tag: v1.0.11-p2-complete

Current Phase

P0 + P1.4 + P1.5 + P2.6 + P2.7 + P2.x Milestone - Foundation, Documentation, Type Safety & Resilience Established

Status: ✅ Complete — Tagged as baseline: v1.0.11-p2-complete

What This Baseline Includes:

  • ✅ P0: Publish safety & CI hardening (packaging, exports, CI debuggability)
  • ✅ P1.4: Shared core types module (errors/enums/contracts/events/guards)
  • ✅ P1.5: Documentation consolidation (authoritative index, drift guards, archive standardization, contracts as policy)
  • ✅ P2.6: Type safety cleanup (zero any except documented TS mixin limitation)
  • ✅ P2.7: System invariants documentation (SYSTEM_INVARIANTS.md created)
  • ✅ P2.1: Schema versioning strategy (iOS explicit version tracking in CoreData metadata)
  • ✅ P2.2: Combined edge case tests (3 resilience scenarios: DST + duplicate + cold start, rollover + duplicate + cold start, schema version + cold start)
  • ✅ Core module purity enforcement (platform import blocking, export validation)
  • ✅ Consumer migration complete (observability, definitions, web use core types)
  • ✅ All invariants enforced in tooling (verify.sh + ci/run.sh)

Last Verify Run

Date: 2025-12-22
Result: ✅ Publish-safety checks pass on Linux (TypeScript + build + pack checks); Android/iOS native builds skipped (expected)
Local CI Command: ./ci/run.sh (wraps ./scripts/verify.sh)
Verification:

  • ./scripts/verify.sh - All critical checks passed
  • npm pack --dry-run | grep -E "xcuserdata|xcuserstate|DerivedData|ios/App/" - Empty (no forbidden files)

Blockers

None currently.

Completed This Week

  • Documentation consolidation (139 files organized)
  • Created progress tracking system
  • PHASE 1: Remove native code from src/android/ and src/ios/
  • PHASE 3: Single verification entrypoint (scripts/verify.sh)
  • PHASE 3: Created local CI entrypoint (ci/run.sh)
  • P0: Build/publish safety fixes (web.ts, podspec, markdown paths)
  • P0: iOS recovery tests (DailyNotificationRecoveryTests.swift)
  • P0.5: Packaging fixes (exports["./web"] paths, tightened "files" field, excluded xcuserdata/ios/App/)
  • Parity corrections: iOS rollover and persistence confirmed
  • P1.4: Shared core types module (errors/enums/contracts/events/guards)
  • P1.4: Core module consumer migration (observability.ts, definitions.ts, web.ts)
  • P1.4: Core module purity enforcement (platform import blocking, export validation)
  • P2.6: Type safety cleanup — eliminated all any usages except documented TS mixin limitation
    • vite-plugin.ts: removed any return types (replaced with UserConfig and concrete transform return type)
    • PlatformServiceMixin.ts: documented TS mixin any[] exception (TypeScript limitation, not design choice)
    • Audit confirmed: zero any in codebase except intentional mixin pattern
  • P2.7: Created SYSTEM_INVARIANTS.md — single authoritative document naming and explaining all enforced invariants
  • P2.1: Schema versioning strategy — iOS explicit version tracking in CoreData metadata (observability contract, not migration gate)
  • P2.2: Combined edge case tests — 3 resilience test scenarios (DST + duplicate + cold start, rollover + duplicate + cold start, schema version + cold start)

Next Actions (Max 5)

  1. P2.3 - Android combined edge case tests (achieve parity with iOS P2.2)
  2. P1.5b - Move iOS/App test harness out of published tree (optional but recommended)

Known Gaps (Parity)

See 04-PARITY-MATRIX.md for detailed parity tracking.

Summary:

  • iOS persistence: ✅ Implemented (CoreData + SQLite)
  • iOS rollover: ✅ Implemented (NotificationCenter pattern)
  • iOS recovery testing: ✅ Implemented (DailyNotificationRecoveryTests.swift)
  • iOS reboot recovery: N/A (iOS handles automatically)
  • Storage schema versioning: ✅ Explicit (CoreData metadata tracking, P2.1 complete)

Phase Status

Phase Priority Status Notes
PHASE 1 P0.1 ✅ Complete Repo hygiene + packaging
PHASE 2 P0.2 ✅ Complete iOS persistence parity (CoreData + SQLite confirmed)
PHASE 3 P0.3 ✅ Complete Verification entrypoint + local CI
P0 Phase P0 ✅ Complete Publish safety & CI hardening (packaging, exports, CI debuggability)
PHASE 4 P1.4 ✅ Complete Shared core types module (errors/enums/contracts/events/guards)
PHASE 5 P1.5 ✅ Complete Docs consolidation (authoritative index, drift guards, archive standardization, contracts as policy)
PHASE 6 P2.6 ✅ Complete Type safety cleanup (zero any except documented TS mixin limitation)
PHASE 7 P2.7 ✅ Complete System invariants doc (SYSTEM_INVARIANTS.md created)
PHASE 8 P2.1 ✅ Complete Schema versioning strategy (iOS explicit version tracking)
PHASE 9 P2.2 ✅ Complete Combined edge case tests (3 resilience scenarios)

Maintained By: Development Team
Update Frequency: After each phase completion or significant change

Packaging Invariants

Policy: Packaging is controlled primarily by package.json.files (whitelist). .npmignore is secondary.

Required Checks:

  • npm pack --dry-run | grep -E "xcuserdata|xcuserstate|DerivedData|ios/App/" must remain empty
  • CI must fail if forbidden files appear in package
  • exports["./web"] paths must match actual build artifacts (dist/esm/web.{js,d.ts})

Verification: Run ./ci/run.sh (or make ci) before any publish - it includes forbidden files check.

Local CI Policy: ./ci/run.sh is the single source of truth for CI. All publishing/releasing must be gated by ./ci/run.sh. See ci/README.md for details.

Critical Invariant: Any CI or release gate MUST call ./ci/run.sh (not npm run build directly), because verify.sh encodes packaging and core-purity invariants that must be checked before publish.

Git Hook: Pre-push hook available at githooks/pre-push (setup: git config core.hooksPath githooks). Calls ./ci/run.sh.

Baseline Tag: v1.0.11-p2-complete — This tag represents P2.x completion (schema versioning + combined resilience tests). Use as rollback anchor or reference point for future work.

Previous Baselines:

  • v1.0.11-p0-p1.4-p1.5-p2.6-p2.7-complete — Foundation + type safety milestone
  • v1.0.11-p0-p1.4-complete — Foundation milestone (P0 publish safety, P1.4 core module, P1.5 docs consolidation)

Type Safety Invariant: Only allowed any in repo: TS mixin constructor pattern (src/utils/PlatformServiceMixin.ts:258), documented inline. All external boundaries use unknown, all data payloads use Record<string, unknown>.

Reference in New Issue View Git Blame Copy Permalink