Release: wave 11 + T13.2-T13.5 (D18 Okta sync), T13.1 held back until T14.1; mobile roadmap docs (BL-062..BL-069)

This commit is contained in:
2026-10-16 14:03:33 -07:00
37 changed files with 3311 additions and 347 deletions

View File

@@ -696,3 +696,124 @@ deliberately deferred.
- **Suggested wave or follow-up:** wave 14, alongside T14.1's badge changes:
do not show the badge on pages with nothing to sync, and keep it clear of
page controls.
<<<<<<< ours
### BL-069 - The sync has no cap on one run and no last-admin guard
- **Found during:** T13.3 (D18)
- **Where:** `server/okta_sync.py` `run_sync()`
- **What:** a run disables every account the rules select, however many. If the
identity attribute is partly wrong (it matches some accounts and not others),
one run can disable most of the company, including every admin. The
zero-match guard only stops the case where nothing matches. Disabled accounts
cannot sign in, so re-enabling needs an admin who is still active, or the
`manage_users.py` command line on the host.
- **Why not now:** D18 does not ask for it, and the right limit is a product
call: a count, a share of accounts, a rule that the last active admin never
disables, or all three.
- **Suggested wave or follow-up:** before the first live run, or in T13.6 if
Matt decides. Needs Matt.
=======
## Future build: mobile app and scaling
Logged 2026-10-12 from the meeting with Nick. The answers are in
`docs/waves/decisions-2026-10-12.md` (Q2 to Q14). The path from here to a
mobile version outside the VPN, across projects, is in
`docs/waves/roadmap-mobile-scaling.md`. These are features for a future
build. They have no wave and no `CR-`/`D-` id yet. Give each one an id when a
wave is planned. Items marked "to confirm" have an open question listed in the
decision file ("Still open"). Do not build them until it is answered.
Follow-up answers from Matt on 2026-10-12 are folded into the entries below.
Server work is needed for BL-062 to BL-066 (CLAUDE.md, "Frontend and backend
boundary"). Do not use `localStorage` as the store of record.
### BL-062 - Offline Field View for crews
- **From:** Q2, Q3
- **What:** Field View opens offline for up to **7 days** after the last sign-in
(today: 12 hours). Only crews in Field View work offline. The creator has no
offline mode. When the app opens online again and the account is disabled,
wipe that account's local data.
- **Why not now:** new scope. It needs an id, and it follows the outbox work in
wave 14 (T14.1 to T14.3).
- **Suggested wave or follow-up:** future mobile wave. Check it against the D18
session rules (idle timeout, absolute ceiling): a 7 day offline window and a
session ceiling must agree on what "signed in" means.
### BL-063 - Offline edit conflicts: merge, notify, log
- **From:** Q4
- **What:** When an offline edit meets a newer server version, the app merges
the two, shows a notification to the crew, writes a log entry, and updates the
owner. If both sides changed the same field, **the field value wins**, and the
app keeps a **history of changes**. This replaces the earlier default (keep
both, crew chooses).
- **To confirm:** who "the owner" is, how long the history is kept, and who can
read it. See the decision file, "Still open" item 2.
- **Suggested wave or follow-up:** same wave as BL-062.
### BL-064 - Field photo limits
- **From:** Q5
- **What:** a limit of **5 MB per photo**. This equals the D8 limit that the
server already enforces for drawings (`FILE_MAX_BYTES`), so photos can use the
same upload path and the same D19 download headers.
- **To confirm:** the count per package, and whether the app resizes a photo
before upload (phone photos are often 3 MB to 8 MB). Decision file, "Still
open" item 1.
- **Suggested wave or follow-up:** same wave as BL-062.
### BL-065 - Batch print and merged PDF
- **From:** Q6, Q7, Q8, Q9
- **What:** print many packages in one PDF.
- Limit: **25 packages on phones**. On desktop the user can scale the filter
up to 50 or 100. Open: who sets the larger value (each user, or an admin
setting). Decision file, "Still open" item 5.
- Drawings go **after the form**, in **upload order**, **scaled to fit**.
- SVG drawings are **left out**. A page names each file that was left out.
- Every page shows the **package number, the print date, and page X of Y**.
- **Related:** BL-000d (merge or list attachments on export) asked the same
question for CR-008. This entry answers the layout part of it.
- **Suggested wave or follow-up:** future print wave.
### BL-066 - Keep drawings when a package is deleted
- **From:** Q13
- **What:** deleting a package no longer deletes its drawings. Keep them for
data retention. **The storage quota is freed** when the package is deleted.
Storage will move to cloud storage in a future deployment. This replaces the
earlier default (delete with the package).
- **Today:** drawing bytes live in the Postgres `wp_files` table (CR-007, D8).
The 2 GB per project limit counts them. Kept files must not count toward that
limit, so the count has to change.
- **To confirm:** retention period, who can delete for good, who can recover.
See the decision file, "Still open" item 3.
- **Suggested wave or follow-up:** roadmap Phase 3 (object storage). It affects
D19 (safe download) paths too: recovered files must keep the attachment and
sandbox headers.
### BL-067 - Ready for QA progress weight is 0.85
- **From:** Q12
- **What:** change the progress weight for Ready for QA from 0 to **0.85**.
Today a package falls from 75% to 0% when it reaches Ready for QA.
- **Why not now:** it changes a shipped number on dashboards and roll-ups. Use
its own item id and re-run the roll-up checks.
- **Suggested wave or follow-up:** future wave. Small task.
### BL-068 - One cost-code list, kept in the SOP
- **From:** Q14
- **What:** the creator has 38 cost codes, the SOP has 39, and 13 differ. Keep
**one list, in the SOP**, and make the creator read it.
- **Blocked on:** the correct codes. The **PM** supplies them (decided
2026-10-12). The date is not set. This is a data question and not a code
question.
- **Related:** BL-019 (closed) made a stored code that has left the list stay
as an option. Keep that behavior when the list changes.
- **Suggested wave or follow-up:** future wave, after the codes arrive.
>>>>>>> theirs