| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | docs: add the ticket save-model v2 spec | Craig Jennings | 2026-05-25 | 1 | -0/+2 |
| | | | | | | | The v2 spec folds the structured fields — priority, state, assignee, labels — onto the save engine and removes immediate push, so the package has one write path instead of two. It extends the shipped v1 save-model spec and supersedes the "field setters stay immediate" half of v1 decision 8. I incorporated two Codex review rounds. I also added the supersession pointer to the top of the v1 spec so the v1/v2 relationship is legible from either file. | ||||
| * | docs: title-case the section headings in the save-model spec | Craig Jennings | 2026-05-24 | 1 | -8/+8 |
| | | |||||
| * | docs: add the ticket-save-model and multi-account specs | Craig Jennings | 2026-05-24 | 1 | -0/+253 |
| Two design specs for upcoming work. ticket-save-model-spec covers the unified "save the ticket" model — diff title/description/comments against their provenance hashes and push only what changed, with a sequential conflict-aware engine and an opt-in keymap — and went through two review rounds (Codex). multi-account-spec covers switching between work and personal Linear workspaces over the existing globals, with auth-source credentials and per-account cache isolation; it's still pre-review draft. | |||||
