jpmschweitzerandClaude Opus 4.6
2235cc4c19
pql 1.2.0 changed its record format to drop leading zeros. All 262 references across 18 files renumbered (D-001→D-1, T-043→T-43, etc.). pql-plan.json export updated as the git source of truth for the planning database. DB rebuilt via pql plan import. Co-Authored-By: Claude Opus 4.6 (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.