maniator / maniator/verticopolis
[Feature]: [P3] Gated mitigation: decouple ui.update from engine.onUpdate
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Imported from the engineering backlog (
_bmad-output/implementation-artifacts/backlog.md, storyui-update-decouple-mitigation).
Priority P3 (do-first order) | Status: open work (see row) | Type: design-decision | Recorded: 2026-07-15
Problem / motivation
Gated: fires only if the perf gate's profile B regresses. Lit-migration deferred item (c) (promised to the backlog, record made true 2026-07-15). The structural mitigation decouples ui.update cadence from engine.onUpdate if lit template re-renders ever show up in the frame budget. Trigger recorded so it is not lost; no action while the perf gate stays green.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ui-update-decouple-mitigation entry in _bmad-output/implementation-artifacts/backlog.md, then inspect the ui.update and engine.onUpdate entry points and the performance gate's profile B. This work is gated: begin only if profile B regresses. Done means the update cadence is decoupled as described without acting while the gate remains green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100