feat: establish LifeOS MSA foundation

[seonghobae]

Summary

Establishes the first implementation slice for LifeOS as a public, multi-user, domain-oriented microservice platform.

Included

• pnpm + Turborepo monorepo
• Next.js responsive Today dashboard shell
• NestJS API gateway with health and Today composition endpoints
• Identity, Planning, Habit, and Review service skeletons
• shared request, problem-details, and domain-event contracts
• PostgreSQL and NATS JetStream local infrastructure
• Google/GitHub OAuth environment contract
• CI for formatting, linting, type checking, tests, builds, Compose validation, and security scanning
• product architecture and implementation-plan documentation

Architectural decisions

• Goals, projects, milestones, and tasks remain in one Planning bounded context for the MVP.
• Services own persistence boundaries and communicate through versioned events.
• Public fixtures are synthetic; no personal todo or health data is committed.

Validation

• CI: passed
• SAST Semgrep: passed
• Security Scan: passed
• GitHub Advanced Security findings were fixed and threads resolved

Merged after required checks and review verification.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ff9b6cb8-77af-4d85-9b10-ef71569a3023

📥 Commits

Reviewing files that changed from the base of the PR and between 2745f10 and 5d48596.

📒 Files selected for processing (35)

• .env.example
• .github/workflows/ci.yml
• .gitignore
• README.md
• apps/gateway/package.json
• apps/gateway/src/app.module.ts
• apps/gateway/src/main.ts
• apps/gateway/tsconfig.json
• apps/habit-service/package.json
• apps/habit-service/src/main.ts
• apps/habit-service/tsconfig.json
• apps/identity-service/package.json
• apps/identity-service/src/main.ts
• apps/identity-service/tsconfig.json
• apps/planning-service/package.json
• apps/planning-service/src/main.ts
• apps/planning-service/tsconfig.json
• apps/review-service/package.json
• apps/review-service/src/main.ts
• apps/review-service/tsconfig.json
• apps/web/app/layout.tsx
• apps/web/app/page.tsx
• apps/web/app/styles.css
• apps/web/next-env.d.ts
• apps/web/package.json
• apps/web/tsconfig.json
• compose.yaml
• docs/superpowers/plans/2026-08-02-life-os-foundation.md
• package.json
• packages/contracts/package.json
• packages/contracts/src/index.ts
• packages/contracts/tsconfig.json
• pnpm-workspace.yaml
• tsconfig.base.json
• turbo.json

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.