DD-338 Phase B.2 — caldav-blade-mcp catalog flips (1 stable + 5 unsorted)#21
Merged
Conversation
…ted) Flip 6 deterministic_ordering declarations on caldav-blade-mcp tools per the DD-338 Phase B.2 spec (architect-approved 2026-05-23): - cal_info: unstable → stable (single-record per B.1.a precedent) - cal_calendars: unstable → unsorted (honest multi-provider declaration) - cal_events_batch: unstable → unsorted - cal_search: unstable → unsorted - cal_today: unstable → unsorted - cal_week: unstable → unsorted The honest-unsorted declaration mirrors the cf_d1_query architect-ratified precedent from B.1.b — where the blade cannot honestly fulfil the deterministic contract (no atomic cross-provider sort guarantee), declare set semantics rather than fake-comply with an internal sort. Assembler downstream is responsible for canonical ordering with provenance. OQ-1 (PRIMARY) RATIFIED: honest-unsorted across all 5 multi-record tools; no bounded-wait rewrite. OQ-2 RATIFIED NO: no defensive in-blade sort under unsorted declaration. OQ-3 RATIFIED YES: cal_calendars partial-tolerance softening lands in the paired caldav-blade-mcp PR. Convention #23 reader-audit advances 43 → 44 migrated blade-tool-sets on merge of both paired PRs. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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.
Summary
Catalog-side of DD-338 Phase B.2. Paired with
caldav-blade-mcpPR #1 (source-side changes + tests).Six
granularity.deterministic_orderingflips oncaldav-blade-mcp.json:cal_infounstablestablecal_calendarsunstableunsortedcal_events_batchunstableunsortedcal_searchunstableunsortedcal_todayunstableunsortedcal_weekunstableunsortedHonest-degraded-declaration precedent
The
unsorteddeclarations mirror the architect-ratifiedcf_d1_queryprecedent from B.1.b (joined bytailscaletag-filterclient-side). Where the blade cannot honestly fulfil the deterministic contract, declare what you actually deliver — set semantics — rather than fake-comply with an internal sort. The assembler downstream is responsible for canonical ordering with full provenance.DD-338 honest-degraded-declaration registry now has three entries:
cf_d1_query—unstable(user-supplied SQL precludes blade-side reorder)tailscaletag-filter —client-side(server returns full set; blade filters in-process)cal_*multi-provider (this PR) —unsorted(cross-provider interleave is honest-set)Architect OQ locks honoured
unsorteddeclaration ✅Test plan
npm testgreen: 164/178 passing (14 skipped, 0 fail) afternode scripts/build-forge-context.jsscope_filteringoraudit_surfacedeclaration (out of scope for B.2)Convention #23 reader-audit advances 43 → 44 migrated blade-tool-sets on merge of both paired PRs.
🤖 Generated with Claude Code