docs: remove PDF processing from product scope #80
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/remove-pdf-processing"
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?
PDF processing has no established familiar use case and is removed from product scope entirely. ADR 0030 now treats PDFs as ordinary stored, downloadable binary attachments, without extraction, OCR or model-facing page input.
Removes text extraction from Phase 2f, page input from Later, the L9 File parts dependency, and the PdfPig candidate. Reconciles ADRs 0004 and 0021, the requirements and the chat story. Generic binary storage/download behavior and mail attachment examples stay valid.
Validation: independent adversarial review approved the complete six-file diff with no findings; git diff --check passed; all 42 local Markdown links resolve; repository-wide searches found no remaining PDF-processing promises or L9 prerequisites. Executable tests, mutation probes and browser verification were skipped because this change is documentation-only.
Summary
Summary
Coverage
Shikigami.BlazorAdapter - 96.9%
Shikigami.Capabilities.Contracts - 100%
Shikigami.Capabilities.TestFixture - 95.6%
Shikigami.Capabilities.TestFixture.UI - 100%
Shikigami.Capabilities.UI.Contracts - 91.3%
Shikigami.Capabilities.Web - 97.1%
Shikigami.Domain - 98.2%
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__Hex_0
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__Hex_2
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__MediaTypeShape_3
916AED265A903CAC15169BB5EE676ADBEFE655D493DD7AC75__NamePattern_1
Shikigami.Infrastructure - 95.1%
Mapping
ping
apping
on
ation
ration
ts
shot
234D40E1D5003482F41439E482AB211B6EAD2E13F0A9D40B0__Id_1
234D40E1D5003482F41439E482AB211B6EAD2E13F0A9D40B0__Pattern_0
Shikigami.Kernel - 90.9%
Shikigami.Server - 86.4%
Shikigami.UseCases - 96.3%
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? A scope-execution PR — six files, +13/−14, not one line of C# touched. You have no idea how rare it is to see a docs-only change that actually reconciles every artifact it touches. So I got out my magnifying glass and went hunting for the corpse the removal leaves behind~ ♡
Verdict: ✅ Looks good to me~
I could not find a single orphan. Not one! Do you know how disappointing that is for a yandere reviewer? (…delightful. It's delightful~ ♪)
What I verified myself — not what the PR description told me:
pdfacross all docs leaves exactly three benign survivors — this PR's own amendment text in ADR 0030, the reconciled story line, andinvoice.pdfas a path example in ADR 0026's mail story (an ordinary binary attachment; correctly untouched).L9→ zero hits anywhere.PdfPig→ zero.as pages/page markers/.pdf.mdcompanion /report.pdf (12 pages)/free parser→ all zero. The extraction truly is dead, not merely moved~annotation/file part/video_url/parsedhave zero residual hits in that ADR.[Later]line, PROJECT_PLAN 2f, the Later list, and the chats story acceptance criterion all now say the same thing as ADR 0030's table row ("PDFs, video, archives, other binaries → stored and listed as attachments only"). The amendment block follows the sibling pattern set by the 2026-10-22 amendment in the Generation section — placed inline where the decision lives. ♡git diff --checkclean too.✅ What I liked~
invoice.pdf) staying valid untouched — surgical restraint about what doesn't change.No blocking issues, and I refuse to invent a fake suggestion just to look busy — there is genuinely nothing to fix here~
Automated review by Jibril · 2026-10-24
CI: green for head SHA
4f6f6eaf(build, image, shell-eval, test) · Mutation probes: 0 run, 0 survived — skipped, documentation-only diff, no executable logic to mutate · Local suite: skipped (CI green)