You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three new structure rules: boundary conversion earns its types (no enum that mirrors domain cases just to serialize; one bespoke format encodes in the request DTO; a deliberately shared multi-type field uses a format-shaped Encodable value with string, array, number and null cases, converted in the network layer, supported cases only), meaning visible at the boundary (named values for cohesive multi-value payloads such as AnswerSubmission(answer, questionID, sessionID), labelled tuples for light local cases, domain payloads kept apart from wire DTOs), and grouping by responsibility (properties and methods grouped by their job, blank lines between real stages inside functions, Swift member ordering within semantic groups).
New test rule: assert the final wire output, including explicit JSON null, not the internal conversion steps.
Later rules renumbered: structure 6–15, screen state 16–21, tests 22–26. The core five rules and the DI guidance are unchanged.
wrap-up
The wrap-up now presents numbered choices for completed work, unfinished work and live state, and resumes only what the user explicitly selects.
Selected context survives a session clear in a locally excluded, uncommitted HANDOFF.md; entries leave it only once resolved or saved to an approved persistent record.