Source: Audit section 6 (coverage caveat). The 2026-07-20 spec audit verified all engine/persistence specs claim-by-claim, but the UI micro-behaviour specs were only checked structurally (views exist, enums match, key configs present).
Not yet verified line-by-line:specs/sidebar_views.allium (814 lines — per-view content, filters, date formatting, auto-load at 0.9 threshold), specs/editor_misc.allium (797 — dashboard, menu editor, metadata diff view, git diff view), specs/layout.allium (shell, activity bar, status bar, panels), specs/tabs.allium (detailed open/replace/pin/close semantics), specs/modals.allium, specs/editor_post.allium, specs/editor_media.allium, specs/editor_settings.allium, specs/editor_tags.allium, specs/editor_chat.allium, specs/editor_script.allium, specs/editor_template.allium, specs/ui_data_flow.allium, specs/tui.allium panel details, specs/template_context.allium field-by-field.
Task: For each spec file: extract every rule/invariant/@guarantee, verify against crates/bds-ui/src (and crates/bds-server/src/tui.rs for tui.allium), running the app where static reading is insufficient. Where behaviour diverges, check ../bDS2 (lib/bds/desktop, lib/bds/ui) as golden master and file one issue per confirmed divergence, referencing spec lines and code locations (same format as the issues from the engine audit). Do not change code in this pass.
Acceptance: A report listing per-spec verification status and filed follow-up issues for every divergence found.
**Source:** Audit section 6 (coverage caveat). The 2026-07-20 spec audit verified all engine/persistence specs claim-by-claim, but the UI micro-behaviour specs were only checked structurally (views exist, enums match, key configs present).
**Not yet verified line-by-line:** `specs/sidebar_views.allium` (814 lines — per-view content, filters, date formatting, auto-load at 0.9 threshold), `specs/editor_misc.allium` (797 — dashboard, menu editor, metadata diff view, git diff view), `specs/layout.allium` (shell, activity bar, status bar, panels), `specs/tabs.allium` (detailed open/replace/pin/close semantics), `specs/modals.allium`, `specs/editor_post.allium`, `specs/editor_media.allium`, `specs/editor_settings.allium`, `specs/editor_tags.allium`, `specs/editor_chat.allium`, `specs/editor_script.allium`, `specs/editor_template.allium`, `specs/ui_data_flow.allium`, `specs/tui.allium` panel details, `specs/template_context.allium` field-by-field.
**Task:** For each spec file: extract every rule/invariant/@guarantee, verify against `crates/bds-ui/src` (and `crates/bds-server/src/tui.rs` for tui.allium), running the app where static reading is insufficient. Where behaviour diverges, check `../bDS2` (lib/bds/desktop, lib/bds/ui) as golden master and file one issue per confirmed divergence, referencing spec lines and code locations (same format as the issues from the engine audit). Do not change code in this pass.
**Acceptance:** A report listing per-spec verification status and filed follow-up issues for every divergence found.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Source: Audit section 6 (coverage caveat). The 2026-07-20 spec audit verified all engine/persistence specs claim-by-claim, but the UI micro-behaviour specs were only checked structurally (views exist, enums match, key configs present).
Not yet verified line-by-line:
specs/sidebar_views.allium(814 lines — per-view content, filters, date formatting, auto-load at 0.9 threshold),specs/editor_misc.allium(797 — dashboard, menu editor, metadata diff view, git diff view),specs/layout.allium(shell, activity bar, status bar, panels),specs/tabs.allium(detailed open/replace/pin/close semantics),specs/modals.allium,specs/editor_post.allium,specs/editor_media.allium,specs/editor_settings.allium,specs/editor_tags.allium,specs/editor_chat.allium,specs/editor_script.allium,specs/editor_template.allium,specs/ui_data_flow.allium,specs/tui.alliumpanel details,specs/template_context.alliumfield-by-field.Task: For each spec file: extract every rule/invariant/@guarantee, verify against
crates/bds-ui/src(andcrates/bds-server/src/tui.rsfor tui.allium), running the app where static reading is insufficient. Where behaviour diverges, check../bDS2(lib/bds/desktop, lib/bds/ui) as golden master and file one issue per confirmed divergence, referencing spec lines and code locations (same format as the issues from the engine audit). Do not change code in this pass.Acceptance: A report listing per-spec verification status and filed follow-up issues for every divergence found.
this would just redo everything again that was done multiple times. time waste.