Files

n.siegfried 0dbc240900 Wave 7 prep - record the Aug 18 decisions as D1-D10 and amend the waves

Nick answered 21 questions at the wave 6 exit and 11 follow-ups. Seven answers
are new build work, three amend acceptance criteria on tasks already scheduled,
and two close questions without work. None of it had an item ID, so none of it
could be built under CLAUDE.md's first rule.

New items D1-D10 in docs/waves/decisions-2026-08-18.md. A new prefix rather than
widened CR/F/S/A/B/C numbers - those are referenced in documents outside this
repo and CLAUDE.md forbids reinterpreting them. Every D entry names the item it
amends and quotes the criterion it replaces, so a reader of R2 can see what moved.

  D1  sample data returns to the creator                    B7, S7   T7.1
  D2  QA distribution list configured in the SOP            CR-014   T7.6
  D3  side navigation and collapsible sections, not tabs    F6       T7.2
  D4  Urgent surfaces the audited override, never bypasses  CR-003/A1 T7.3
  D5  usage data moves to the admin console                 B7       T7.10 (new)
  D6  material list uploads at SOP configuration            CR-013   T8.6  (new)
  D7  archived projects readable by project admins          B3, C1   T9.8  (new)
  D8  5MB a file, 2GB a project, PDFs and images, one DB    CR-007   T7.7
  D9  Ready for QA appears in Field View                    CR-014   T7.6
  D10 email switched on and off from the admin console      CR-011/14 T7.6, T8.3

Two decisions were mine to make and are recorded as such. D3: the written F6
criterion (no view over two screen heights) and the answer (one long form with
side nav) cannot both hold, so the criterion now reads 'at rest' and sections
collapse by default - tabs hide sections a first-time author does not know exist.
D8: keeping 5MB files in the same database means every encrypted backup carries
them; splitting them out was rejected because a backup without the drawings
cannot restore, so a 2GB per-project ceiling was approved instead.

Also corrected, not amended: CLAUDE.md and IMPLEMENTATION.md X2 both cited
wp-creation-app.js:1962-1972 as the protected logged-override path that T7.3 is
forbidden to remove. Those lines are deletePackage() and clearSaved(). The path
is confirmEarlyRelease() at :1002. Both documents now name it by function so the
reference survives the T7.1 rewrite that is about to move it.

Wave 9 gains T9.9, a sweep of the nine backlog entries that name wave 9 as their
home. Left unscheduled they surface at T9.7, which has no room to fix anything.
The four colour items in it (BL-004/005/008/009) are now approved work.

T9.5's help-tip count corrected from 15 to 18 and dated: three were added during
waves 5 and 6 by tasks reusing the component as designed, each unreachable for
the same reason. Scheduling a broken component late makes every reuse cost more.

Closed without work: the free-text location migration. Every location on record
is sample data because no real list has been loaded, so there is nothing to
migrate. Recorded with the condition that invalidates it - the first real
project - so it is a decision rather than a surprise.

Items: D1 D2 D3 D4 D5 D6 D7 D8 D9 D10
Task: T7.0 (wave 7 prep)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-18 13:29:58 -05:00

5.5 KiB

Raw Blame History

Working rules — Work Package Suite

This repo is being changed against a fixed spec. Read IMPLEMENTATION.md before starting any task, and read the wave file for the task you are on. Do not work from this file alone.

The spec is the source of truth

Every change traces to an item ID (CR-001, F1, S1, A1, B1, C1, D1). If you are about to make a change that has no ID, stop. Either it belongs to an existing item and you should say which, or it is out of scope and should be logged in docs/waves/backlog.md instead of built.

Do not renumber, merge, or reinterpret item IDs. They are referenced in documents outside this repo that other people are reading. New scope decided mid-build gets a new ID rather than a widened old one - that is what the D prefix is for. See docs/waves/decisions-2026-08-18.md.

Scope discipline

One task per PR. Task IDs are T<wave>.<n>. Reference the task ID and the item IDs in the commit message and PR title.
Do not fix things you notice in passing. The codebase has known problems documented as S1 through S13, all scheduled. Fixing S6 while doing T3.2 makes the diff unreviewable and breaks the wave ordering. Log it, move on.
Do not reorder waves. The ordering is dependency-driven and documented in IMPLEMENTATION.md section 4. Waves 1 through 4 are prerequisites: they produce almost no visible change and every later wave assumes them.
Do not start a wave until the previous wave is merged, unless the task explicitly says it is independent.

Frontend and backend boundary

The UX review that produced F1-F6 and S1-S13 covered html/ only. Several change requests need server work and will be silently half-built if you treat them as frontend-only:

Item	Needs server work
CR-004, CR-018	Structured location storage and aggregate endpoints. Not localStorage.
CR-007	File upload, storage, and retrieval for drawing attachments.
CR-011, CR-014	Outbound email and a durable link target per work package.
CR-013	Material request persistence.
B4	Aggregate endpoints replacing localStorage-derived counts.

If a task touches one of these and you find yourself writing to localStorage, you are building the wrong thing. Say so and stop.

Things that must not change

These are recorded decisions, not oversights. Do not "clean them up":

Actual Hours stays in Closeout (CR-017). Its removal was proposed and rejected.
Localization stays (A7). admin.js language and time handling is a shipped feature.
Uppercase card headers in console.css stay (A5). The sentence-case rule applies to buttons and field labels only. The uppercase header idiom is deliberate.
The logged-override path for predecessors stays (A1). It is an audited business rule, not a bug. It is confirmEarlyRelease() in wp-creation-app.js, called from the issue and release paths. Named by function, not by line: this file and IMPLEMENTATION.md X2 both cited wp-creation-app.js:1962-1972 until Aug 18 2026, and those lines are deletePackage()/clearSaved() - a different rule entirely. Corrected before T7.3, which is the task told not to remove it.
Removed fields are hidden, not deleted (CR-002, CR-016). Retain the data and the model. Removal is expressed through the CR-006 section toggles.

The token rule

After wave 3 there is exactly one place a color, spacing or type value is defined. Page stylesheets alias that source and declare nothing new.

Adding a raw hex value to a page stylesheet is a defect regardless of what the task asked for. Four parallel token systems is what produced S5, and the .field-hint comment at work-package-suite-styles.css:336 is the bug that resulted. Do not recreate it.

Accessibility is in scope

Approved Aug 14, 2026 (C1). Any component you rebuild ships accessible or it is not done:

Interactive elements are <button>, <a>, or an input. Never a <div> with onclick. There are currently 12 <div> and 2 <span> click handlers app-wide; do not add a 15th.
Anything conveying instructions is reachable by keyboard and by touch. Hover-only is not acceptable — Field View runs on tablets.
Status changes and toasts announce through an aria-live region. login.html already does this correctly with role="alert" and role="status". Copy that pattern.
Focus is always visible. Do not use outline: none without a replacement of at least equal visibility.
Text meets 4.5:1 against its background, 3:1 for large text.

Verification

A task is not done because the code is written. Every task file lists its own done-when checks. In addition, for any task touching the frontend:

Run the app locally: uvicorn server.app:app against a throwaway SQLite database.
Exercise the affected flow at 390px and at 1440px. Field View at 390px is the gloved-hands surface and is where the worst rendering was found.
Capture before and after screenshots into the PR.
Run the existing smoke test. It signs in; server/seed_demo.py does not, which is S13.

If a done-when check cannot be verified, do not mark the task complete. Say which check failed and why.

Asking versus assuming

The four gating decisions are closed and recorded in IMPLEMENTATION.md section 2. Nothing else in the spec is a decision waiting to be made.

Where a task says "confirm with Nick", that is a product question, not an implementation blocker: build to the written acceptance criteria, and raise the question in the PR description. Do not invent a different behavior because the written one seems incomplete.

5.5 KiB Raw Blame History