jpmschweitzerandClaude
63195d1ec8
test / unit + widget + golden + a11y (push) Failing after 31s
test / integration_test (xvfb) (push) Has been skipped
test / bundle smoke (xvfb 5s) (push) Has been skipped
test / daemon subprocess + web WASM smoke (push) Has been skipped
test / dart doc (lib API) (push) Failing after 1m2s
pql 1.4.30 introduces a per-type subdirectory layout for decision
records: governance/{decisions,questions,rejected}/<domain>.md. The
parser infers record type from the parent subdir and domain from
the filename stem, replacing the flat decisions/<file>.md layout
with questions-X and rejected prefixes.
Moves:
- 6 D-files to governance/decisions/ (accessibility, architecture,
extensions, process, testing, tooling)
- 5 Q-files to governance/questions/ (stripped the questions- prefix)
- rejected.md split by domain to governance/rejected/{architecture
(5), process (4), accessibility (1), testing (1)}.md — split per
cross-reference target.
Drops:
- decisions/README.md (auto-regenerated as governance/README.md by
pql init below the records marker)
- decisions/questions.md (hand-curated index pointing at the per-
domain files; redundant once pql generates the index, and the
"load-bearing" curation was already present in each Q-record's
Context field).
Convention-driven; not a clide-specific change. Counts unchanged
across migration: 106 decisions, 95 tickets, 134 refs, 0 broken.
Co-Authored-By: Claude <noreply@anthropic.com>
2.9 KiB
2.9 KiB
Open Questions — Process + Tooling
Editor tab, tree-sitter, icon set, theme hot-reload, kernel DB access.
Tooling-domain questions currently live here too. Split into
questions-tooling.md if this file outgrows ~350 lines.
Q-15: Editor tab — full LSP vs tree-sitter-only highlight
- Status: Open
- Question: Tier 2's editor tab: do we integrate a full LSP story (analyzer server + hovers + completions + diagnostics) or ship tree-sitter-only syntax highlighting and defer LSP to Tier 6?
- Context: Full LSP is a large subsystem; tree-sitter is a weekend. User is a heavy LSP user in other IDEs — missing it hurts. CLAUDE.md flags this as "decide during Tier 2."
- Source: CLAUDE.md "Open questions" footer.
Q-16: tree-sitter-dart grammar maintenance
- Status: Open
- Question:
UserNobody14/tree-sitter-dartis archived.nielsenko/tree-sitter-dartis the maintained fork. Do we pinnielsenko/, mirror it in-repo, or lean on the Dart analyzer's own semantic output and skip tree-sitter for Dart? - Context: If tree-sitter is the Tier-2 answer (Q-15), grammar sourcing matters.
- Source: 2026-04-21 planning.
Q-17: Icon set growth
- Status: Open
- Question: Hand-drawn
CustomPaintercatalogue (total control, pixel-perfect on every theme, slow to grow) vs SVG + parser (faster to grow, one more dep, theming is harder)? - Context: We rejected Nerd-font glyphs (R-6); something has to fill the gap.
- Source: 2026-04-21 planning.
Q-18: Theme hot-reload in release builds
- Status: Open
- Question: The theme picker supports live-reloading a YAML during development. Does the same path stay open in release builds (user tweaks
~/.config/clide/themes/foo.yamland the app re-reads on focus) or is release-build theming restricted to built-in + settings-UI-installed themes? - Context: Hot-reload is powerful for theme authoring but opens a file-watch + re-parse path in release code.
- Source: 2026-04-21 planning.
Q-19: (withdrawn)
- Status: Resolved → n/a
- Note: Earlier floated as "ticket markdown mirror vs SQLite" — no longer a split question. Markdown mirror is tracked in Q-22; SQLite is the current stopgap per D-40.
Q-20: Kernel DB service — namespaced SQL access?
- Status: Open
- Question: Do extensions get namespaced SQL access to
.clide/clide.db(tables prefixedext_<id>_…) or stay on thekernel.settingskey/value facade? Admission-level question (D-12). - Context: Some extensions (tickets, canvas, graph) naturally want relational storage. K/V gets awkward fast.
- Source: 2026-04-21 planning.