Files

T

jpmschweitzerandClaude Opus 4.8 9be75d5592 clean-house: fix 37 stale DQR cross-links; sort architecture.md decisions

clean-house sweep over governance/ (validate green, 0 broken refs before
and after):

- RULE-ANCHOR-DRIFT (37): rewrote inline cross-reference links left over
  from before the decisions/questions/rejected subdir split — flat naming
  (questions-architecture.md, questions-process.md, rejected.md) and bare
  same-dir paths that were actually cross-type — to canonical
  subdir-relative form with current slugs. pql resolved these by ID so they
  were never broken to the tooling, only to GitHub anchor navigation.
- RULE-RECORD-SORT (1): reordered decisions/architecture.md D-records to
  strictly ascending (the D-1..D-6 block had been appended after D-41); pure
  block move, line count unchanged, content identical.
- RULE-FILE-OVER-THRESHOLD: deferred (architecture.md 435 > 350; splitting
  would re-churn the anchors just fixed).
- EOF/whitespace and Q↔D backlinks clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-06 12:50:27 +02:00

2.9 KiB

Raw Permalink Blame History

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-dart is archived. nielsenko/tree-sitter-dart is the maintained fork. Do we pin nielsenko/, 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 CustomPainter catalogue (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.yaml and 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 prefixed ext_<id>_…) or stay on the kernel.settings key/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.

2.9 KiB Raw Permalink Blame History