chore: auto-commit ticket changes before merge

Author: JoeOakhartNava

.tickets/w21-ablv.md

@@ -33,6 +33,10 @@ parent: dso-0k2k
   ← Satisfies: cross-story contract (adversarial review)
 - When this story is complete, the reducer's event ordering contract is defined and documented (filename sort with timestamp prefix, deterministic tie-breaking for same-second events)
   ← Satisfies: cross-story contract (adversarial review)
+- When this story is complete, every `ticket` command auto-initializes if `.tickets-tracker/` does not exist — `ticket init` runs silently on first use, making initialization transparent to the user
+  ← Satisfies: "transparent first-use initialization"
+- When this story is complete, `ticket init` generates a unique environment ID (UUID) at `.tickets-tracker/.env-id` (gitignored on the tickets branch) that is embedded in every event for cross-environment conflict resolution
+  ← Satisfies: cross-environment identity for Epic 2 conflict resolution
 - When this story is complete, unit tests are written and passing for all new logic
 
 ## Considerations

.tickets/w21-o72z.md

@@ -25,8 +25,8 @@ parent: dso-0k2k
 
 - When this story is complete, `ticket list` compiles all tickets via the reducer and returns their current state
   ← Satisfies: "ticket list works correctly"
-- When this story is complete, `ticket transition` appends a STATUS event and auto-commits
-  ← Satisfies: "ticket transition works correctly"
+- When this story is complete, `ticket transition <id> <current_status> <target_status>` requires both current and target status. The command acquires flock, reads actual state, rejects with the actual state if it doesn't match the provided current_status, and only writes the STATUS event if the precondition holds. This ensures agents always prove they know the starting state before changing it.
+  ← Satisfies: "ticket transition works correctly" + optimistic concurrency control
 - When this story is complete, `ticket comment` appends a COMMENT event and auto-commits
   ← Satisfies: "ticket comment works correctly"
 - When this story is complete, non-CREATE commands verify the target ticket has a CREATE event and fail fast with a clear error if not