Repository navigation
docs: correct what the docs claim the pipeline does - #26
Merged
Merged
Conversation
The API reference still described the pre-0.6.0 pipeline — busy times always merged, padding applied after — which is the exact model the maxOverlaps bug lived inside. Under maxOverlaps they are deliberately not merged, because the count is how many busy times cover a moment and merging two into one interval caps that count at one. It also said slots align to slotSplit boundaries when offset is zero. They do not: they start at the beginning of the search range. And it defined maxOverlaps as 'traditional behavior applies', a phrase defined nowhere; it now says what the option is for, which is capacity — three people who can each take a meeting is maxOverlaps: 2. The availability guide gains the wall-clock rule, ARCHITECTURE stops listing two files that do not exist, and CLAUDE.md stops naming ESLint and Prettier for a repo that uses Biome, or pinning a version five minors old. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs-only, no code changes. Each of these was verifiably wrong rather than merely thin.
docs/api-reference.mdmaxOverlapsbug lived inside: undermaxOverlapsthey are deliberately not merged, because the count is how many busy times cover a moment and merging two overlapping ones caps it at one.slotSplitboundaries whenoffsetis 0. They do not — they start at the beginning of the search range.maxOverlapswas defined as "traditional behavior applies", a phrase defined nowhere. It now says what the option is for: capacity. Three people who can each take a meeting ismaxOverlaps: 2.docs/availability-scheduler.md— the wall-clock rule, which is what 0.7.1 changed.ARCHITECTURE.md— stops listinginternal.types.tsanderrors.ts, neither of which exists.CLAUDE.md— stops naming ESLint and Prettier for a repo that uses Biome, and stops pinning a version five minors out of date.Version bumped to 0.7.2 because
version-checknow runs on every PR and requires a version ahead of npm — a consequence of the change in #24. Publishing is a separate step; this does not release itself.Untracked and left alone:
NPM_PUBLISH_SETUP.mdandRELEASE_SECURITY.mdstill describe theNPM_TOKENflow that OIDC replaced. They are not in the repo, so they are local residue worth deleting.🤖 Generated with Claude Code