What — a series of small, behaviour-preserving cleanups across the Node and Vue stacks: remove duplicated code, delete unused modules, and move a few oversized functions to the right layer.
Why — the same logic is currently copy-pasted in several places (in one case a security-relevant error-sanitising rule), so a fix in one copy silently leaves the others wrong. Nothing here changes runtime behaviour.
Scope — 10 sub-issues from a "simplify lens" audit (reuse · simplify · efficiency · altitude) run on 2026-07-28 against master. Findings were verified per-file; function ranges come from an AST parse, not lint line counts.
Two classes of sub-issue:
- Mechanical (7) — the change is fully specified: a helper already exists, or exactly one is missing.
- Derive-in-place (3) — the sub-issue states the diagnosis and the invariants that must survive, and the implementer reads the function to derive the change. These deliberately carry no code sketch: two independent review rounds found that every pre-written sketch encoded a wrong call signature (e.g. dropping a fallback argument that would downgrade a paying organization's plan). Read the code, do not trust a sketch.
Global constraints for every sub-issue:
- Behaviour-preserving. No change to an HTTP status, a response payload, a rendered attribute, a log string or an emitted event. If a refactor forces a behaviour change, stop and report.
- Branch off freshly-fetched
origin/master. Ranges cited in the sub-issues are master-relative.
- Coverage thresholds are gates, never lowered. One sub-issue = one PR.
Sequenced pairs (same files, merge best-first then rebase): T05 → T08 and T09 → T10.
Audit: spine x3
Scope: validated 2026-07-28
Created via /dev:issue
What — a series of small, behaviour-preserving cleanups across the Node and Vue stacks: remove duplicated code, delete unused modules, and move a few oversized functions to the right layer.
Why — the same logic is currently copy-pasted in several places (in one case a security-relevant error-sanitising rule), so a fix in one copy silently leaves the others wrong. Nothing here changes runtime behaviour.
Scope — 10 sub-issues from a "simplify lens" audit (reuse · simplify · efficiency · altitude) run on 2026-07-28 against master. Findings were verified per-file; function ranges come from an AST parse, not lint line counts.
Two classes of sub-issue:
Global constraints for every sub-issue:
origin/master. Ranges cited in the sub-issues are master-relative.Sequenced pairs (same files, merge best-first then rebase): T05 → T08 and T09 → T10.
Audit: spine x3
Scope: validated 2026-07-28
Created via /dev:issue