diff --git a/docs/CURRENT_SPRINT_ISSUES.md b/docs/CURRENT_SPRINT_ISSUES.md
new file mode 100644
index 0000000..dac4633
--- /dev/null
+++ b/docs/CURRENT_SPRINT_ISSUES.md
@@ -0,0 +1,279 @@
+# Current Sprint Issues Ongoing with `teacher-workspace-pg` Migration
+The following issues are to be considered alongside the migration of the commits in `teacher-workspace-pg`, to ensure minimal merge conflict and dependencies.
+
+Issues here are grouped by status: Issues in Review, Issues in Progress, Issues Ready to be Taken Up, and Open Pull Requests (N)
+
+Updated as of: 5/21/2026 4.03PM
+
+# ISSUES IN REVIEW
+
+# [#132](https://github.com/String-sg/teacher-workspace/issues/132) Request logging middleware (method, URL, status, duration)
+
+## Overview
+
+Implement a middleware in the Go backend that logs every request with: HTTP method, URL path, response status code, and total request duration. Logs are structured JSON in production.
+
+## Business value
+
+- Provides visibility into platform usage and errors. Without request logging, diagnosing production issues (slow responses, unexpected errors, failed requests) requires guesswork.
+- Enables operational monitoring — teams can track error rates, latency trends, and usage patterns from logs.
+
+## Engineering value
+
+- Structured JSON logs integrate cleanly with log aggregation and monitoring tools.
+- Middleware approach ensures consistent logging across all routes without handler-level boilerplate.
+- Straightforward to implement — method, URL, status, and duration are all available in Go middleware without needing to parse the request body.
+
+## Deferral tradeoff
+
+- Could technically be deferred, but debugging production issues without request logs is painful and time-consuming. The effort to implement is low relative to the value it provides from day one.
+
+# [#175](https://github.com/String-sg/teacher-workspace/issues/175) Add production session Store backed by Valkey
+
+## Overview
+
+Implement a `valkeystore` that satisfies the session `Store` contract using Valkey as the backing store. Intended for production deployments where session state must outlive a single process.
+
+## Goals
+
+- `valkeystore` implementation of the session `Store` contract backed by Valkey
+
+# ISSUES IN PROGRESS
+
+# [#40](https://github.com/String-sg/teacher-workspace/issues/40) Stateful session management
+
+## Overview
+
+Implement stateful session management using Valkey. The middleware must handle session creation on login, session validation on every incoming request, and session destruction on logout.
+
+## Goals
+
+- Typed session abstraction with in-memory store
+- Production session `Store` backed by Valkey
+- Session middleware
+
+# [#140](https://github.com/String-sg/teacher-workspace/issues/140) Migrate from Flow to Shadcn + BaseUI
+
+## Overview
+
+Replace the current internal organisation design system, Flow, with [Shadcn](https://ui.shadcn.com/) + [BaseUI](https://base-ui.com/). Migrate all existing components built on Flow to their Shadcn + BaseUI equivalents, align the theme tokens with UX (converting Flow's design tokens to the Shadcn convention), and set up the new design system as the foundation for all TW frontend work.
+
+## Existing components to migrate
+
+- Buttons
+- Dropdown
+- Menu
+- Sidebar (mainly theme changes — sidebar was built in-house, may not need to be replaced)
+- Card
+- Tooltip
+
+## Engineering rationale for moving away from Flow
+
+- **Central ownership creates a delivery bottleneck.** Component fixes, adjustments, or additions go through the Flow team's backlog, build pipeline, and release process. A change that might take a TW engineer an hour can take days or weeks. The Flow team's position is that maintenance should be shared across consumers, but this assumes every team has engineers with bandwidth to work within Flow's internals (build system, token pipeline, slot-based styling, release process). The TW team does not have this bandwidth.
+
+- **Customising components is disproportionately expensive.** Flow's styling system has multiple internal layers. For example, changing a button's hover colour requires knowing which "slot" the hover style lives in (a button has four: root, icon, content, spinner), writing a nested override object that targets the right slot for the right variant at the right state, and understanding whether the override will win against the built-in style via Flow's custom class-merging system. In Shadcn, the same change is: open the button file, change the class, done. TW's product has its own theme with custom colours selected by UX, meaning colour overrides are needed on almost every component — this is the default workflow, not a one-off cost.
+
+- **Custom token vocabulary conflicts with industry-standard Tailwind.** Flow resets Tailwind's entire default theme (`--color-*: initial`, `--spacing-*: initial`, `--font-*: initial`) and replaces it with its own token vocabulary. Standard classes like `text-red-500`, `p-4`, `text-lg` stop working. Engineers must learn Flow-specific equivalents (`p-md` instead of `p-4`, `bg-btn-fill-brand-enabled` instead of `bg-blue-600`). Flow's no-reset option keeps Tailwind defaults alongside Flow tokens, but then both systems are active simultaneously with no guidance on which to use, leading to inconsistent code reviews and codebase drift. Shadcn uses one system: standard Tailwind extended with a small set of semantic CSS variables (`--primary`, `--secondary`, `--destructive`).
+
+- **End-to-end ownership.** As the main team working on the teacher vertical, TW should own the entire design system end to end rather than depending on an external team's roadmap.
+
+## Theme alignment with UX
+
+The current design tokens (colours, typography, spacing) follow Flow's convention. As part of this migration, the team will work with UX to convert these tokens into the Shadcn convention. This is a one-time, bounded collaboration — once the tokens are converted and set up, the work is complete.
+
+## Business value
+
+- Faster iteration on UI changes — engineers can fix or customise components in hours instead of waiting days or weeks for the Flow team.
+- The TW team gains full control over the design system, removing an external dependency that has historically slowed delivery.
+- A clean, single design token system reduces engineer confusion and code review friction, leading to faster development overall.
+
+## Engineering value
+
+- Eliminates the cost of navigating Flow's slot-based styling and custom class-merging system for every customisation.
+- Standard Tailwind knowledge transfers directly — no need to learn or maintain Flow-specific token vocabulary.
+- Shadcn's "copy the code into your repo" model means all component code lives in TW, accessible to every engineer with no external dependency.
+- Removes the need to coordinate with the Flow team for component changes, reducing cross-team friction.
+
+## Deferral tradeoff
+
+- Could technically be deferred past WPS launch by continuing to use Flow for the initial launch UI. However:
+  - Every customisation built on Flow before migration is throwaway work — it will need to be rebuilt against Shadcn + BaseUI later.
+  - The migration cost grows with every new component built on Flow.
+  - Ongoing UI work during the launch crunch will be slower with Flow's customisation overhead than with Shadcn.
+  - Deferring also delays UX collaboration on the token conversion, which is a prerequisite for the migration.
+  - Doing this before the bulk of UI work begins minimises rework and unblocks faster iteration during launch.
+
+# [#126](https://github.com/String-sg/teacher-workspace/issues/126) Recreate Email OTP flow to TW repository
+
+## Overview
+
+Code and logic for the Email OTP flow exist in a separate repository. This task involves pulling the backend logic and UI into the main TW repository with minimal refactoring.
+
+## Business value
+
+- Email OTP is the alternative sign-in method for teachers. While all teachers will have Edupass accounts, OTP provides a fallback when Edupass is unavailable or when teachers encounter issues with their Edupass credentials.
+- Consolidating into the TW repository ensures the sign-in experience is consistent and maintained in one place.
+
+## Engineering value
+
+- Eliminates cross-repository dependencies for a critical auth flow.
+- Simplifies deployment — OTP flow ships as part of the single TW build artifact.
+- Enables shared tooling, linting, and CI/CD coverage from day one.
+
+## Deferral tradeoff
+
+- Cannot be deferred. OTP is a required fallback login method for WPS launch. Without it, there is no alternative sign-in path if teachers encounter issues with Edupass.
+
+# [#171](https://github.com/String-sg/teacher-workspace/issues/171) Create access whitelisting and master app code tables
+
+## Overview
+
+Create the access whitelisting table and the master `app_code` table via Atlas migration.
+
+## Goals
+
+- Atlas migration creating both tables
+- Access whitelisting table:
+  - Columns: `app_code`, `school_code`, `created_at`, `updated_at`
+  - Composite unique on (`app_code`, `school_code`)
+- Master `app_code` table (name and columns TBD during sprint planning)
+
+## Open questions for sprint planning
+
+- Names for both tables
+- Columns for the master `app_code` table
+
+# [#176](https://github.com/String-sg/teacher-workspace/issues/176) Session middleware
+
+## Overview
+
+HTTP middleware that wires the session `Store` into the request pipeline: creates sessions on login, validates sessions on every request, and destroys sessions on logout.
+
+## Goals
+
+- Session creation on login
+- Session validation on incoming requests
+- Session destruction on logout
+
+# Issues Ready to Be Taken Up
+
+# [#131](https://github.com/String-sg/teacher-workspace/issues/131) Data Loading Foundations
+
+## Overview
+
+Build a production-quality proof of the full data loading flow described in [RFC 27 — Frontend Architecture](https://github.com/transformteamsg/design-documents/issues/27) and [RFC 28 — Backend Architecture](https://github.com/transformteamsg/design-documents/issues/28).
+
+1. **Frontend — Initial load hydration:** Server-provided bootstrap data injected via a JSON script tag (`<script id="preloaded-data" type="application/json">`) is consumed by React Router loaders on initial page load, avoiding extra network requests.
+2. **Frontend — Client-side navigation:** On client-side navigation, React Router loaders fetch route-specific `.json` endpoints from the TW backend.
+3. **Backend — Downstream proxying:** The Go TW backend receives a page request, mints a short-lived JWT with user identity, and proxies the request to the appropriate downstream app service based on the route's base path, following the API contract.
+4. **Mock downstream service:** A mock app backend service that conforms to the TW API contract, used to validate the full end-to-end flow. This mock service will be retained as an integration testing target for the TW backend.
+5. **Developer ergonomics:** Validate what it is like for an app team to build a service against the API contract defined by the TW platform team. The experience of building the mock service serves as a proxy for the real onboarding experience.
+
+## Business value
+
+- Provides app teams with a working reference implementation of the TW integration pattern, giving them confidence in the platform's data loading model and reducing ambiguity when building their services.
+- Validates that the platform can deliver the seamless, fast page transitions promised to users — initial loads are instant (no loading spinners for data the server already has), and navigation between pages feels like a native app.
+- Confirms that the multi-app architecture works end-to-end: TW backend can proxy to independently-owned services, meaning app teams can build and own their backends without being bottlenecked by the platform team.
+
+## Engineering value
+
+- Produces production-quality code: the proxy layer, React Router loader integration, and bootstrap data injection become the foundations all future development builds on.
+- The mock downstream service doubles as a permanent integration test target for the TW backend, improving CI reliability.
+- Validates developer ergonomics early — if the API contract is awkward or the onboarding experience is painful, it is far cheaper to adjust the contract now than after multiple teams have built against it.
+- Exercises the full stack (React Router loaders, Go HTTP proxying, JWT minting, downstream service contract) in a single coherent experiment, exposing integration issues that isolated testing would miss.
+
+## Deferral tradeoff
+
+- Deferring this means teams start building on an unvalidated architecture. If the approach has issues (e.g., React Router loaders do not work as expected with the bootstrap pattern, or the proxy layer introduces unexpected latency), the cost of rework scales with every feature built on top.
+- The API contract between TW backend and downstream services is a multiplier — every team depends on it. Getting it wrong early and correcting late affects all teams simultaneously.
+- If deferred past WPS launch, the September release would need an alternative (and likely ad-hoc) data loading approach, which would then need to be migrated to the validated architecture — double the work.
+
+# [#74](https://github.com/String-sg/teacher-workspace/issues/74) Setup DEV environment
+
+## Overview
+
+Establish the DEV environment for the application server: implement and containerise the server, provision AWS infrastructure via Terragrunt, set up the CI image pipeline, and align on a deployment strategy.
+
+Work is tracked through the sub-issues below.
+
+# [#76](https://github.com/String-sg/teacher-workspace/issues/76) Containerise the Application Server using Docker
+## Overview
+Set up Docker containerisation for the application server to ensure consistent and portable deployments across environments.
+
+## Goals
+- Produce a working `Dockerfile` that successfully builds a Docker image for the application server
+- Ensure the containerised application runs correctly and serves expected responses
+- Establish a consistent and reproducible environment for the application across all deployment targets
+
+# [#168](https://github.com/String-sg/teacher-workspace/issues/168) Provision DEV infrastructure: ECR, ECS, Valkey 
+## Overview
+
+Provision the AWS infrastructure for the DEV environment using Terragrunt, including ECR, ECS and Valkey.
+
+## Goals
+
+- AWS ECR
+  - Create ECR repository `transform/teacher-workspace`
+  - Configure repository access for CI pipeline and ECS
+
+- AWS ECS
+  - ECS cluster (if not existing)
+  - ECS task definition referencing ECR image
+  - ECS service to run the application
+
+- AWS Valkey
+  - Provision Valkey instance for DEV environment
+  - Ensure ECS service can connect to Valkey
+
+- Logging
+  - Configure ECS logging via CloudWatch Logs
+
+# [#170](https://github.com/String-sg/teacher-workspace/issues/170) Discussion: DEV deployment strategy
+
+## Overview
+
+Define and align on the deployment approach for the DEV environment so deployments are reliable and repeatable.
+
+## Goals
+
+- Image tagging strategy
+- Whether deployments are triggered automatically via GitHub Actions to GitLab, or manually triggered from GitLab
+- Rollback strategy
+- Deployment safety considerations
+
+# [#136](https://github.com/String-sg/teacher-workspace/issues/136) Schema design for access whitelisting
+
+## Overview
+
+Define the table(s) and supporting code for **access whitelisting** so we can control which teachers (by school) can access TW and/or specific onboarded apps, even when they can authenticate via OTP or Edupass.
+
+User records are deferred until we have a concrete use case for them.
+
+The whitelisting requirement serves two purposes:
+
+- **Piloting:** Before and around launch, restrict TW access to a pilot set of schools. This is effectively platform-level gating.
+- **App-level control:** Allow specific onboarded apps to restrict access to certain schools.
+
+A single app-level whitelisting model can also serve the platform-level piloting need: if a school is not whitelisted on any app, it effectively has no access to TW.
+
+## Goals
+
+- Access whitelisting table
+- Middleware that gates each request based on the whitelisting table
+- Frontend that hides apps the user cannot access from the sidebar
+
+# Open PRs
+- [feat(db): add Atlas declarative schema, Postgres 18, and sqlc queries](https://github.com/String-sg/teacher-workspace/pull/157)
+- [feat(valkeystore): add Valkey-backed Store](https://github.com/String-sg/teacher-workspace/pull/180)
+- [feat(otp): replace inline OTPaaS calls with provider abstraction](https://github.com/String-sg/teacher-workspace/pull/181)
+- [refactor(web): replace Flow DS with shadcn Base UI](https://github.com/String-sg/teacher-workspace/pull/182)
+- [feat(config): add config tests](https://github.com/String-sg/teacher-workspace/pull/183)
+
+
+
+
+
+
+
+
+
diff --git a/docs/FORK_MIGRATION.md b/docs/FORK_MIGRATION.md
new file mode 100644
index 0000000..3fede24
--- /dev/null
+++ b/docs/FORK_MIGRATION.md
@@ -0,0 +1,347 @@
+# Fork Migration Reference
+
+**Source:** `teacher-workspace-pg` (fork) — 381 commits  
+**Target:** `teacher-workspace` (this repo) — 63 commits  
+**Fork diverged at:** initial commit ("Let there be code!")  
+**Last updated:** 2026-05-21
+
+The fork is a mature, feature-complete implementation. This repo is the review-gated migration target. Work lands here incrementally, in dependency order, via PRs with full review.
+
+---
+
+## Active Sprint Work: PR to Issue Map
+
+These are the open PRs as of 2026-05-21 and which sprint issues they address. Migration PRs must be aware of these to avoid conflicts.
+
+| PR | Title | Branch | Issue | Migration overlap |
+|----|-------|--------|-------|-------------------|
+| [#157](https://github.com/String-sg/teacher-workspace/pull/157) | `feat(db): add Atlas declarative schema, Postgres 18, and sqlc queries` | `feat/135-decide-on-tooling-stack-pgx-sqlc-migration-tool` | #171 (access whitelisting tables) | Low — adds `docker-compose.yaml` (Postgres); fork adds `docker-compose.yml` (MySQL/PGW). Different files, different purposes, but need naming clarity when Layer 1 lands. Also touches `go.mod`, `.env.example`, `Makefile`. |
+| [#180](https://github.com/String-sg/teacher-workspace/pull/180) | `feat(valkeystore): add Valkey-backed Store` | `feat/session-valkeystore` | #175 (Valkey session store) | None — touches only `server/internal/session/`. Fork does not touch this package. |
+| [#181](https://github.com/String-sg/teacher-workspace/pull/181) | `feat(otp): replace inline OTPaaS calls with provider abstraction` | `feat/botp-provider` | #126 (Email OTP flow) | **High** — touches `server/cmd/tw/main.go`, `server/internal/config/config.go`, `server/internal/handler/handler.go`. Layer 2 (PG BFF) must register PG routes in these same files. Layer 2 migration branch must be rebased on top of this PR after it merges. |
+| [#182](https://github.com/String-sg/teacher-workspace/pull/182) | `refactor(web): replace Flow DS with shadcn Base UI` | `refactor/140-flow-ds-to-shadcn` | #140 (Flow → Shadcn migration) | **Critical** — directly covers the majority of Layer 1 (config) and all of Layer 4 (shadcn UI primitives). Adds `components.json`, shadcn packages in `package.json`, `web/components/ui/`, `web/lib/utils.ts`. Do not open Layer 1 or Layer 4 migration PRs until this merges. After it merges, diff against fork to identify only what is still missing. |
+| [#183](https://github.com/String-sg/teacher-workspace/pull/183) | `feat(config): add config tests` | `feat/add-config-tests` | (standalone) | None — adds `server/internal/config/config_test.go` only. |
+
+---
+
+## Migration Status
+
+| # | Area | Status | Notes |
+|---|------|--------|-------|
+| 1 | Tooling & config foundation | `[ ] blocked` | Partially covered by PR #182 (shadcn config, package.json). Also blocked on PR #157 (docker-compose naming). Wait for both to merge, then diff against fork for delta only. |
+| 2 | Go: PG BFF layer | `[ ] blocked` | Blocked on PR #181 merging first. Rebase Layer 2 branch on top of #181 to avoid conflicts in `main.go`, `config.go`, `handler.go`. |
+| 3 | Web: API client layer | `[ ] pending` | No active sprint conflicts. Can be drafted now. |
+| 4 | Web: shadcn UI primitives | `[ ] blocked` | Covered by PR #182. Wait for it to merge, then diff `web/components/ui/` against fork to find any missing components. |
+| 5 | Web: Posts module | `[ ] pending` | depends on 2, 3, 4 |
+| 6 | Web: Groups module | `[ ] pending` | depends on 2, 3, 4 |
+| 7 | Web: Shared comms selectors | `[ ] pending` | depends on 3, 4 |
+| 8 | Documentation & planning docs | `[ ] pending` | can land anytime |
+
+---
+
+## What Changed: Summary
+
+The fork adds two major product features — **Posts/Announcements** and **Custom Groups** — on top of a PG (Parent Guardian) backend integration. Underneath those features sit several foundational layers that must land first.
+
+**Scale:**
+- Original: ~78 tracked files, minimal scaffold
+- Fork: ~345 tracked files, fully-featured app
+- New npm packages: 17 production + 6 dev
+- New fixture files: 48 JSON mocks for PGW API
+- New views: 17+ containers (from 3 to 20+)
+
+---
+
+## Layer 1 — Tooling & Config Foundation
+
+**Status: blocked — wait for PR #182 and PR #157 to merge first.**
+
+PR #182 (`refactor/140-flow-ds-to-shadcn`) is landing `components.json`, the shadcn-related `package.json` additions, and `web/lib/utils.ts` as part of sprint work. PR #157 is landing `docker-compose.yaml` for Postgres. After both merge, open a single migration PR for the remaining delta only (items not already in main).
+
+When adding the fork's `docker-compose.yml` (MySQL for PGW mock dev), name it explicitly — `docker-compose.pgw.yml` or similar — to distinguish it from the Postgres `docker-compose.yaml` already added by PR #157. Do not name it `docker-compose.yml` without first confirming with the team that the naming won't cause confusion.
+
+### Root config files added in fork
+| File | Sprint overlap | Notes |
+|------|---------------|-------|
+| `vitest.config.ts` | None | Add as-is |
+| `components.json` | **Covered by PR #182** | Skip — will be in main after #182 merges; diff if fork version differs |
+| `docker-compose.yml` | **Conflicts with PR #157** | Rename to `docker-compose.pgw.yml` to avoid collision with Postgres compose |
+| `docker/` | None | MySQL config for PGW local dev — add with renamed compose |
+| `.mcp.json` | None | Add as-is |
+| `TODOS.md` | None | Add as-is |
+| `DESIGN.md` | None | Add as-is |
+| `.planning/codebase/` | None | Add as-is |
+
+### package.json changes
+
+PR #182 is already adding the shadcn-related packages (`@base-ui/react`, `@radix-ui/colors`, `class-variance-authority`, `clsx`, `tailwind-merge`, `lucide-react`, `tw-animate-css`). After it merges, only add what is still missing.
+
+New dev scripts (not in sprint PRs — safe to add):
+```json
+"test": "vitest run",
+"test:watch": "vitest",
+"golint": "golangci-lint run"
+```
+
+Removed script (coordinate with team — sprint CONTRIBUTING.md still references `air`):
+```json
+"dev:all": "concurrently -k -n server,web -c blue,green \"go tool air\" \"vite\""
+```
+The fork dropped `air` in favour of a simpler `go run` workflow and removed the `go.mod` tool directive. Confirm the team is aligned before removing this from main.
+
+### New production npm packages
+| Package | Sprint overlap | Notes |
+|---------|---------------|-------|
+| `@tiptap/react` + 6 extensions | None | Add with Posts module (Layer 5) |
+| `@base-ui/react` | **Covered by PR #182** | Skip if already in main after #182 merges |
+| `@radix-ui/colors` | **Covered by PR #182** | Skip if already in main |
+| `class-variance-authority` | **Covered by PR #182** | Skip if already in main |
+| `clsx` + `tailwind-merge` | **Covered by PR #182** | Skip if already in main |
+| `lucide-react` | **Covered by PR #182** | Skip if already in main |
+| `react-day-picker` | None | Add with Posts module (Layer 5) |
+| `sonner` | None | Add with Layer 4 / lib utilities |
+| `tw-animate-css` | **Covered by PR #182** | Skip if already in main |
+| `xlsx` | None | Add with Groups module (Layer 6) |
+
+### New dev npm packages (safe to add, no sprint overlap)
+| Package | Purpose |
+|---------|---------|
+| `vitest` + `@vitest/ui` | Test runner |
+| `@testing-library/react` | Component test utilities |
+| `@testing-library/user-event` | User interaction simulation |
+| `@testing-library/jest-dom` | DOM assertion matchers |
+| `jsdom` | DOM environment for tests |
+
+### pnpm override added
+```json
+"pnpm": { "overrides": { "@tiptap/pm": "3.22.3" } }
+```
+
+### Web test setup
+- `web/test/setup.ts` — jsdom + jest-dom initialisation for Vitest
+
+---
+
+## Layer 2 — Go: PG BFF Layer
+
+**Status: blocked — wait for PR #181 to merge first.**
+
+PR #181 (`feat/botp-provider`) modifies `server/cmd/tw/main.go`, `server/internal/config/config.go`, and `server/internal/handler/handler.go` to add the OTP provider abstraction. The PG BFF layer must register its routes and config in these same files. Create the Layer 2 branch from main only after PR #181 merges, then apply the PG registration on top of the OTP changes.
+
+The fork adds a full Backend for Frontend proxy/mock for the PG (Parent Guardian) API.
+
+**New package:** `server/internal/pg/`
+
+| File | Purpose |
+|------|---------|
+| `handler.go` | HTTP route handlers for all PG endpoints |
+| `proxy.go` | Reverse-proxy to real PGW (`TW_PG_MOCK=false`) |
+| `mock.go` | Mock BFF that serves fixtures (`TW_PG_MOCK=true`) |
+| `identity.go` | User identity / session handling |
+| `mock_files_test.go` | Fixture loading tests |
+
+**Fixtures** (`server/internal/pg/fixtures/` — 48 JSON files):
+- Announcements: draft, scheduled, shared, detail variants (yes/no response)
+- Consent forms: draft, scheduled, closed, detail variants
+- Custom groups: assigned, custom, detail
+- Students / staff / groups (school-level)
+- Meeting bookings, timeslots, details
+- Message groups, notification preferences
+- Feature flags, session, user data
+- HeyTalia conversations and email recipients
+
+**Removed package:** `server/pkg/random/` (base58/base62 generator — no longer needed)
+
+**New env vars** (all prefixed `TW_`):
+```
+TW_PG_MOCK=true|false
+TW_PG_BASE_URL=https://pg.moe.edu.sg
+TW_PG_TIMEOUT_MS=10000
+TW_OTPAAS_HOST=...   # required only when TW_PG_MOCK=false
+TW_OTPAAS_ID=...
+TW_OTPAAS_NAMESPACE=...
+TW_OTPAAS_SECRET=...
+TW_OTPAAS_TIMEOUT=10s
+```
+
+---
+
+## Layer 3 — Web: API Client Layer
+
+**New directory:** `web/api/`
+
+| File | Purpose |
+|------|---------|
+| `client.ts` | HTTP client + `mutateApi` wrapper with CSRF retry logic |
+| `client.test.ts` | Client unit tests |
+| `types.ts` | Request/response type definitions |
+| `mappers.ts` | PG API response → internal type mappers |
+| `mappers.test.ts` | Mapper unit tests |
+| `errors.ts` | Typed error classes (validation, redirect, timeout) |
+
+This layer is a dependency of every feature view. It must land before Posts or Groups.
+
+---
+
+## Layer 4 — Web: Shadcn UI Primitives
+
+**Status: blocked — wait for PR #182 to merge first.**
+
+PR #182 (`refactor/140-flow-ds-to-shadcn`) is the team's own shadcn migration. It adds `web/components/ui/`, `web/lib/utils.ts`, `components.json`, and the shadcn-related packages. This is the same work Layer 4 was planning to do. After PR #182 merges:
+
+1. Compare `web/components/ui/` in main against the fork. The fork has these components that the sprint PR may not include: `Calendar`, `Collapsible`, `Progress`, `RadioGroup`, `Sheet` — verify each after #182 merges.
+2. Check `web/lib/` — fork adds `notify.ts` (Sonner wrapper) and `validation-errors.ts`. These are unlikely to be in the sprint PR and still need to land.
+3. Layer 4 migration PR should be a small delta PR adding only what is missing after #182 merges, not a full re-add of all shadcn components.
+
+**New directory:** `web/components/ui/`
+
+20+ headless component wrappers built on Radix primitives via shadcn. They apply project-specific defaults (pill radius, font-weight). Feature components import these, never `@flow/core` directly.
+
+Components:
+`Badge`, `Button`, `Calendar`, `Card`, `Checkbox`, `Collapsible`, `Dialog`, `DropdownMenu`, `Input`, `Label`, `Popover`, `Progress`, `RadioGroup`, `Select`, `Separator`, `Sheet`, `Switch`, `Table`, `Tabs`, `Textarea`, `Tooltip`
+
+**New utility files:**
+- `web/lib/utils.ts` — `cn()` helper (clsx + tailwind-merge) — **covered by PR #182**
+- `web/lib/notify.ts` — Sonner toast wrapper — not in sprint PR, add in Layer 4 delta
+- `web/lib/validation-errors.ts` — Validation error mapping/formatting — not in sprint PR, add in Layer 4 delta
+
+Must land before Posts or Groups (both import from `~/components/ui` and `~/lib`).
+
+---
+
+## Layer 5 — Web: Posts Module
+
+**New directories:**
+- `web/components/posts/` — 24+ components
+- `web/data/` — Mock data and post registry
+- `web/containers/PostsView/`, `CreatePostView/`, `PostDetailView/`
+
+### Key components
+| Component | Purpose |
+|-----------|---------|
+| `RichTextEditor` / `RichTextToolbar` | Tiptap-based body editor with PGW allowlist |
+| `RecipientSelector` + `RecipientFilterPopover` | Group/student recipient picker |
+| `SchedulePickerDialog` | Two-column scheduled-send picker (capped to today+21 days, filters past slots when today selected) |
+| `AttachmentSection` | File/photo upload with race-condition handling |
+| `QuestionBuilder` | Consent-form question authoring |
+| `PostPreview` | Parent-view preview of post |
+| `PostCard` / `PostFilterPopover` | List view with Status/Response/Date filters + Mine/Shared tabs |
+| `SendConfirmationDialog` | Pre-send confirmation |
+| `SplitPostButton` | Save-as-draft vs send split button |
+| `ReadTrackingCards` / `ReadRate` | Response/read-rate analytics |
+| `DraftManager` | Autosave + dirty-state tracking |
+
+### Consent form specifics
+- Payload field: `startDateTime` vs `eventStartDate` — fork aligns to real PGW shape
+- Event dates sent as `{date, time}` object (not flat strings)
+- Detail response unwraps a `[detail]` array (real PGW quirk)
+- Drafts route through dedicated endpoints; bare-array post-list responses handled
+
+### Bug fixes baked in
+- Validation error mapping from PG → form fields
+- Required-field asterisks
+- Duplicate-draft numeric ID vs NaN guard
+- Scheduled-send failure UX (badges, detail banners)
+- `@tiptap/starter-kit` link/underline disabled to silence extension warnings
+
+---
+
+## Layer 6 — Web: Groups Module
+
+**New directories:**
+- `web/components/groups/` — 15 components
+- `web/containers/GroupsView/`, `CreateCustomGroupView/`, `AddStudentsView/`, `CustomGroupDetailView/`, `EditCustomGroupView/`
+
+### Key components
+| Component | Purpose |
+|-----------|---------|
+| `CustomGroupsTable` | Empty + populated states |
+| `AssignedGroupsSection` | Card grid of assigned groups |
+| `CreateCustomGroupView` | Title input with 120-char counter |
+| `AddStudentsView` | Filter/select students (`StudentFilterBar`, `StudentResultsTable`) |
+| `StudentsByClassList` | Index + CCA columns for edit flow |
+| `ShareGroupModal` | Staff picker + permissions list |
+| `DeleteGroupModal` | Confirmation checkbox |
+| `ExcelUploadPanel` | Bulk-upload students via Excel |
+
+### Excel upload utilities
+- `web/components/groups/excel-upload-validation.ts`
+- `web/components/groups/parse-excel-file.ts`
+- `web/components/groups/validate-upload-students.ts`
+
+### PGW integration notes
+- `groupName` + `selectedSchoolStudents` in create/update payloads
+- Detail response unwraps array (same quirk as consent form)
+- `staffIds` field name (not `staffId`) in shareCustomGroup
+- UIN/FIN masked in `StudentResultsTable` for PII compliance
+- Pre-selects existing students in edit flow; pre-selects already-shared staff in ShareGroupModal
+
+---
+
+## Layer 7 — Web: Shared Comms Selectors
+
+**New directory:** `web/components/comms/`
+
+| File | Purpose |
+|------|---------|
+| `entity-selector.tsx` | Generic entity selection primitive |
+| `staff-selector.tsx` | Staff picker (reused by Groups ShareModal and Posts enquiry) |
+| `student-recipient-selector.tsx` | Student recipient selection |
+
+These are consumed by both Posts and Groups, so they belong in a shared location. Land alongside or just before Layer 5/6.
+
+---
+
+## Layer 8 — Documentation & Planning Docs
+
+The fork has ~50 markdown docs. These can be ported at any time and don't block feature PRs.
+
+| Source path | Contents |
+|-------------|---------|
+| `docs/architecture/` | RFC-027 (frontend), RFC-028 (backend), color tokens, sidebar flow shim |
+| `docs/audits/` | PG parity scope audits (PGTW-1-12, PGTW-13-20, PGTW-13-25) |
+| `docs/plans/` | Implementation plans per ticket (PGTW-13a–14, save-as-draft/autosave) |
+| `docs/references/` | PG API contracts, BFF design, context, specs |
+| `docs/setup/` | Local pgw-web integration guide |
+| `.planning/codebase/` | Architecture, concerns, conventions, integrations, stack, structure, testing |
+
+---
+
+## Dependency Order (landing sequence)
+
+Sprint PRs that must merge before migration work can start are shown as gates.
+
+```
+[Sprint PR #182 merges]  ──► Layer 1 delta (remaining config, vitest, docker rename)
+                         ──► Layer 4 delta (missing shadcn components, notify.ts, validation-errors.ts)
+
+[Sprint PR #181 merges]  ──► Layer 2 (Go PG BFF — register on top of OTP changes)
+
+Layer 3  Web API client  ──► no sprint conflicts, draft now
+
+[Layers 1, 2, 3, 4 merged]
+         ──► Layer 7  Shared comms selectors
+         ──► Layer 5  Posts module  (parallel with Layer 6)
+         ──► Layer 6  Groups module (parallel with Layer 5)
+
+Layer 8  Docs            ──► no dependencies, land anytime
+```
+
+**What can be drafted right now (before any sprint PR merges):**
+- Layer 3 (Web API client) — `web/api/` is a new directory with no sprint conflicts
+- Layer 8 (Docs) — pure markdown, no conflicts
+
+**What to draft once PR #182 merges:**
+- Layer 1 delta — compare main against fork, open a PR for remaining items only
+- Layer 4 delta — compare `web/components/ui/` and `web/lib/` against fork, open a PR for missing pieces
+
+**What to draft once PR #181 merges:**
+- Layer 2 — create branch from updated main, apply PG BFF on top of OTP handler changes
+
+---
+
+## Notes on Review Approach
+
+- **Prefer feature branches over snippet issues.** Each layer should become a real branch in this repo that reviewers can diff, not a description with copy-paste snippets.
+- **Foundational layers (1–4) deserve the most scrutiny** — they underpin everything else. A naming or structural decision made here propagates to all feature code.
+- **PGW quirks are load-bearing.** Several fixes in the fork address real PGW API shape oddities (array-unwrapping, field naming, payload structure). These should be captured in tests, not just in code, so the behaviour is visible to reviewers.
+- **PII handling.** `StudentResultsTable` masks UIN/FIN — ensure this is explicitly called out in the Groups PR and verified in review.
diff --git a/docs/fork-migration-issues/_index.md b/docs/fork-migration-issues/_index.md
new file mode 100644
index 0000000..5d70df6
--- /dev/null
+++ b/docs/fork-migration-issues/_index.md
@@ -0,0 +1,43 @@
+# Fork Migration Issues Index
+
+Source of truth for migration layer status and ordering.
+Full layer details: `docs/FORK_MIGRATION.md`.
+Active sprint conflicts: `docs/CURRENT_SPRINT_ISSUES.md`.
+
+Last updated: 2026-05-21
+
+---
+
+## Issues
+
+| ID | File | Title | Status | Blocks on PRs | Blocks on issues |
+|----|------|-------|--------|---------------|-----------------|
+| MIGRATION-01 | [issue-01-tooling-config-delta.md](issue-01-tooling-config-delta.md) | Tooling and config delta | `blocked` | PR #182, PR #157 | — |
+| MIGRATION-02 | [issue-02-go-pg-bff.md](issue-02-go-pg-bff.md) | Go: PG BFF layer | `blocked` | PR #181 | — |
+| MIGRATION-03 | [issue-03-web-api-client.md](issue-03-web-api-client.md) | Web: API client layer | `ready` | — | — |
+| MIGRATION-04 | [issue-04-shadcn-ui-delta.md](issue-04-shadcn-ui-delta.md) | Web: shadcn UI primitives delta | `blocked` | PR #182 | MIGRATION-01 |
+| MIGRATION-05 | [issue-05-posts-module.md](issue-05-posts-module.md) | Web: Posts module | `pending` | — | MIGRATION-02, 03, 04, 07 |
+| MIGRATION-06 | [issue-06-groups-module.md](issue-06-groups-module.md) | Web: Groups module | `pending` | — | MIGRATION-02, 03, 04, 07 |
+| MIGRATION-07 | [issue-07-shared-comms-selectors.md](issue-07-shared-comms-selectors.md) | Web: Shared comms selectors | `pending` | — | MIGRATION-03, 04 |
+| MIGRATION-08 | [issue-08-docs.md](issue-08-docs.md) | Documentation and planning docs | `ready` | — | — |
+
+---
+
+## Landing order
+
+```
+[PR #182 merges] --> MIGRATION-01, MIGRATION-04
+[PR #181 merges] --> MIGRATION-02
+MIGRATION-03     --> (draft now, no blockers)
+MIGRATION-08     --> (draft now, no blockers)
+
+After MIGRATION-01, 02, 03, 04 merged:
+  --> MIGRATION-07
+  --> MIGRATION-05 (parallel with 06)
+  --> MIGRATION-06 (parallel with 05)
+```
+
+## What can be started right now
+
+- **MIGRATION-03** (Web: API client) — no blockers, purely additive new directory
+- **MIGRATION-08** (Docs) — no blockers, markdown only
diff --git a/docs/fork-migration-issues/_template.md b/docs/fork-migration-issues/_template.md
new file mode 100644
index 0000000..d0df35d
--- /dev/null
+++ b/docs/fork-migration-issues/_template.md
@@ -0,0 +1,82 @@
+# Migration Issue Template
+
+This template defines the structure for all fork migration issues in this folder.
+Every issue file must follow this structure exactly so that a coding agent with no prior
+context can pick it up and complete it without back-and-forth.
+
+---
+
+## MIGRATION-XX — [Title]
+
+### Status
+`blocked` | `ready` | `in-progress` | `done`
+
+### Blocking sprint PRs
+List every open sprint PR that must merge into `main` before this issue can start.
+Check `docs/CURRENT_SPRINT_ISSUES.md` for current PR URLs and merge status.
+If none, write: None.
+
+### Prerequisite migration issues
+List every migration issue (by ID) whose PR must be merged into `main` before this
+issue branch can be created. If none, write: None.
+
+### Background
+2-4 sentences explaining what this migration issue is adding and why it exists.
+Reference the relevant layer in `docs/FORK_MIGRATION.md`. Do not assume the reader
+has read that doc.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+All relative file paths in the Steps section are relative to these roots.
+
+### Starting point
+Before creating the branch, verify the following are true in `main`:
+- [ ] All blocking sprint PRs listed above have been merged
+- [ ] All prerequisite migration issues listed above have been merged
+- [ ] `git pull origin main` is clean
+
+Branch off `main` after all the above are confirmed.
+
+---
+
+### Steps
+
+Numbered steps the agent must execute in order. Each step must be atomic and
+verifiable. Prefer explicit commands over vague instructions.
+
+#### Step N — [Step title]
+What to do, including exact commands, file paths, and any modification instructions.
+
+---
+
+### Files to copy verbatim
+Files that can be copied from the fork to the target without modification.
+List as: `<fork-relative-path>` → `<target-relative-path>`
+
+### Files to copy with modifications
+Files that must be copied and then edited. For each file, state what to change and why.
+
+### Files to skip
+Files present in the fork that must NOT be copied. State why.
+
+### New packages
+Exact `pnpm add` commands to run.
+
+---
+
+### Acceptance criteria
+Checkable conditions that confirm the issue is complete.
+- [ ] Criterion 1
+- [ ] Criterion 2
+
+### Branch name
+`chore/migration-XX-[short-description]`
+
+### PR title
+`chore(migration): [short description matching CONTRIBUTING.md conventions]`
+
+### PR summary template
+One paragraph the agent can use as the PR summary section. It should explain what
+the PR adds and reference `docs/FORK_MIGRATION.md` Layer N.
diff --git a/docs/fork-migration-issues/issue-01-tooling-config-delta.md b/docs/fork-migration-issues/issue-01-tooling-config-delta.md
new file mode 100644
index 0000000..37f52d1
--- /dev/null
+++ b/docs/fork-migration-issues/issue-01-tooling-config-delta.md
@@ -0,0 +1,166 @@
+# MIGRATION-01 — Tooling and config delta
+
+### Status
+`blocked`
+
+### Blocking sprint PRs
+- [PR #182](https://github.com/String-sg/teacher-workspace/pull/182) `refactor(web): replace Flow DS with shadcn Base UI` — adds `components.json`, shadcn npm packages, `web/lib/utils.ts`. Must merge before this issue so we only add the delta.
+- [PR #157](https://github.com/String-sg/teacher-workspace/pull/157) `feat(db): add Atlas declarative schema, Postgres 18, and sqlc queries` — adds `docker-compose.yaml` (Postgres). Must merge before this issue so we can name the PGW compose file without collision.
+
+### Prerequisite migration issues
+None.
+
+### Background
+The fork adds test infrastructure (Vitest + React Testing Library), a renamed docker-compose
+file for local PGW development, and several root-level config files that are not present in
+this repo. Much of the shadcn setup (components.json, shadcn npm packages, web/lib/utils.ts)
+is being done by PR #182 as sprint work. This issue adds only what remains after that PR merges.
+See `docs/FORK_MIGRATION.md` Layer 1.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify the following are true in `main`:
+- [ ] PR #182 has been merged
+- [ ] PR #157 has been merged
+- [ ] `git pull origin main` is clean
+
+---
+
+### Steps
+
+#### Step 1 — Check what PR #182 already landed
+Run the following and note what is already present in `main`:
+```
+ls web/lib/
+ls web/components/ui/
+cat components.json
+cat package.json | grep -E "class-variance|clsx|tailwind-merge|lucide|base-ui|radix|tw-animate"
+```
+Do NOT re-add anything already present. The items below marked "skip if present" should
+only be added if they are missing after PR #182.
+
+#### Step 2 — Add Vitest test infrastructure
+Copy the following files verbatim from the fork:
+- `vitest.config.ts` → `vitest.config.ts`
+- `web/test/setup.ts` → `web/test/setup.ts` (create `web/test/` directory if absent)
+
+Add dev dependencies:
+```
+pnpm add -D vitest @vitest/ui @testing-library/react @testing-library/user-event @testing-library/jest-dom jsdom
+```
+
+Add the pnpm override to `package.json` (inside the `"pnpm"` key, create it if absent):
+```json
+"pnpm": {
+  "overrides": {
+    "@tiptap/pm": "3.22.3"
+  }
+}
+```
+
+Add test scripts to `package.json` `"scripts"` section:
+```json
+"test": "vitest run",
+"test:watch": "vitest"
+```
+
+Add lint script (if not already present from sprint work):
+```json
+"golint": "golangci-lint run"
+```
+
+Verify the test runner works before proceeding:
+```
+pnpm test
+```
+There are no test files yet in this repo, so Vitest will report "No test files found" —
+that is expected and passing.
+
+#### Step 3 — Add sonner package (skip if already present)
+`sonner` is the toast notification library used by `web/lib/notify.ts`. Check if it was
+added by PR #182. If not:
+```
+pnpm add sonner
+```
+
+#### Step 4 — Add the PGW docker-compose and MySQL config
+The fork includes a `docker-compose.yml` and `docker/` directory for running a local
+PGW MySQL replica during development. PR #157 already added a `docker-compose.yaml`
+(Postgres) to this repo. To avoid naming confusion, copy the fork's compose file with a
+distinct name:
+
+```
+cp d:\Environment\tw\teacher-workspace-pg\docker-compose.yml docker-compose.pgw.yml
+cp -r d:\Environment\tw\teacher-workspace-pg\docker\ docker\
+```
+
+Open `docker-compose.pgw.yml` and verify it does not conflict with any service names
+already defined in `docker-compose.yaml`. If there are collisions on service names
+(e.g. both define a service called `db`), rename the PGW service to `pgw-db` and update
+any volume references inside the same file accordingly.
+
+#### Step 5 — Copy remaining root config files
+Copy verbatim from fork:
+- `.mcp.json` → `.mcp.json`
+
+The fork also has `DESIGN.md` and `TODOS.md` at the root. These are handled separately
+in MIGRATION-08 (Docs). Skip them here.
+
+#### Step 6 — Remove the `air` dev script (coordinate with team first)
+The fork removed the `dev:all` script and the `go.mod` tool directive for `air` in favour
+of a plain `go run` workflow. Before removing these from this repo, confirm with the team
+that no one is actively using `go tool air` for development. If the team agrees, remove:
+- The `"dev:all"` script from `package.json`
+- The `tool github.com/air-verse/air` line from `go.mod`
+
+If the team is not ready to drop `air`, skip this step and leave a comment in the PR.
+
+---
+
+### Files to copy verbatim
+- `vitest.config.ts` → `vitest.config.ts`
+- `web/test/setup.ts` → `web/test/setup.ts`
+- `.mcp.json` → `.mcp.json`
+- `docker-compose.yml` → `docker-compose.pgw.yml` (rename on copy — see Step 4)
+- `docker/` → `docker/` (entire directory)
+
+### Files to skip
+- `components.json` — covered by PR #182 (check before adding)
+- `DESIGN.md` — handled by MIGRATION-08
+- `TODOS.md` — handled by MIGRATION-08
+- `.planning/` — handled by MIGRATION-08
+- `docker-compose.yml` (original name) — rename to `docker-compose.pgw.yml` to avoid collision
+
+### New packages
+```
+pnpm add sonner
+pnpm add -D vitest @vitest/ui @testing-library/react @testing-library/user-event @testing-library/jest-dom jsdom
+```
+
+---
+
+### Acceptance criteria
+- [ ] `pnpm test` runs and exits 0 (no test files found is acceptable)
+- [ ] `vitest.config.ts` exists at repo root
+- [ ] `web/test/setup.ts` exists
+- [ ] `docker-compose.pgw.yml` exists and does not share service names with `docker-compose.yaml`
+- [ ] `docker/` directory exists with MySQL config copied from fork
+- [ ] `.mcp.json` exists at repo root
+- [ ] `package.json` contains `"test"` and `"test:watch"` scripts
+- [ ] `pnpm install` runs without errors
+
+### Branch name
+`chore/migration-01-tooling-config-delta`
+
+### PR title
+`chore(migration): add Vitest, test setup, PGW docker config, and remaining tooling delta`
+
+### PR summary template
+Adds the tooling and configuration items from the fork (`teacher-workspace-pg`) that were
+not covered by the concurrent sprint work in PR #182 and PR #157. Specifically: Vitest +
+React Testing Library test infrastructure, the `docker-compose.pgw.yml` and `docker/`
+directory for local PGW MySQL development, and `.mcp.json`. See `docs/FORK_MIGRATION.md`
+Layer 1 for the full list of what was and was not included.
diff --git a/docs/fork-migration-issues/issue-02-go-pg-bff.md b/docs/fork-migration-issues/issue-02-go-pg-bff.md
new file mode 100644
index 0000000..1eadb33
--- /dev/null
+++ b/docs/fork-migration-issues/issue-02-go-pg-bff.md
@@ -0,0 +1,241 @@
+# MIGRATION-02 — Go: PG BFF layer
+
+### Status
+`blocked`
+
+### Blocking sprint PRs
+- [PR #181](https://github.com/String-sg/teacher-workspace/pull/181) `feat(otp): replace inline OTPaaS calls with provider abstraction` — modifies `server/cmd/tw/main.go`, `server/internal/config/config.go`, and `server/internal/handler/handler.go`. This issue must be rebased on top of those changes.
+
+### Prerequisite migration issues
+None.
+
+### Background
+The fork adds a complete Backend for Frontend (BFF) proxy layer for the Parents Gateway (PG)
+API under `server/internal/pg/`. In development, it serves 48 JSON fixture files to the
+frontend without requiring a real PGW connection (`TW_PG_MOCK=true`). In production, it
+reverse-proxies requests to a real PGW instance and mints a short-lived JWT for each request.
+This layer is a hard dependency for the Posts (MIGRATION-05) and Groups (MIGRATION-06) modules,
+which both make API calls to `/api/web/2/staff/*` routes served by this package.
+See `docs/FORK_MIGRATION.md` Layer 2.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify:
+- [ ] PR #181 has been merged into `main`
+- [ ] `git pull origin main` is clean
+- [ ] `go build ./...` passes on `main` before you make any changes
+
+---
+
+### Steps
+
+#### Step 1 — Copy the entire `server/internal/pg/` package
+The package is entirely new. Copy it verbatim from the fork:
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\server\internal\pg\ server\internal\pg\
+```
+This copies:
+- `server/internal/pg/handler.go` — `New()`, `Register()` — dispatches to mock or proxy
+- `server/internal/pg/mock.go` — serves JSON fixtures from `fixtures/`
+- `server/internal/pg/proxy.go` — reverse-proxies to real PGW with JWT minting
+- `server/internal/pg/identity.go` — user identity/session helpers
+- `server/internal/pg/mock_files_test.go` — tests that all fixture files load correctly
+- `server/internal/pg/fixtures/` — 48 JSON fixture files (see fixture list below)
+
+Do NOT modify any of these files at this stage. Copy them as-is.
+
+#### Step 2 — Add `PGConfig` to `server/internal/config/config.go`
+PR #181 will have modified `config.go`. Read the current state of that file after the PR
+merges, then apply the following additions:
+
+**Add the `PGConfig` struct** (new type, alongside the existing `ServerConfig` and `OTPaaSConfig`):
+```go
+// PGConfig holds configuration for the Parents Gateway integration.
+type PGConfig struct {
+    Mock      bool   `dotenv:"TW_PG_MOCK"`
+    BaseURL   string `dotenv:"TW_PG_BASE_URL"`
+    TimeoutMS int    `dotenv:"TW_PG_TIMEOUT_MS"`
+}
+```
+
+**Add `PG PGConfig` field to the `Config` struct** (after the `OTPaaS` field):
+```go
+PG PGConfig `dotenv:",squash"`
+```
+
+**Add PG defaults to the `Default()` function** (inside the `return &Config{...}` literal,
+after the `OTPaaS:` block):
+```go
+PG: PGConfig{
+    Mock:      true,
+    BaseURL:   "https://pg.moe.edu.sg",
+    TimeoutMS: 10000,
+},
+```
+
+**Update `Validate()` to only call `cfg.OTPaaS.validate()` when not in mock mode.**
+Find the line in `Validate()` that calls `cfg.OTPaaS.validate()`. In the fork, OTPaaS
+validation is only required when proxying to a real PGW (`!cfg.PG.Mock`). Replace the
+unconditional `cfg.OTPaaS.validate()` call with a conditional:
+
+Before (original pattern, may look slightly different after PR #181):
+```go
+return errors.Join(append(errs, cfg.Server.validate(), cfg.OTPaaS.validate())...)
+```
+
+After:
+```go
+errs = append(errs, cfg.Server.validate())
+if !cfg.PG.Mock {
+    errs = append(errs, cfg.OTPaaS.validate())
+}
+return errors.Join(errs...)
+```
+
+The intent: mock mode (`TW_PG_MOCK=true`) does not contact OTPaaS, so its credentials
+should not be required. This allows developers to run the app locally without OTPaaS creds.
+
+#### Step 3 — Register the PG handler in `server/internal/handler/handler.go`
+PR #181 will have modified `handler.go`. Read the current state after that PR merges, then
+apply the following changes.
+
+**Add the `pg` import:**
+```go
+"github.com/String-sg/teacher-workspace/server/internal/pg"
+```
+
+**In the `Register` method, add `pg.New(&h.cfg.PG).Register(mux)` before the catch-all
+`GET /` route:**
+```go
+func (h *Handler) Register(mux *http.ServeMux) {
+    // ... existing OTP routes from PR #181 ...
+    pg.New(&h.cfg.PG).Register(mux)
+    mux.HandleFunc("GET /", h.Index)
+}
+```
+The PG handler must be registered before `GET /` because `GET /` is a catch-all that
+matches all unmatched routes. PG routes must be registered first or they will never match.
+
+#### Step 4 — Add new env vars to `.env.example`
+Open `.env.example` and add the following block in an appropriate section (after existing
+server config vars):
+```
+# Parents Gateway (PG) integration
+# TW_PG_MOCK=true serves JSON fixtures; set to false to proxy a real PGW instance.
+TW_PG_MOCK=true
+TW_PG_BASE_URL=https://pg.moe.edu.sg
+TW_PG_TIMEOUT_MS=10000
+
+# Required only when TW_PG_MOCK=false.
+TW_OTPAAS_HOST=https://otp.techpass.suite.gov.sg
+TW_OTPAAS_ID=
+TW_OTPAAS_NAMESPACE=
+TW_OTPAAS_SECRET=
+TW_OTPAAS_TIMEOUT=10s
+```
+If `TW_OTPAAS_*` vars are already in `.env.example` from PR #181, do not duplicate them.
+Only add the `TW_PG_*` vars.
+
+#### Step 5 — Remove `server/pkg/random/` (if still present)
+The fork removed this package (base58/base62 generator) as it is no longer needed.
+Check if it still exists in `main` after the sprint PRs merge:
+```
+ls server/pkg/random/
+```
+If it exists and is not imported anywhere, delete it:
+```
+rm -rf server/pkg/random/
+```
+Verify no remaining imports:
+```
+grep -r "pkg/random" server/
+```
+If anything still imports it, do NOT delete it — leave a note in the PR.
+
+#### Step 6 — Build and test
+```
+go build ./...
+go test ./...
+```
+Both must pass with zero errors. The `mock_files_test.go` in the new `pg` package tests
+that every fixture file is valid JSON and can be loaded — this test must pass.
+
+---
+
+### Files to copy verbatim
+- `server/internal/pg/handler.go` → `server/internal/pg/handler.go`
+- `server/internal/pg/mock.go` → `server/internal/pg/mock.go`
+- `server/internal/pg/proxy.go` → `server/internal/pg/proxy.go`
+- `server/internal/pg/identity.go` → `server/internal/pg/identity.go`
+- `server/internal/pg/mock_files_test.go` → `server/internal/pg/mock_files_test.go`
+- `server/internal/pg/fixtures/` → `server/internal/pg/fixtures/` (all 48 JSON files)
+
+### Files to copy with modifications
+None — all changes to existing files are described as targeted edits above.
+
+### Files to skip
+None within the `pg` package.
+
+### Fixture file inventory
+All 48 fixtures must be present after copy. Grouped by category:
+
+**Announcements (9):** `announcement_detail.json`, `announcement_detail_draft.json`,
+`announcement_detail_scheduled.json`, `announcement_detail_shared.json`,
+`announcement_detail_yes_no.json`, `announcement_draft.json`,
+`announcement_draft_scheduled_failed.json`, `announcements.json`, `announcements_shared.json`
+
+**Consent forms (7):** `consent_form_detail.json`, `consent_form_detail_closed.json`,
+`consent_form_detail_draft.json`, `consent_form_detail_scheduled.json`,
+`consent_form_draft.json`, `consent_form_draft_swim_gala.json`, `consent_forms.json`
+
+**Groups (7):** `cca_students.json`, `group_custom_detail.json`, `groups_assigned.json`,
+`groups_custom.json`, `school_groups.json`, `school_student_groups.json`, `school_staff_groups.json`
+
+**Students (2):** `school_students.json`, `validate_students_results.json`
+
+**Classes (1):** `class_detail.json`
+
+**Staff (1):** `school_staff.json`
+
+**Meetings (7):** `meeting_booking.json`, `meeting_bookings.json`, `meeting_detail.json`,
+`meeting_schedule.json`, `meeting_target_students.json`, `meeting_timeslots.json`, `meetings.json`
+
+**HeyTalia (3):** `heytalia_conversation.json`, `heytalia_conversations.json`,
+`heytalia_email_recipients_history.json`
+
+**Config and session (4):** `configs.json`, `feature_flags.json`, `ptm_serverdatetime.json`,
+`session_current.json`
+
+**Notifications and user (3):** `notification_preferences.json`, `users_me.json`,
+`web_notifications.json`
+
+**Messages (1):** `message_groups.json`
+
+---
+
+### Acceptance criteria
+- [ ] `go build ./...` passes
+- [ ] `go test ./...` passes, including `server/internal/pg` package tests
+- [ ] `server/internal/pg/fixtures/` contains all 48 JSON files
+- [ ] `config.Config` has a `PG PGConfig` field
+- [ ] `handler.Register()` calls `pg.New(&h.cfg.PG).Register(mux)` before `GET /`
+- [ ] `.env.example` includes `TW_PG_MOCK`, `TW_PG_BASE_URL`, `TW_PG_TIMEOUT_MS`
+- [ ] OTPaaS config validation is skipped when `TW_PG_MOCK=true`
+- [ ] App starts with `TW_PG_MOCK=true` and no OTPaaS env vars set
+
+### Branch name
+`feat/migration-02-go-pg-bff`
+
+### PR title
+`feat(\`pg\`): add PG BFF proxy and mock layer with fixtures`
+
+### PR summary template
+Adds the `server/internal/pg` package from the fork. In mock mode (`TW_PG_MOCK=true`,
+the default), the BFF serves 48 JSON fixtures to the frontend with no external dependencies.
+In proxy mode, it reverse-proxies to a real PGW instance. Wires `PGConfig` into the config
+struct, registers PG routes in the handler, and conditions OTPaaS credential validation on
+non-mock mode. This is a prerequisite for the Posts (MIGRATION-05) and Groups (MIGRATION-06)
+migration layers. See `docs/FORK_MIGRATION.md` Layer 2.
diff --git a/docs/fork-migration-issues/issue-03-web-api-client.md b/docs/fork-migration-issues/issue-03-web-api-client.md
new file mode 100644
index 0000000..5a22f3b
--- /dev/null
+++ b/docs/fork-migration-issues/issue-03-web-api-client.md
@@ -0,0 +1,116 @@
+# MIGRATION-03 — Web: API client layer
+
+### Status
+`ready`
+
+### Blocking sprint PRs
+None.
+
+### Prerequisite migration issues
+None.
+
+### Background
+The fork introduces a typed API client layer under `web/api/`. It abstracts all HTTP calls
+to the Go BFF, handles PG envelope unwrapping (`{body, resultCode}`), typed error classes,
+CSRF retry logic, timeout composition, and response-to-internal-type mapping. Every feature
+view (Posts, Groups) imports from this layer. It must land before MIGRATION-05, MIGRATION-06,
+and MIGRATION-07. It has no dependency on the shadcn UI or the Go BFF being present in this
+repo — it only makes network calls at runtime.
+See `docs/FORK_MIGRATION.md` Layer 3.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify:
+- [ ] `git pull origin main` is clean
+- [ ] `pnpm install` passes
+
+No sprint PR needs to merge before this issue can start.
+
+---
+
+### Steps
+
+#### Step 1 — Create `web/api/` and copy all files
+The directory does not exist in this repo. Copy the entire directory from the fork:
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\web\api\ web\api\
+```
+
+This copies 6 files:
+- `web/api/client.ts` — all HTTP helpers and every PG API call
+- `web/api/client.test.ts` — unit tests for the HTTP client
+- `web/api/errors.ts` — typed error classes
+- `web/api/mappers.ts` — PG wire DTO → internal type transformations
+- `web/api/mappers.test.ts` — mapper unit tests
+- `web/api/types.ts` — wire DTO TypeScript types (request and response shapes)
+
+Do NOT modify any of these files.
+
+#### Step 2 — Verify TypeScript compiles
+```
+pnpm exec tsc --noEmit
+```
+The files import from `~/lib/utils` and `~/lib/validation-errors` via the `~` alias.
+Those files do not exist yet (they land in MIGRATION-04). TypeScript will report errors
+for those missing imports.
+
+This is expected and acceptable at this stage. The PR description must note that TypeScript
+errors from missing `~/lib/*` imports will be resolved when MIGRATION-04 merges.
+
+If there are TypeScript errors OTHER than missing `~/lib/` imports, investigate and resolve
+them before raising the PR.
+
+#### Step 3 — Run existing tests
+```
+pnpm test
+```
+The `client.test.ts` and `mappers.test.ts` files may have import errors for the same missing
+`~/lib/*` modules. If Vitest fails to parse them, exclude those test files in `vitest.config.ts`
+temporarily by adding an `exclude` pattern, or note in the PR that tests will be fully
+runnable after MIGRATION-04 merges.
+
+Do not modify the test files themselves.
+
+---
+
+### Files to copy verbatim
+- `web/api/client.ts` → `web/api/client.ts`
+- `web/api/client.test.ts` → `web/api/client.test.ts`
+- `web/api/errors.ts` → `web/api/errors.ts`
+- `web/api/mappers.ts` → `web/api/mappers.ts`
+- `web/api/mappers.test.ts` → `web/api/mappers.test.ts`
+- `web/api/types.ts` → `web/api/types.ts`
+
+### Files to copy with modifications
+None.
+
+### Files to skip
+None.
+
+### New packages
+None. The API client uses only `fetch` (built-in) and types. No new npm packages required.
+
+---
+
+### Acceptance criteria
+- [ ] `web/api/` directory exists with all 6 files
+- [ ] No TypeScript errors other than missing `~/lib/*` imports (those are resolved in MIGRATION-04)
+- [ ] `pnpm build` does not introduce new errors beyond the known `~/lib/*` missing imports
+- [ ] Files are copied verbatim from the fork — no functional modifications
+
+### Branch name
+`feat/migration-03-web-api-client`
+
+### PR title
+`feat(\`web/api\`): add PG API client, types, mappers, and error classes`
+
+### PR summary template
+Adds the `web/api/` layer from the fork: a typed HTTP client for all PG BFF routes,
+wire DTO TypeScript types, response mappers, and a typed error hierarchy (session expired,
+not found, timeout, CSRF, redirect, validation). TypeScript errors on `~/lib/*` imports
+are expected and will be resolved when MIGRATION-04 (shadcn UI delta) merges. This layer
+is a prerequisite for the Posts (MIGRATION-05), Groups (MIGRATION-06), and shared comms
+selectors (MIGRATION-07) migration layers. See `docs/FORK_MIGRATION.md` Layer 3.
diff --git a/docs/fork-migration-issues/issue-04-shadcn-ui-delta.md b/docs/fork-migration-issues/issue-04-shadcn-ui-delta.md
new file mode 100644
index 0000000..49dd5fc
--- /dev/null
+++ b/docs/fork-migration-issues/issue-04-shadcn-ui-delta.md
@@ -0,0 +1,149 @@
+# MIGRATION-04 — Web: shadcn UI primitives delta
+
+### Status
+`blocked`
+
+### Blocking sprint PRs
+- [PR #182](https://github.com/String-sg/teacher-workspace/pull/182) `refactor(web): replace Flow DS with shadcn Base UI` — adds most of `web/components/ui/` and `web/lib/utils.ts`. Must merge first so this issue only adds the delta.
+
+### Prerequisite migration issues
+- MIGRATION-01 — ensures `sonner` is installed (needed by `web/lib/notify.ts`)
+
+### Background
+PR #182 migrates the existing UI from Flow DS to shadcn. The fork contains 22 shadcn
+component files and 4 `web/lib/` utility files. PR #182 will land the components needed
+for the existing app. This issue adds what remains: components specific to Posts and Groups
+(Calendar, Collapsible, Progress, RadioGroup, Sheet) and two utility files
+(`web/lib/notify.ts` and `web/lib/validation-errors.ts`) that the feature modules depend on.
+See `docs/FORK_MIGRATION.md` Layer 4.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify:
+- [ ] PR #182 has been merged
+- [ ] MIGRATION-01 has been merged (sonner installed)
+- [ ] `git pull origin main` is clean
+
+---
+
+### Steps
+
+#### Step 1 — Diff `web/components/ui/` against the fork
+The fork has exactly these 22 files in `web/components/ui/`:
+```
+badge.tsx        button.tsx     calendar.tsx   card.tsx
+checkbox.tsx     collapsible.tsx dialog.tsx     dropdown-menu.tsx
+index.ts         input.tsx      label.tsx      popover.tsx
+progress.tsx     radio-group.tsx select.tsx    separator.tsx
+sheet.tsx        switch.tsx     table.tsx      tabs.tsx
+textarea.tsx     tooltip.tsx
+```
+
+Run:
+```
+ls web/components/ui/
+```
+
+For every file in the fork list that is NOT present in `main` after PR #182 merges,
+copy it from the fork:
+```
+cp d:\Environment\tw\teacher-workspace-pg\web\components\ui\<filename> web\components\ui\<filename>
+```
+
+Components most likely to be missing (not needed for the existing app, only for Posts/Groups):
+- `calendar.tsx` — used by `SchedulePickerDialog` in Posts
+- `collapsible.tsx` — used by recipient selector in Posts
+- `progress.tsx` — used by read-rate display in Posts
+- `radio-group.tsx` — used by response type selector in Posts
+- `sheet.tsx` — used by mobile panel in Posts
+
+Also check `index.ts` — the fork exports all components from a single barrel file.
+If PR #182's `index.ts` is missing any components that were just added, append
+the missing exports.
+
+#### Step 2 — Add `web/lib/notify.ts`
+Check if `web/lib/notify.ts` exists after PR #182 merges:
+```
+ls web/lib/
+```
+If absent, copy verbatim from the fork:
+```
+cp d:\Environment\tw\teacher-workspace-pg\web\lib\notify.ts web\lib\notify.ts
+```
+This file wraps `sonner`'s `toast()` into named helpers (`notify.success`, `notify.error`,
+etc.). It requires `sonner` to be installed (handled in MIGRATION-01).
+
+#### Step 3 — Add `web/lib/validation-errors.ts` and its test
+Check if `web/lib/validation-errors.ts` exists:
+```
+ls web/lib/
+```
+If absent, copy both files from the fork:
+```
+cp d:\Environment\tw\teacher-workspace-pg\web\lib\validation-errors.ts web\lib\validation-errors.ts
+cp d:\Environment\tw\teacher-workspace-pg\web\lib\validation-errors.test.ts web\lib\validation-errors.test.ts
+```
+This file maps `PGValidationError` field paths to form field names. It is imported by
+`web/api/client.ts` (already landed in MIGRATION-03).
+
+#### Step 4 — Verify TypeScript and tests
+```
+pnpm exec tsc --noEmit
+pnpm test
+```
+After this issue, the `~/lib/` import errors that were expected in MIGRATION-03 should
+now resolve. All tests in `web/lib/validation-errors.test.ts` must pass.
+
+If `pnpm exec tsc --noEmit` still shows errors, investigate — do not raise the PR with
+unresolved TypeScript errors (other than imports from MIGRATION-05/06/07 which have not
+landed yet).
+
+---
+
+### Files to copy verbatim (only those absent after PR #182 merges)
+Check presence before copying each:
+- `web/components/ui/calendar.tsx` → `web/components/ui/calendar.tsx`
+- `web/components/ui/collapsible.tsx` → `web/components/ui/collapsible.tsx`
+- `web/components/ui/progress.tsx` → `web/components/ui/progress.tsx`
+- `web/components/ui/radio-group.tsx` → `web/components/ui/radio-group.tsx`
+- `web/components/ui/sheet.tsx` → `web/components/ui/sheet.tsx`
+- `web/lib/notify.ts` → `web/lib/notify.ts`
+- `web/lib/validation-errors.ts` → `web/lib/validation-errors.ts`
+- `web/lib/validation-errors.test.ts` → `web/lib/validation-errors.test.ts`
+
+### Files to copy with modifications
+- `web/components/ui/index.ts` — append missing exports if incomplete (do not overwrite)
+
+### Files to skip
+- `web/lib/utils.ts` — added by PR #182, do not duplicate
+
+### New packages
+None (sonner handled by MIGRATION-01, all other shadcn-related packages by PR #182).
+
+---
+
+### Acceptance criteria
+- [ ] All 22 files from the fork's `web/components/ui/` are present in `main`
+- [ ] `web/components/ui/index.ts` exports all 22 components
+- [ ] `web/lib/notify.ts` exists
+- [ ] `web/lib/validation-errors.ts` exists
+- [ ] `web/lib/validation-errors.test.ts` exists and passes
+- [ ] `pnpm exec tsc --noEmit` passes (zero errors, other than any from not-yet-landed MIGRATION-05/06/07)
+- [ ] `pnpm test` passes
+
+### Branch name
+`feat/migration-04-shadcn-ui-delta`
+
+### PR title
+`feat(\`web\`): add missing shadcn components and lib utilities`
+
+### PR summary template
+Adds the shadcn UI components and `web/lib/` utilities from the fork that were not included
+in the sprint's PR #182 migration. Specifically: the shadcn components needed by the Posts
+and Groups modules (Calendar, Collapsible, Progress, RadioGroup, Sheet), the `notify.ts`
+toast helper, and the `validation-errors.ts` PG error mapper with its tests. After this PR,
+the TypeScript errors introduced by MIGRATION-03 (missing `~/lib/*` imports) will resolve.
+See `docs/FORK_MIGRATION.md` Layer 4.
diff --git a/docs/fork-migration-issues/issue-05-posts-module.md b/docs/fork-migration-issues/issue-05-posts-module.md
new file mode 100644
index 0000000..ad08862
--- /dev/null
+++ b/docs/fork-migration-issues/issue-05-posts-module.md
@@ -0,0 +1,215 @@
+# MIGRATION-05 — Web: Posts module
+
+### Status
+`pending`
+
+### Blocking sprint PRs
+None directly. All blockers are migration prerequisites below.
+
+### Prerequisite migration issues
+- MIGRATION-02 (Go PG BFF) — Go server must serve `/api/web/2/staff/*` routes
+- MIGRATION-03 (Web API client) — all PG API calls live in `web/api/`
+- MIGRATION-04 (shadcn UI delta) — Posts components import from `~/components/ui/` and `~/lib/`
+- MIGRATION-07 (Shared comms selectors) — `RecipientSelector` uses `student-recipient-selector`
+
+### Background
+The fork's Posts module implements the full announcements and consent-form creation,
+editing, scheduling, and viewing flows. It comprises 31 component files, 5 test files,
+3 container views, 3 data/registry files, and 1 container-level utility. The module
+includes a Tiptap rich-text editor, attachment upload with race-condition handling,
+draft/autosave, schedule-send with a two-column date-time picker, consent form questions,
+recipient selection, and response/read-rate analytics.
+See `docs/FORK_MIGRATION.md` Layer 5.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify:
+- [ ] MIGRATION-02, MIGRATION-03, MIGRATION-04, MIGRATION-07 are all merged into `main`
+- [ ] `git pull origin main` is clean
+- [ ] `pnpm exec tsc --noEmit` passes with zero errors on `main`
+- [ ] `pnpm test` passes on `main`
+- [ ] Go server starts with `TW_PG_MOCK=true` and responds to `/api/web/2/staff/*`
+
+---
+
+### Steps
+
+#### Step 1 — Install Tiptap and date picker packages
+The rich-text editor and schedule picker require new npm packages:
+```
+pnpm add @tiptap/react @tiptap/starter-kit @tiptap/extension-character-count @tiptap/extension-highlight @tiptap/extension-link @tiptap/extension-text-align @tiptap/extension-underline
+pnpm add react-day-picker
+```
+
+Verify the pnpm override for `@tiptap/pm` is present in `package.json` (added in MIGRATION-01):
+```json
+"pnpm": { "overrides": { "@tiptap/pm": "3.22.3" } }
+```
+If absent, add it before running `pnpm install`.
+
+#### Step 2 — Copy `web/components/posts/`
+The directory does not exist in this repo. Copy the entire directory:
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\web\components\posts\ web\components\posts\
+```
+
+This copies 31 files (26 components + 5 tests):
+- `AttachmentSection.tsx` — file/photo upload with race-condition handling
+- `ConsentFormHistoryList.tsx` — read-only history of past versions
+- `DeletePostDialog.tsx` — confirmation dialog for post deletion
+- `DueDateSection.tsx` — due date picker for consent forms
+- `EnquiryEmailSelector.tsx` — staff email selector for enquiries
+- `EventScheduleSection.tsx` — event date/time/venue for consent forms
+- `PostCard.tsx` — card in the posts list view
+- `PostFilterPopover.tsx` — Status/Response/Date filter axes + Mine/Shared tabs
+- `PostPreview.tsx` — parent-view phone-frame preview
+- `PostTypePicker.tsx` — announcement vs consent form type selector
+- `QuestionBuilder.tsx` — consent form custom question authoring
+- `ReadRate.tsx` — read/response rate percentage display
+- `ReadTrackingCards.tsx` — analytics cards for post detail
+- `RecipientFilterPopover.tsx` — filter recipients by class/group
+- `RecipientReadTable.tsx` — table of per-recipient read status
+- `RecipientSelector.tsx` — group + individual student selection
+- `ReminderSection.tsx` + `ReminderSection.test.tsx`
+- `ResponseTypeSelector.tsx` — yes/no, acknowledgement, etc.
+- `RichTextEditor.tsx` — Tiptap editor with PGW HTML allowlist restrictions
+- `RichTextToolbar.tsx` + `RichTextToolbar.test.tsx`
+- `SchedulePickerDialog.tsx` + `SchedulePickerDialog.test.tsx` — two-column date/time picker
+- `SendConfirmationDialog.tsx` — pre-send confirmation with recipient summary
+- `ShortcutsSection.tsx` — quick-fill shortcuts in the create form
+- `SplitPostButton.tsx` — save-as-draft vs send split button
+- `summarise-recipients.ts` + `summarise-recipients.test.ts`
+- `VenueSection.tsx` — venue input for events
+- `WebsiteLinksSection.tsx` — URL attachment section
+
+Do NOT modify any of these files during copy.
+
+#### Step 3 — Copy `web/data/`
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\web\data\ web\data\
+```
+Copies:
+- `web/data/mock-pg-announcements.ts` — mock announcement data for development
+- `web/data/mock-pg-announcements.test.ts` — tests for mock data shape
+- `web/data/posts-registry.ts` — post type configuration registry
+
+#### Step 4 — Copy Posts container views
+Copy the three Posts-related containers from the fork. Check the current state of
+`web/containers/` in `main` — do not overwrite existing containers (`HomeView.tsx`,
+`RootLayout.tsx`, `StudentsView.tsx`). Copy only the new ones:
+
+```
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\PostsView.tsx web\containers\PostsView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\PostsView.test.tsx web\containers\PostsView.test.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\PostDetailView.tsx web\containers\PostDetailView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CreatePostView.tsx web\containers\CreatePostView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CreatePostView.reducer.test.ts web\containers\CreatePostView.reducer.test.ts
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CreatePostView.validation.test.tsx web\containers\CreatePostView.validation.test.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\createPostValidation.ts web\containers\createPostValidation.ts
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\SessionExpiredView.tsx web\containers\SessionExpiredView.tsx
+```
+
+Also copy `ComponentsView.tsx` (a dev-only component preview page):
+```
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\ComponentsView.tsx web\containers\ComponentsView.tsx
+```
+
+#### Step 5 — Wire up routes in the React Router config
+Open the fork's router/App setup to understand how Posts routes are registered:
+```
+cat d:\Environment\tw\teacher-workspace-pg\web\App.tsx
+```
+(or wherever the fork defines its React Router routes — check `web/main.tsx` or `web/App.tsx`)
+
+Then open the equivalent file in this repo and add the Posts routes following the same
+pattern. Posts routes to add:
+- `/posts` → `PostsView`
+- `/posts/:id` → `PostDetailView`
+- `/posts/create` → `CreatePostView`
+- `/posts/:id/edit` → `CreatePostView` (edit mode)
+- `/session-expired` → `SessionExpiredView`
+- `/components` → `ComponentsView` (dev only — consider gating behind `import.meta.env.DEV`)
+
+Follow the existing routing conventions in `main`. If the fork uses React Router data
+loaders for fetching, replicate that pattern exactly — do not substitute with `useEffect`
+fetching.
+
+#### Step 6 — TypeScript and tests
+```
+pnpm exec tsc --noEmit
+pnpm test
+```
+All tests in `web/components/posts/` and `web/containers/` must pass.
+
+Known issues to watch for:
+- `SchedulePickerDialog` caps the selectable date to today+21 days and filters out past
+  time slots when today is selected. Its tests assert this behaviour — do not modify the logic.
+- `RichTextEditor` disables `StarterKit`'s built-in `link` and `underline` extensions
+  to avoid conflicts with the explicit `@tiptap/extension-link` and `@tiptap/extension-underline`
+  packages. If Tiptap warns about duplicate extensions, this is why.
+
+---
+
+### Files to copy verbatim
+All files in `web/components/posts/` (31 files), `web/data/` (3 files), and the Posts
+containers listed in Step 4 (9 files).
+
+### Files to copy with modifications
+None. Do not modify component files during migration.
+
+### Files to modify (existing repo files)
+- Router config / `web/App.tsx` or `web/main.tsx` — add Posts routes (Step 5)
+
+### Files to skip
+- Do not copy containers that already exist in this repo:
+  `HomeView.tsx`, `RootLayout.tsx`, `StudentsView.tsx`
+- Groups containers (`GroupsView`, `CreateCustomGroupView`, etc.) — handled in MIGRATION-06
+- `AddStudentsView.tsx` — Groups, handled in MIGRATION-06
+
+### New packages
+```
+pnpm add @tiptap/react @tiptap/starter-kit @tiptap/extension-character-count @tiptap/extension-highlight @tiptap/extension-link @tiptap/extension-text-align @tiptap/extension-underline
+pnpm add react-day-picker
+```
+
+---
+
+### Key behavioural notes for review
+These are non-obvious behaviours baked into the fork that reviewers should verify:
+
+1. **SchedulePickerDialog date cap:** The picker disables dates beyond today+21 days and
+   filters time slots that have already passed when today is selected. Tests verify this.
+2. **Draft autosave:** `CreatePostView` has dirty-state tracking and autosave. If a user
+   navigates away mid-edit, a save is triggered. The reducer test covers this.
+3. **Consent form payload shape:** `eventStartDate` is sent as `{date, time}` (not a flat
+   string). The PGW API requires this exact shape — do not normalise it.
+4. **Consent form detail response:** The PGW detail endpoint returns `[detail]` (an array
+   with one item). The mapper unwraps this. Do not remove that unwrap.
+5. **CSRF retry:** The API client retries once on `-4013` errors with a token refresh.
+   This is in `web/api/client.ts` (already landed), not in the component files.
+
+### Acceptance criteria
+- [ ] `pnpm exec tsc --noEmit` passes with zero errors
+- [ ] `pnpm test` passes including all posts component and container tests
+- [ ] `/posts` route renders `PostsView` in the browser
+- [ ] `/posts/create` route renders `CreatePostView` in the browser
+- [ ] Go server running with `TW_PG_MOCK=true` serves announcement fixture data to the posts list
+- [ ] `pnpm build` succeeds
+
+### Branch name
+`feat/migration-05-posts-module`
+
+### PR title
+`feat(\`posts\`): migrate Posts and Announcements module from fork`
+
+### PR summary template
+Migrates the Posts and Announcements module from `teacher-workspace-pg`. Includes the
+complete create/edit/detail/list flow for announcements and consent forms, Tiptap rich-text
+editor, schedule-send picker, recipient selection, attachment upload, draft/autosave,
+read-rate analytics, and all associated tests. Wires up React Router routes for `/posts`,
+`/posts/create`, `/posts/:id`, and `/posts/:id/edit`. Backend data is served by the mock
+BFF (MIGRATION-02) with no external dependencies in development. See `docs/FORK_MIGRATION.md`
+Layer 5.
diff --git a/docs/fork-migration-issues/issue-06-groups-module.md b/docs/fork-migration-issues/issue-06-groups-module.md
new file mode 100644
index 0000000..09bb8a9
--- /dev/null
+++ b/docs/fork-migration-issues/issue-06-groups-module.md
@@ -0,0 +1,176 @@
+# MIGRATION-06 — Web: Groups module
+
+### Status
+`pending`
+
+### Blocking sprint PRs
+None directly. All blockers are migration prerequisites below.
+
+### Prerequisite migration issues
+- MIGRATION-02 (Go PG BFF) — Go server must serve `/api/web/2/staff/*` routes
+- MIGRATION-03 (Web API client) — custom group API calls live in `web/api/`
+- MIGRATION-04 (shadcn UI delta) — Groups components import from `~/components/ui/` and `~/lib/`
+- MIGRATION-07 (Shared comms selectors) — `ShareGroupModal` uses `staff-selector`
+
+### Background
+The fork's Groups module implements custom student group creation, editing, sharing, and
+deletion. It includes an Excel upload path for bulk-adding students. The module comprises
+22 component files (including tests), 5 container views (including tests), and 3 Excel
+utility files. PII compliance is built in: the `StudentResultsTable` masks UIN/FIN values.
+This module can be developed in parallel with MIGRATION-05 (Posts) once the shared
+prerequisites (02, 03, 04, 07) are merged.
+See `docs/FORK_MIGRATION.md` Layer 6.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify:
+- [ ] MIGRATION-02, MIGRATION-03, MIGRATION-04, MIGRATION-07 are all merged into `main`
+- [ ] `git pull origin main` is clean
+- [ ] `pnpm exec tsc --noEmit` passes with zero errors on `main`
+- [ ] `pnpm test` passes on `main`
+- [ ] Go server starts with `TW_PG_MOCK=true` and responds to custom groups fixtures
+
+---
+
+### Steps
+
+#### Step 1 — Install xlsx package
+The Excel upload feature parses `.xlsx` and `.xls` files client-side:
+```
+pnpm add xlsx
+```
+
+#### Step 2 — Copy `web/components/groups/`
+The directory does not exist in this repo. Copy the entire directory:
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\web\components\groups\ web\components\groups\
+```
+
+This copies 22 files (12 components + 10 tests):
+- `AssignedGroupsSection.tsx` + `AssignedGroupsSection.test.tsx` — card grid of teacher's assigned groups
+- `CustomGroupsTable.tsx` + `CustomGroupsTable.test.tsx` — table with empty and populated states
+- `DeleteGroupModal.tsx` + `DeleteGroupModal.test.tsx` — confirmation modal with checkbox
+- `ExcelUploadPanel.tsx` + `ExcelUploadPanel.test.tsx` — drag-and-drop + file-select for Excel upload
+- `ShareGroupModal.tsx` + `ShareGroupModal.test.tsx` — staff picker with view/edit permission toggle
+- `StudentFilterBar.tsx` + `StudentFilterBar.test.tsx` — class/CCA filter for student search
+- `StudentResultsTable.tsx` + `StudentResultsTable.test.tsx` — UIN/FIN masked student results
+- `StudentsByClassList.tsx` + `StudentsByClassList.test.tsx` — class-indexed student list for edit flow
+- `excel-upload-validation.ts` + `excel-upload-validation.test.ts` — validates uploaded file format
+- `parse-excel-file.ts` + `parse-excel-file.test.ts` — parses xlsx to student array
+- `validate-upload-students.ts` + `validate-upload-students.test.ts` — validates student data against school roster
+
+Do NOT modify any of these files during copy.
+
+#### Step 3 — Copy Groups container views
+Copy only the Groups-related containers. Do not overwrite containers that already exist
+in this repo or were added by MIGRATION-05:
+
+```
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\GroupsView.tsx web\containers\GroupsView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\GroupsView.test.tsx web\containers\GroupsView.test.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CreateCustomGroupView.tsx web\containers\CreateCustomGroupView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CreateCustomGroupView.test.tsx web\containers\CreateCustomGroupView.test.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CreateCustomGroupView.excel.test.tsx web\containers\CreateCustomGroupView.excel.test.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\AddStudentsView.tsx web\containers\AddStudentsView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\AddStudentsView.test.tsx web\containers\AddStudentsView.test.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CustomGroupDetailView.tsx web\containers\CustomGroupDetailView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\CustomGroupDetailView.test.tsx web\containers\CustomGroupDetailView.test.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\EditCustomGroupView.tsx web\containers\EditCustomGroupView.tsx
+cp d:\Environment\tw\teacher-workspace-pg\web\containers\EditCustomGroupView.test.tsx web\containers\EditCustomGroupView.test.tsx
+```
+
+#### Step 4 — Wire up routes in the React Router config
+Open the fork's router/App to see how Groups routes are registered:
+```
+cat d:\Environment\tw\teacher-workspace-pg\web\App.tsx
+```
+(or wherever routes are defined — check `web/main.tsx` or `web/App.tsx`)
+
+Then add the Groups routes to the equivalent file in this repo. Routes to add:
+- `/groups` → `GroupsView`
+- `/groups/create` → `CreateCustomGroupView`
+- `/groups/create/add-students` → `AddStudentsView`
+- `/groups/:id` → `CustomGroupDetailView`
+- `/groups/:id/edit` → `EditCustomGroupView`
+- `/groups/:id/edit/add-students` → `AddStudentsView` (reused with edit context)
+
+Follow the same React Router conventions used by MIGRATION-05 for Posts routes.
+
+#### Step 5 — TypeScript and tests
+```
+pnpm exec tsc --noEmit
+pnpm test
+```
+All tests in `web/components/groups/` and the Groups containers must pass.
+
+---
+
+### Files to copy verbatim
+All 22 files in `web/components/groups/` and 11 Groups container files listed in Step 3.
+
+### Files to copy with modifications
+None. Do not modify component files during migration.
+
+### Files to modify (existing repo files)
+- Router config / `web/App.tsx` or `web/main.tsx` — add Groups routes (Step 4)
+
+### Files to skip
+- Do not copy containers already in this repo or added by MIGRATION-05
+
+### New packages
+```
+pnpm add xlsx
+```
+
+---
+
+### Key behavioural notes for review
+
+1. **PII masking (critical):** `StudentResultsTable` masks UIN and FIN values. This is a
+   compliance requirement. Verify in the browser that student ID numbers are masked in
+   the search results table. Do NOT remove the masking logic.
+
+2. **API payload field names:** The create/update custom group endpoints require exactly:
+   - `groupName` (not `name`)
+   - `selectedSchoolStudents` (not `students` or `studentIds`)
+   - `staffIds` (not `staffId`) in the share endpoint
+   These are PGW API quirks. Do not rename them.
+
+3. **Detail response unwrap:** The custom group detail endpoint returns `[detail]` (a single-
+   item array, same quirk as consent forms). The mapper in `web/api/mappers.ts` unwraps this.
+   Do not remove that unwrap.
+
+4. **Pre-population in edit flow:** `EditCustomGroupView` pre-selects existing students from
+   the group. `ShareGroupModal` pre-selects staff who already have access. Both rely on the
+   detail response being correctly mapped before the view renders.
+
+5. **Excel upload validation:** The three Excel utility files validate file format, parse
+   the xlsx, and cross-reference the uploaded students against the school's student roster.
+   All three steps must succeed before the upload is accepted. Tests cover the validation
+   logic and error paths.
+
+### Acceptance criteria
+- [ ] `pnpm exec tsc --noEmit` passes with zero errors
+- [ ] `pnpm test` passes including all groups component and container tests
+- [ ] `/groups` route renders `GroupsView` in the browser
+- [ ] `/groups/create` route renders `CreateCustomGroupView` in the browser
+- [ ] Go server running with `TW_PG_MOCK=true` serves groups fixture data
+- [ ] Student ID numbers are masked in `StudentResultsTable`
+- [ ] `pnpm build` succeeds
+
+### Branch name
+`feat/migration-06-groups-module`
+
+### PR title
+`feat(\`groups\`): migrate Custom Groups module from fork`
+
+### PR summary template
+Migrates the Custom Groups module from `teacher-workspace-pg`. Includes create, edit, share,
+and delete flows for custom student groups, an Excel upload path for bulk student addition,
+and the full student search and filter experience. PII compliance: UIN/FIN values are masked
+in all student result tables. Wires up React Router routes for `/groups` and its sub-routes.
+Backend data is served by the mock BFF (MIGRATION-02) with no external dependencies in
+development. See `docs/FORK_MIGRATION.md` Layer 6.
diff --git a/docs/fork-migration-issues/issue-07-shared-comms-selectors.md b/docs/fork-migration-issues/issue-07-shared-comms-selectors.md
new file mode 100644
index 0000000..8912199
--- /dev/null
+++ b/docs/fork-migration-issues/issue-07-shared-comms-selectors.md
@@ -0,0 +1,96 @@
+# MIGRATION-07 — Web: Shared comms selectors
+
+### Status
+`pending`
+
+### Blocking sprint PRs
+None.
+
+### Prerequisite migration issues
+- MIGRATION-03 (Web API client) — selectors call PG staff/student APIs
+- MIGRATION-04 (shadcn UI delta) — selectors import from `~/components/ui/`
+
+### Background
+The fork adds three shared selector components under `web/components/comms/`. These are
+consumed by both the Posts module (`RecipientSelector` uses `student-recipient-selector`,
+`EnquiryEmailSelector` uses `staff-selector`) and the Groups module (`ShareGroupModal`
+uses `staff-selector`). They are placed in a shared `comms/` directory rather than in
+either feature directory to make this shared ownership explicit. This issue must merge
+before MIGRATION-05 and MIGRATION-06.
+See `docs/FORK_MIGRATION.md` Layer 7.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify:
+- [ ] MIGRATION-03 has been merged
+- [ ] MIGRATION-04 has been merged
+- [ ] `git pull origin main` is clean
+- [ ] `pnpm exec tsc --noEmit` passes with zero errors on `main`
+
+---
+
+### Steps
+
+#### Step 1 — Copy `web/components/comms/`
+The directory does not exist in this repo. Copy all three files:
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\web\components\comms\ web\components\comms\
+```
+
+Files copied:
+- `web/components/comms/entity-selector.tsx` — generic headless selection primitive
+- `web/components/comms/staff-selector.tsx` — staff search and selection, used by ShareGroupModal and EnquiryEmailSelector
+- `web/components/comms/student-recipient-selector.tsx` — student recipient search and selection, used by RecipientSelector
+
+Do NOT modify any of these files.
+
+#### Step 2 — TypeScript check
+```
+pnpm exec tsc --noEmit
+```
+These three files import from `~/components/ui/` (MIGRATION-04) and `~/api/` (MIGRATION-03),
+both of which must already be in `main`. There should be no TypeScript errors.
+
+If there are errors related to `~/components/posts/` or `~/components/groups/`, those are
+from the files being imported by not-yet-landed MIGRATION-05/06 — they do not exist yet
+and will not cause errors in this file set because the comms files themselves only export,
+not import those modules.
+
+---
+
+### Files to copy verbatim
+- `web/components/comms/entity-selector.tsx` → `web/components/comms/entity-selector.tsx`
+- `web/components/comms/staff-selector.tsx` → `web/components/comms/staff-selector.tsx`
+- `web/components/comms/student-recipient-selector.tsx` → `web/components/comms/student-recipient-selector.tsx`
+
+### Files to copy with modifications
+None.
+
+### Files to skip
+None.
+
+### New packages
+None.
+
+---
+
+### Acceptance criteria
+- [ ] `web/components/comms/` directory exists with all 3 files
+- [ ] `pnpm exec tsc --noEmit` passes with zero errors
+- [ ] `pnpm build` succeeds
+
+### Branch name
+`feat/migration-07-shared-comms-selectors`
+
+### PR title
+`feat(\`web/comms\`): add shared staff and student selector components`
+
+### PR summary template
+Adds the shared comms selector components from the fork: a generic entity selector
+primitive, a staff picker (used by the Groups share flow and Posts enquiry email selector),
+and a student recipient selector (used by the Posts recipient section). These three files
+are prerequisites for both MIGRATION-05 (Posts) and MIGRATION-06 (Groups). See
+`docs/FORK_MIGRATION.md` Layer 7.
diff --git a/docs/fork-migration-issues/issue-08-docs.md b/docs/fork-migration-issues/issue-08-docs.md
new file mode 100644
index 0000000..41db6e9
--- /dev/null
+++ b/docs/fork-migration-issues/issue-08-docs.md
@@ -0,0 +1,124 @@
+# MIGRATION-08 — Documentation and planning docs
+
+### Status
+`ready`
+
+### Blocking sprint PRs
+None.
+
+### Prerequisite migration issues
+None.
+
+### Background
+The fork contains roughly 50 markdown files across `docs/`, `.planning/codebase/`, and
+the root-level `DESIGN.md` and `TODOS.md`. These cover architecture RFCs, PG parity scope
+audits, implementation plans, API reference specs, and local setup guides. None of these
+files are code and none block feature work. They can land in any order and in any number
+of separate PRs. Consider splitting by subdirectory if a single PR would be too large to
+review comfortably.
+See `docs/FORK_MIGRATION.md` Layer 8.
+
+### Repo paths
+- **Fork (source):** `d:\Environment\tw\teacher-workspace-pg\`
+- **Target (this repo):** `d:\Environment\tw\teacher-workspace\`
+
+### Starting point
+Before creating the branch, verify:
+- [ ] `git pull origin main` is clean
+
+No code dependencies. Can be raised at any time.
+
+---
+
+### Steps
+
+#### Step 1 — Copy root-level docs files
+```
+cp d:\Environment\tw\teacher-workspace-pg\DESIGN.md DESIGN.md
+cp d:\Environment\tw\teacher-workspace-pg\TODOS.md TODOS.md
+```
+
+#### Step 2 — Copy `.planning/codebase/` docs
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\.planning\ .planning\
+```
+This copies 7 markdown files documenting: architecture overview, known concerns,
+conventions, third-party integrations, tech stack decisions, repo structure, and
+testing strategy.
+
+#### Step 3 — Copy `docs/` subdirectories from fork
+The fork's `docs/` tree (distinct from this repo's `docs/` which already has
+`FORK_MIGRATION.md`, `CURRENT_SPRINT_ISSUES.md`, and `fork-migration-issues/`).
+
+Copy each subdirectory carefully — do NOT overwrite existing files in this repo's `docs/`:
+```
+cp -r d:\Environment\tw\teacher-workspace-pg\docs\architecture\ docs\architecture\
+cp -r d:\Environment\tw\teacher-workspace-pg\docs\audits\ docs\audits\
+cp -r d:\Environment\tw\teacher-workspace-pg\docs\brainstorms\ docs\brainstorms\
+cp -r d:\Environment\tw\teacher-workspace-pg\docs\plans\ docs\plans\
+cp -r d:\Environment\tw\teacher-workspace-pg\docs\references\ docs\references\
+cp -r d:\Environment\tw\teacher-workspace-pg\docs\setup\ docs\setup\
+cp -r d:\Environment\tw\teacher-workspace-pg\docs\superpowers\ docs\superpowers\
+```
+
+Before running, verify none of these subdirectory names already exist in `docs/`:
+```
+ls docs/
+```
+If any name collides, inspect the collision manually before overwriting.
+
+Do NOT copy:
+- `d:\Environment\tw\teacher-workspace-pg\docs\screenshots\` — binary image assets, large,
+  low value in the repo. Skip unless the team specifically requests them.
+
+#### Step 4 — Review for sensitive content
+Before raising the PR, scan the copied markdown files for any accidentally committed
+sensitive data (API keys, credentials, internal URLs that should not be public):
+```
+grep -r "secret\|password\|token\|key\|credential" docs/ .planning/ --include="*.md" -i
+```
+Review each match. Remove any sensitive values found before committing.
+
+---
+
+### Files to copy verbatim
+- `DESIGN.md` → `DESIGN.md`
+- `TODOS.md` → `TODOS.md`
+- `.planning/codebase/` → `.planning/codebase/` (7 markdown files)
+- `docs/architecture/` → `docs/architecture/`
+- `docs/audits/` → `docs/audits/`
+- `docs/brainstorms/` → `docs/brainstorms/`
+- `docs/plans/` → `docs/plans/`
+- `docs/references/` → `docs/references/`
+- `docs/setup/` → `docs/setup/`
+- `docs/superpowers/` → `docs/superpowers/`
+
+### Files to skip
+- `docs/screenshots/` — binary assets, skip by default
+- Any file from the fork that would overwrite an existing file in `docs/` — inspect manually
+
+### New packages
+None.
+
+---
+
+### Acceptance criteria
+- [ ] `DESIGN.md` exists at repo root
+- [ ] `TODOS.md` exists at repo root
+- [ ] `.planning/codebase/` contains 7 markdown files
+- [ ] `docs/architecture/`, `docs/audits/`, `docs/plans/`, `docs/references/`, `docs/setup/` all exist
+- [ ] No sensitive values in copied markdown files
+- [ ] No existing files in `docs/` were overwritten
+
+### Branch name
+`docs/migration-08-planning-and-architecture-docs`
+
+### PR title
+`docs(migration): port architecture docs, RFCs, and planning files from fork`
+
+### PR summary template
+Ports the documentation and planning files from `teacher-workspace-pg` to this repo.
+Includes architecture RFCs (frontend RFC-027, backend RFC-028, color tokens, sidebar flow
+shim), PG parity scope audits, implementation plans, PG API reference specs, local PGW
+setup guide, and codebase mapping docs. No code changes. Can be reviewed independently of
+any feature migration PR. See `docs/FORK_MIGRATION.md` Layer 8.