Files
Project-SDE-WP-Suite/docs/waves/context-handoff-2026-10-12.md

98 lines
7.1 KiB
Markdown

# Context handoff: Work Package Suite
> Update 2026-10-16: waves 11 and 13 (T13.2 to T13.5) are on the release branch `release/waves-11-13-okta-sync`, with T13.1 held back. The branch and wave status tables below describe 2026-10-12. See `docs/waves/wave-13.md` for the current state.
Date: 2026-10-12
Purpose: Give a new chat the facts about waves 11, 12, 13, and 16.
This file is a handoff note. It is not a spec. The spec files stay the source of truth (`IMPLEMENTATION.md`, `docs/waves/*`, `CLAUDE.md`).
It was checked against `git` on 2026-10-12. Earlier chat summaries about this repo are out of date. Use this file.
## 1. Branch state
| Branch | State |
|---|---|
| `main` | At `d42ae0c` (2026-10-06). Contains wave 12 (CR-020, bulk user editing) and wave 16 (D19, D20, D21), both merged by PR. |
| `feat/waves-11-13` | Local and `origin` are the same commit, `da1325c`. It is pushed. It is not merged. It is 13 commits ahead of `main` and 19 behind. |
| `notes/cr019-usage-metrics-d18-deprovisioning` | Holds the same wave 11 work plus the session notes. |
Correction to an earlier statement: the Gitea push is no longer blocked. The branch is on `origin`.
Merge rule from `wave-12.md`: T13.1 (idle timeout) must not reach `main` before T14.1. Do not merge `feat/waves-11-13` into `main` as a whole without a decision from the user. Wave 11 and T13.1 are on the same branch.
Working tree on `main` (2026-10-12) has two untracked files: `WorkPackageSuite_Consolidated_Change_Request_R2.docx` and `docs/waves/decisions-2026-08-25.md`. Do not delete them.
## 2. What is on `feat/waves-11-13`
| Commit | Task | Item |
|---|---|---|
| `75ac930` | Planning docs for CR-019, CR-020, D18 | CR-019, CR-020, D18 |
| `0652fa7` | T11.1 UsageEvent model and migration | CR-019 |
| `850b789` | T11.2 capture usage events | CR-019 |
| `3584695`, `6cde6e3` | T13.1 idle timeout with an absolute ceiling | D18 |
| `8e863ae` | T11.3 aggregation endpoint with filters | CR-019 |
| `2de76d5` | T11.4 usage export (raw and sanitized CSV) | CR-019 |
| `a6c3fbf`, `0b5ab59` | T11.5 admin console "Activity & usage" card, checked at 390px and 1440px | CR-019 |
| `b2a083a` | T11.6 retire the per-browser Usage report | CR-019 |
| `2842ec9` | Session notes for 2026-09-23 | none |
| `4f3a94b` | T11.6 follow-up: fix `tests/autosave_check.py` | CR-019 |
| `da1325c` | T11.7 full verification pass. Wave 11 closed on 2026-09-24. | CR-019 |
Notes:
- `html/wp-usage.js` and `tests/usage_check.py` were deleted in T11.6. The `track()` functions in `wp-creation-app.js` and `work-package-suite-app.js` are now documented no-ops. About 45 call sites stay.
- T11.7 found a real regression that T11.6 caused. `tests/autosave_check.py` still expected the retired tracker to write to `localStorage`. The test was fixed. It now passes 33 of 33. The cause was that T11.6 ran only `tests/baseline_shots.py`, not the full suite. Run the full suite for any frontend task.
## 3. T11.7 verification results (2026-09-24)
- Alembic: upgrade, downgrade, upgrade on SQLite passed. The SQL render for Postgres was clean (this catches SQLite-only DDL, the "BL-027 class" of defect).
- Test scripts: 38 of 39 passed after the autosave fix.
- Two known failures that are not regressions:
- `token_check.py` exits 2. This is a CLI usage detail.
- `generalinfo_check.py` finds an old color-literal gap in `wp-creation-styles.css`.
## 4. Wave status
| Wave | Items | Status |
|---|---|---|
| 10 | Okta OIDC sign-in (D15, D16) | Done. In production. |
| 11 | CR-019 usage and activity metrics | Done on `feat/waves-11-13`. Not on `main`. |
| 12 | CR-020 bulk user editing | Done. Merged to `main` on 2026-10-06 (T12.1 to T12.6). |
| 13 | D18 Okta/AD deprovisioning sync | T13.1 done on `feat/waves-11-13`. T13.2 and later are not started. T13.3 must fail closed. Do not relax that. |
| 14, 15 | Not checked in this handoff | T14.1 must land before T13.1 reaches `main`. Read the wave files before you plan. |
| 16 | D19 safe downloads, D20 one SOP per project, D21 session decode fails closed | Done. Merged to `main` on 2026-10-06. |
Wave 16 decisions (`docs/waves/decisions-2026-10-02.md`): SEC-06 (session revocation) waits for the AWS work. Other SEC findings stay as backlog drafts in `docs/reference/security-review/backlog-drafts.md`.
## 5. Rules that apply here (`CLAUDE.md`)
- Every change traces to an item ID (`CR-`, `F`, `S`, `A`, `B`, `C`, `D`, task `T<wave>.<n>`). New scope gets a new ID.
- One task per PR. Put the task ID and item IDs in the commit message and PR title.
- Do not fix other problems that you see. Log them in `docs/waves/backlog.md`.
- Do not reorder waves. Do not start a wave before the previous wave is merged, unless the task says it is independent.
- Server work is needed for CR-004, CR-018, CR-007, CR-011, CR-014, CR-013, and B4. Do not use `localStorage` for these.
- Do not change: Actual Hours in Closeout (CR-017), localization (A7), uppercase card headers in `console.css` (A5), the logged-override path `confirmEarlyRelease()` (A1), or hidden-not-deleted fields (CR-002, CR-016).
- Token rule: one place defines color, spacing, and type. Do not add raw hex values to page stylesheets.
- Accessibility (C1): use real `<button>`, `<a>`, or input elements. Add `aria-live` for status changes. Keep focus visible. Text contrast is 4.5:1 (3:1 for large text).
- Frontend checks: run `uvicorn server.app:app` on a throwaway SQLite database. Check 390px and 1440px. Capture before and after screenshots. Run the smoke test.
- If a done-when check cannot be run, do not mark the task complete. Say which check failed and why.
## 6. Environment on the user's PC
- Python was installed with `winget`. Tests use the repo `.venv`.
- Browser tests (`tests/cdp.py` and about 40 `*_check.py` scripts) need Edge or Chrome. `cdp.py` starts from an elevated shell (wave 16 note). The Linux sandbox cannot run them.
- See `C:\Users\m.mabrey\GIT\Field Value Driver\sde-meeting-toolkit\docs\context\environment-notes.md` for tool problems (PowerShell `$` removal, long git paths, the 180 second command limit).
## 7. Open items
1. Decide how `feat/waves-11-13` reaches `main`. The T13.1 and T14.1 order is the constraint.
2. Plan the next wave. T13.2 and later need an explicit instruction.
3. Future build list added 2026-10-12: `BL-062` to `BL-068` in `docs/waves/backlog.md` (mobile app, offline Field View, batch print, and related items). Answers are in `docs/waves/decisions-2026-10-12.md` (follow-ups from Matt included). The path to a mobile version outside the VPN is in `docs/waves/roadmap-mobile-scaling.md` (phases 0 to 5; confirmed: all users in the Okta group, multiple customers, company-managed devices; nine open questions in its section 7). These files are uncommitted edits on `main`.
4. Work from the other chat (the SDE Meeting Toolkit) does not touch this repo. See the toolkit `docs/context/` folder.
## 8. Related files
- `IMPLEMENTATION.md` (sections 2 and 4)
- `docs/waves/wave-11.md`, `wave-12.md`, `wave-13.md` (on `feat/waves-11-13`), `wave-16.md`
- `docs/waves/decisions-2026-09-17.md` (CR-019, CR-020, D18), `decisions-2026-10-02.md` (D19, D20, D21)
- `docs/waves/notes-2026-09-23.md` (on `feat/waves-11-13`)
- `docs/waves/backlog.md`