Skip to content

[skip deploy] Specify exclusive end for Calendar CLI mutations - #114

Merged
pocketsharkk merged 1 commit into
mainfrom
codex/calendar-cli-exclusive-end-spec
Aug 14, 2026
Merged

[skip deploy] Specify exclusive end for Calendar CLI mutations#114
pocketsharkk merged 1 commit into
mainfrom
codex/calendar-cli-exclusive-end-spec

Conversation

@pocketsharkk

Copy link
Copy Markdown
Collaborator

What changed

  • add the decision-complete implementation spec for Exclusive End across Calendar CLI mutations
  • link the spec from the README roadmap
  • synchronize the CLI glossary with the canonical Calendar terms used by the contract

Why

event add and event set currently interpret all-day --end as inclusive, while the API, ICS, output, and event occurrence set use Exclusive End. The spec defines the v0.7 migration, cross-repository source ownership, rollout, rollback, validation, and implementation handoff without implementing the behavior.

Impact

Documentation only. No runtime, generated output, API surface, workflow, or deployment behavior changes in this PR.

WSPC Todo: tod_01M006KX9VBKKM8Y43SNNJZM4T

Validation

  • git diff --cached --check
  • verified the spec has exactly the six required top-level sections
  • verified the README roadmap link and glossary _Avoid_ entries
  • confirmed the diff contains only CONTEXT.md, README.md, and the new spec

Remaining acceptance

None.

@pocketsharkk
pocketsharkk marked this pull request as ready for review August 14, 2026 13:53
@pocketsharkk
pocketsharkk merged commit 436e2e5 into main Aug 14, 2026
3 checks passed
@pocketsharkk
pocketsharkk deleted the codex/calendar-cli-exclusive-end-spec branch August 14, 2026 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant