UX review: item 8's two are done, and this stack is deliberately not deployed
This commit is contained in:
@@ -944,7 +944,12 @@ two rounds of measurement, and nothing about the running app looked wrong.
|
|||||||
Untouched: 8, item 3's incremental half.)*
|
Untouched: 8, item 3's incremental half.)*
|
||||||
|
|
||||||
*(Ninth session: item 8's dismissal persistence and status-bar summary done —
|
*(Ninth session: item 8's dismissal persistence and status-bar summary done —
|
||||||
see the subsection under item 8. Two things to carry forward. First, **"the
|
see the subsection under item 8. **Not pushed and not deployed**, by choice:
|
||||||
|
`main` is at the merge `feat/settled-spans` **locally only**, and both gitea and
|
||||||
|
the VPS are still at `1aa3a14`. Nothing about it needs a migration or a backup —
|
||||||
|
it adds one read-only endpoint and touches no schema — so deploying it is
|
||||||
|
`git push` then `git pull && docker compose up -d --build`, whenever it's
|
||||||
|
wanted. Two things to carry forward. First, **"the
|
||||||
server already does this" is not the same as "Petal does this"**: every
|
server already does this" is not the same as "Petal does this"**: every
|
||||||
suppression the item asked for was in place and tested, and the defect lived
|
suppression the item asked for was in place and tested, and the defect lived
|
||||||
entirely in the 250 ms pass that by design never asks the server. Any item
|
entirely in the 250 ms pass that by design never asks the server. Any item
|
||||||
|
|||||||
Reference in New Issue
Block a user