docs: define the context inspector and prompt assembly contract #46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/context-inspector-design"
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?
Define the Context inspector across ADRs 0009, 0021, 0023 and 0032, with its contracts and delivery work assigned to the existing library track and Phase 2 slices.
What's in
Validation
The UI and runtime described here are future implementation work, not a shipped inspector.
Summary
Summary
Coverage
Shikigami.BlazorAdapter - 95.2%
Shikigami.Capabilities.Contracts - 98.5%
Shikigami.Capabilities.TestFixture - 95.2%
Shikigami.Capabilities.TestFixture.UI - 100%
Shikigami.Capabilities.UI.Contracts - 91.3%
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 - 92.6%
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 pure documentation PR — nine Markdown files and not a single line of C#~ A contract defined before the implementation exists... fufu, that's my favorite kind of prey, and I hunted it properly: every cross-reference, every link, every ADR claim traced back to its source. You wouldn't believe how happy it makes me when the trail goes cold~ ♡
Verdict: ✅ Looks good to me~
I could not find a single contradiction. Not for lack of trying — I read all nine files in full and stalked every reference across the corpus:
✅ What I liked~
SeedDevDataTests+ the browser-test skill both exist where the plan now cites them.**Amended 2026-10-22 (Context inspector):**paragraphs, originals kept in place — exactly like the 2026-10-18 amendments before them). The ADR index and titles stay untouched, which is correct per convention.IAgentLoop over L1–L5 and L8— every dependency arrow points the right way~epochis an existing CacheLedger field, not a new invention.BlazorAdapter; calculation belongs toUseCases— which the plan already named as owner of "prompt assembly". Beautiful~Fufu~ you defined the contract before the code so the runtime never gets to hide its structure from the UI. "Provider serialization must not silently leave the manifest describing a different request" — yes, YES, that's the spirit! This time you escape unscathed~ ♡
Automated review by Jibril · 2026-10-22
CI: build ✓ / image ✓ / test stalled after 618 s — local full suite run instead (Release, CI's own flags): 5508 passed / 0 failed / 0 skipped · Mutation probes: 0 run — docs-only diff, no code to mutate · Local suite: green