jpmschweitzerandClaude Opus 4.8
9be75d5592
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>
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.