chore: untrack the build logs that were triggering full CI runs

[rubenvdlinde]

build.log, lint.log, inst.log, stylelint.log, test_unit.log and
changed.tsv are transcripts written at the repo root by local tooling, and
they were tracked. Every local build therefore produced a real diff, and
every one of those commits triggered the full 34-job Code Quality suite.

In a 60-commit sample of recent fleet pushes, 58% touched no .php, .js,
.ts or .vue file at all — generated artefacts like these, plus l10n
writebacks, were the bulk of it. Each still ran six PHPUnit legs and a
16-minute Playwright suite.

Scope

Root-anchored (/*.log, /changed.tsv) on purpose. A bare *.log rule
would also reach .claude/skills/*/examples/{pass,fail}.log, which are gate
fixtures — the evidence those skills assert against — and must stay tracked.

Files removed from tracking in this repo are listed in the commit. Nothing that
is not a generated transcript is touched.

Removed here

• build.log
• changed.tsv
• inst.log
• lint.log
• stylelint.log
• test_unit.log

[github-actions]

Quality Report — ConductionNL/decidiq @ 044f0ee

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
check-nav-ceiling		✅
test-l10n		✅
format		✅
check-l10n-js		✅
check-schema-l10n		✅
composer			✅	✅ 104/104
npm			✅	✅ 557/557
app:check-code	⏭️
info.xml	✅
REUSE	❌
PHPUnit					✅
Newman					✅
Playwright					✅
Hydra gates					✅

---

Quality workflow — 2026-08-27 20:32 UTC

Download the full PDF report from the workflow artifacts.