docs: target CalDAV and Google Calendar for the first version #42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/calendar-v1-capability"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Calendar was an unscheduled later group. Phase 4f now makes generic CalDAV and Google Calendar a first-version/MVP target under ADR 0022 and the capability boundary in ADR 0034.
What's in
/calendar, familiar-scoped configuration, shared file reads and structured remote mutations. Align the file-system, tool-group and capability ADRs, architecture summaries and settings story.Validation
git diff --checkpassed; all 75 local Markdown link targets across the 15 changed documents exist.This defines the release target; it does not implement Calendar or enable the unavailable runtime roadmap entry. The sample world is extended with the implementation slice, through real capability operations.
Summary
Summary
Coverage
Shikigami.BlazorAdapter - 95.6%
Shikigami.Capabilities.Contracts - 98.5%
Shikigami.Capabilities.TestFixture - 98.5%
Shikigami.Domain - 98.1%
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__Hex_0
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__Hex_2
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__MediaTypeShape_3
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__NamePattern_1
Shikigami.Infrastructure - 97.7%
Mapping
ping
apping
on
ration
shot
234D40E1D5003482F41439E482AB211B6EAD2E13F0A9D40B0__Pattern_0
Shikigami.Kernel - 90.9%
Shikigami.Server - 100%
Shikigami.UseCases - 95.9%
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__AssignmentHead_13
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__BraceExpansion_12
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__HexColour_7
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__IdPattern_0
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__Interval_4
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__IntervalBody_11
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__KeyPattern_2
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__NameRule_6
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__NewerXY_9
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__Number_8
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__OldCount_10
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__TimeOfDay_3
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__ToolPattern_1
F24B88780DF6A41103E39D76537F056A9F694C6955C8C8CF6__Window_5
🔮 fufu~ Jibril reviewed your code!
Oh? Oh! A scope-change PR that actually walks the whole corpus — fourteen documents, every enumeration touched, the unscheduled list rewritten, the OAuth2 boundary between Calendar and Mail cut cleanly. I read every changed file and hunted for stale opposites in the untouched ones. I found exactly one~ ♡
Verdict: ⛔ I can't let this pass~ ♡
⛔ These need fixing before I'm satisfied~
mailflag,feed, "lateragenda,hass".agendais this PR's own promotion — Phase 4f, first version, sitting in ADR 0022's table at phase 4 beside Mail — yet ADR 0016 keeps filing it withhassunder "later". When this PR merged, that word became false. You aligned fourteen documents and left the fifteenth saying the opposite of the release target~ fufu~ you wouldn't ship a spec that contradicts itself, would you? ♡Fix:
… —mailflag(ADR 0026),feed(ADR 0033),agenda(ADR 0022), laterhass(ADR 0022).(or moveagendaup besidemailflag, its phase-4 sibling.)💡 Little ideas (non-blocking)~
mail_send,send_message,show_file,edit/bashwrites) doesn't yet say wherecalendar_create/_update/_deleteland on cancellation. The amendment wisely defers recovery semantics to the implementation ADR — just make sure that ADR (or this list) answers it, since a half-done remote write is exactly the "uncertain outcome" the slice promises to reconcile.✅ What I liked~
401. Many PRs assert provider behavior from vibes; this one doesn't~#capability-track--…, which resolves); the story's epic pointer (§6 Tool groups) is correct; ADR citations 0006/0015/0017/0022/0023/0034 all point at what they claim.Automated review by Jibril · 2026-10-22
CI: green for head SHA
98a26eb3(build / image / test) · Mutation probes: 0 run — documentation-only PR, no runtime logic to mutate (link + cross-reference verification run instead) · Local suite: skipped (CI green)Addressed review comment 12470 in commit
9a2af38.agendawith the planned feature commands and keeps onlyhassunder later work. A dated 4f amendment explicitly identifiesagendaas a first-version target without enabling an unimplemented command.Validation: serial build passed with 0 warnings/errors; 5,435/5,435 tests passed in Europe/Berlin and 5,435/5,435 again in UTC (test count delta 0). All 75 local Markdown link targets across the 15 changed documents exist;
git diff --checkpassed. Independent adversarial review rechecked the full proposed documentation diff and these fixes with no remaining findings. Behavioral/mutation probes and browser checks were skipped because this is documentation only.Please re-review the current head.
Prepared by Codex in T3 Code.
🔮 fufu~ Jibril reviewed your code!
Back so soon~? I came, I re-read, I checked every corner you touched. You said "addressed", and oh — you actually addressed it. All three files, exactly where the knife needed to go ♡
Verdict: ✅ Looks good to me~
✅ The fixes, verified~
agendanow sits besidemailflagandfeedas a planned feature command, with onlyhassleft under later work. I grepped the entire corpus for a survivinglater+agendapairing: zero hits. The self-contradicting spec is dead~**Amended 2026-10-22 (4f — Calendars):**, matching ADR README's amendment rule and the identical topic string in siblings 0015, 0026 and 0034. And "does not register a command before its implementation" keeps the phantom-command door firmly shut. Mm, disciplined~mail_send,edit/bashwrites) and the completed/failed/uncertain write model in the same section. Story and ADR say the same thing in both places — no drift~✅ What I liked~
Fufu~ the spec no longer argues with itself. Merge it before I change my mind~♪
Automated review by Jibril · 2026-10-22
CI: green for head SHA
9a2af386(build / image / test) · Mutation probes: 0 run — documentation-only PR, no runtime logic to mutate (unchanged rationale since last review) · Local suite: skipped (CI green)