The po agent splits a large idea into specs, records the split, order and
cross-spec decisions in docs/epics/E<NN>-<slug>.md, and keeps the epic
current as each spec is written. The architect reads a spec's epic so the
contract does not block a later spec. Every phase after the spec still
works on one spec.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@@ -0,0 +53,4 @@
+  is short.
+- The architect keeps a running numbered list. Decisions are summarised again in full at
+  the start of Phase 3, as before.
+- The `po` agent is unchanged. Whether it should work the same way is a separate decision.

@@ -66,0 +76,4 @@
+ * Read-only: never sent in a request. Does not extend AbstractDto — it is a reference to a
+ * user, not an editable entity, so `version` does not apply.
+ */
+export interface CompactUserDto {

@@ -66,0 +103,4 @@
+ * never from the `error` text.
+ * See `docs/adr/2026-09-27-required-error-code.md`.
+ */
+export const ErrorCode = {

@@ -0,0 +40,4 @@
+ * Kind of a reason why an item is on a list — see `ShoppingListItemReasonDto`.
+ * Designed to grow: spec B of epic E01 adds a meal-plan kind.
+ */
+export const ShoppingListItemReasonKind = {

@@ -0,0 +50,4 @@
+/**
+ * Result of POST /shopping-list/:id/item/add.
+ */
+export const AddShoppingListItemOutcome = {

@@ -0,0 +107,4 @@
+  /** Whether the item is ticked off. Always present. Read-only — changed via the tick/untick routes. */
+  ticked: boolean;
+  /** ISO-8601 timestamp of the last tick. Present only when `ticked` is true. Read-only. */
+  tickedAt?: string;

@@ -0,0 +227,4 @@
+  version: number;
+}
+
+/** Request body for POST /shopping-list/:id/item/:itemId/move. */

@@ -0,0 +283,4 @@
+  },
+
+  /**
+   * POST /shopping-list/:id/load

@@ -0,0 +381,4 @@
+  },
+
+  /**
+   * POST /shopping-list/:id/item/add

@@ -0,0 +410,4 @@
+  },
+
+  /**
+   * POST /shopping-list/:id/item/:itemId/edit

@@ -0,0 +434,4 @@
+  },
+
+  /**
+   * POST /shopping-list/:id/item/:itemId/tick

@@ -0,0 +16,4 @@
+`TagDto.createdByUser`. `UserDto` carries `email` and `role`, so every reader of a comment and
+every recipient of a shared meal plan receives other users' email addresses.
+
+The name for the reduced type came up too. A first proposal was `UserSummaryDto`. The contract

@@ -0,0 +22,4 @@
+
+## Decision
+
+A reduced view of an entity is named `Compact<Entity>Dto`. Any response that shows a user

@@ -0,0 +191,4 @@
+
+## Affected Repos
+
+Filled in by the cross-cutting architect and approved at GATE A — leave as is when writing