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>
1.5 KiB
1.5 KiB
Open Questions — Extensions
Extension API shape, Lua runtime vendoring, manifest schema version.
Q-8: Extension API shape — widgets, subcommands, both?
- Status: Open
- Question: Should extensions contribute widgets (panels, tabs, status-bar items), subcommands (CLI verbs), or both? Both is the obvious answer but has a cost in API surface that must be designed carefully to satisfy user/Claude parity (D-6).
- Context: CLAUDE.md flags this as "decide during Tier 6."
builtin.*stubs today contribute widgets + commands + keybindings; the third-party Lua contract has to match. - Source: CLAUDE.md "Open questions" footer.
Q-9: Lua runtime vendoring
- Status: Open
- Question: Does the Lua supporter tool (D-19) bundle liblua source (build with the binary) or link system liblua (smaller binary, fragile ABI)?
- Context:
ptychas no deps; Lua is different — it's a whole VM. Bundling is the straightforward choice but locks a Lua version per clide release. - Source: 2026-04-21 planning.
Q-10: Extension manifest schema_version:
- Status: Open
- Question: What's the manifest schema-version scheme and bump policy? Coupled with Q-5 (IPC wire format) — both want a versioning story.
- Context: Today's manifests have no
schema_version:. Adding one is cheap; the hard part is deciding when we bump. - Source: 2026-04-21 planning.