Nabatable Fullstack Delivery

• Update the canonical path, not a duplicate path.
• Reuse the real production component/client path in tests instead of helper replicas whenever possible.
• Keep shared state and business rules centralized.
• Prefer existing repo patterns over new abstractions.

Testing Rules

• Use focused tests that exercise the real behavior under the actual component or route path.
• If you cannot write RED-first for a regression because the first step is confirming existing production behavior, say so explicitly.
• Passing tests alone are not enough if the task requires proof of an interactive or cross-surface state transition.

Verification Rules

• Use $nabatable-ui-proof for UI changes that need browser evidence.
• For non-UI changes, record the exact automated proof path used.
• If a verification requirement could not be completed, capture the blocker and the compensating evidence instead of silently downgrading the claim.

Done Criteria

• The change landed in the canonical path.
• The chosen delivery mode matches the task type and is documented honestly.
• Tests and verification prove the requested behavior rather than a nearby approximation.