3 Commits

Include renames

Author	SHA1	Message	Date
jpmschweitzerandClaude Opus 4.8	4bba2ef2f0	D-100 (fence dart:ffi) + amend D-32 (GitHub Actions); close T-384 ... - D-32 amended: Gitea-primary/not-activated → GitHub Actions, active (Linux test + Windows ConPTY/soak + release; web-WASM e2e withheld). The staged Gitea pipeline was never activated and is gone. - Q-50 resolved → D-100: FENCE the web/WASM target. Every dart:ffi importer goes behind a conditional-import facade with a web stub so `flutter build web --wasm` compiles; desktop fidelity untouched. Keeps the web "happy accident" alive as a hopeful future target per user. - T-438 filed for the fence implementation (12 ffi importers + CI wasm compile gate + re-enable e2e/ui targets). - T-384 closed (done): Gitea premise OBE, scripts repointed (2026-06-12), D-32 reconciled; the dead e2e targets delegated to T-438. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-15 16:29:11 +02:00
jpmschweitzerandClaude Opus 4.8	898a0316e5	claude: Bash live-tail detection + read-only file follower (T-325, core) ... The detection/follow core for the live-tail sub-card, with the UI wiring to follow. Claude Code runs every Bash tool itself and clide only sees the final tool_result block — we can't mirror the running process, so instead we detect a file-backed source the command follows and open our own read-only follower on the same file. - bash_tail_source.dart: detectBashTailSource() parses a Bash command for a single, safe, file-backed source (tail/cat/less with one file arg, inside the workspace via resolveUnderRoot). Returns null for a pipe-into-tail, a redirect, two files, or a path outside the repo — the caller then shows a "nothing to follow" note. bashHasTailIntent() gates WHEN the segment appears: v1 triggers on `tail`/follow-flags only, so ordinary cat/ls/git cards stay clean (cat/less remain detectable for later). - file_tail_follower.dart: a polling, read-only `tail -f`-style follower (no subprocess, no touching Claude's command) that emits the trailing window then appended deltas, and re-reads from the top on truncation. Tested: 19 parser cases (incl. the `git push | tail -25` and outside- workspace null cases), the intent predicate, and the follower (initial window / appended delta / missing file / rotation / start / stop). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-11 17:12:53 +02:00
jpmschweitzerandClaude	63195d1ec8	migrate DQR tree to governance/ layout (pql D-21) ... 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>	2026-05-11 18:34:20 +02:00