jpmschweitzerandClaude
1151a0ce80
First child of T-89. Codifies "don't make coverage worse" as a durable pre-push contract before any test-writing children land. - pubspec.yaml: new `coverage_floor: 34` key. Single source of truth for the floor; ratchets up only. - ci/coverage_gate.sh: parses coverage/lcov.info (LH/LF), reads the floor from pubspec.yaml, exits non-zero if integer-truncated measured % drops below it. Self-contained awk parser — no `lcov` CLI dependency. - ci/test.sh: flutter test now runs with --coverage, so the gate reads fresh data without an extra test invocation. Wall time delta is small and stays inside the < 90 s pre-push budget (D-29). - Makefile: new `coverage-gate` target wires the script in; `push-check` adds it as a dependency. The .githooks/pre-push hook (already wired) picks this up automatically. - .gitignore: ignore /coverage/ wholesale; the floor lives in pubspec.yaml, nothing under coverage/ is committed. Decision recorded as D-66 (decisions/testing.md). End target is 95%; reaching it is tracked as the rest of T-89's children. Co-Authored-By: Claude <noreply@anthropic.com>
Decisions
Confirmed decisions, open questions, and rejected alternatives for clide.
Decisions are split by domain. When unsure where a record belongs: if it constrains how we build, it's architecture. If it defines what ships to users, it's extensions / accessibility. If it defines how we verify, it's testing. If it defines what the toolchain looks like, it's tooling. If it defines how the team works, it's process.
Cross-domain records live in one file with [D-NNN]-shaped cross-
references in related files. Split threshold: when any file exceeds
~350 lines, review whether it should split (see settled-reach's
questions-*.md split pattern for precedent).
Domain files
| File | Domain |
|---|---|
| architecture.md | Core, rendering, IPC, kernel, panel manager |
| extensions.md | Extension contract, Lua runtime, grain, contribution points |
| accessibility.md | A11y + i18n policy, WCAG gates |
| testing.md | Test pyramid, drivers, client-side constraint |
| tooling.md | Toolchain, supply chain, CI, ignore strategy |
| process.md | Q&D system, kanban, commit conventions, changelog |
| rejected.md | Rejected alternatives across all domains |
| questions.md | Master index of open questions |
| questions-architecture.md | Architecture Qs |
| questions-extensions.md | Extension Qs |
| questions-accessibility.md | A11y / i18n Qs |
| questions-testing.md | Testing Qs |
| questions-process.md | Process + tooling Qs |
Record shape
Confirmed decisions (D-NNN):
### D-NNN: Short title
- **Date:** YYYY-MM-DD
- **Decision:** one-sentence summary, then details.
- **Rationale:** why this over alternatives.
- **Cost:** known downsides / what we're accepting.
- **Raised by:** who proposed / endorsed.
Domain-specific fields (Kill switch:, Evaluation reports:,
Amendment:, Cross-reference:) are additive. Amendments are inline
and dated: **Amendment (YYYY-MM-DD):** …. Cross-references use
markdown anchor links with the full slug:
[D-5](architecture.md#d-5-dart-core-ptyc-peer).
Open questions (Q-NNN):
### Q-NNN: Short question-form title
- **Status:** Open | Partially resolved → [D-NNN] | Resolved → [D-NNN]
- **Question:** ...
- **Context:** ...
- **Assigned to:** (optional)
- **Source:** (optional)
Rejected alternatives (R-NNN):
### R-NNN: Short rejected-option title
- **Rejected:** YYYY-MM-DD
- **Reason:** ...
- **Cross-reference:** [D-NNN] (what was picked instead)
Claiming an ID
Until the pql planning subcommands land (Q-21),
claim IDs by inspecting the highest existing D-NNN / Q-NNN /
R-NNN in the target file and incrementing.
Once pql decisions claim D <domain> "title" exists, use that —
same semantics, no race on concurrent sessions.
Querying
pql decisions … reads decisions/*.md and writes .pql/pql.db
(gitignored; markdown is the source of truth).
Common queries:
pql decisions list --type confirmed --domain architecture
pql decisions show D-5 --with-refs
pql decisions coverage # D-records without tickets
pql decisions validate # pre-push parser gate
pql ticket board # kanban view of tickets
Adding a decision
- Edit the appropriate domain file.
- Follow the record shape above.
- Run
pql decisions validate(also runs inmake push-check). - Commit. The SQLite index rebuilds from markdown on any
pql decisions sync.