Bug audit, October 15, 2026

Fifteen bounded fixes were reviewed and pushed individually to main. No new configuration is needed. These are source and focused regression results, not an installed-release acceptance record.

Commit	Corrected behavior
`a7bc937`	Diagnostic queries choose daily files by newest date across clients before applying the existing 200-file scan budget.
`8c5c35d`	An impossible schedule date normalizes to an absent boundary without discarding unrelated saved rules.
`2cdf7b7`	Terminal branch/tag names remain operable when different reference namespaces share a name.
`bd29ee7`	The OAuth token endpoint accepts standard form encoding alongside JSON, retaining body limits and rejecting duplicate decoded parameters.
`e82429f`	Conflict forecasting compares against the merge base itself, avoiding false overlaps and root-commit failures.
`2fc7f96`	Linked `.git` markers stop repository discovery without validation or descent into nested repositories.
`a4efd6c`	SAML service attributes may appear in either order; malformed, duplicate, missing, and cross-element attributes remain rejected.
`c90ba15`	Unstaging a selected terminal rename restores both index paths while preserving unrelated staged files and copy sources.
`d063ccd`	Oversized schedule updates are rejected before replacing storage, runtime state, or the editor; a localized status message retains the previous configuration.
`9596f63`	Conflict forecasting retains both rename endpoints, including rename/delete, rename/modify, and destination collisions.
`fa33685`	Incomplete directory enumeration checks the Git marker directly so entry caps cannot hide repository boundaries.
`9198939`	An empty test selection exits with a clear error instead of invoking unrelated automatic discovery or recursively running the test runner.
`f7430a4`	OAuth startup rejects mismatched signing keys and private keys on the wrong curve; issued tokens verify against served JWKS.
`591cb46`	Profile restoration reloads effective schedules without rewriting storage and ignores obsolete asynchronous responses.
`fa629d4`	Terminal merge review keeps the selected branch's full reference, preventing same-name tags from taking precedence and preserving stale-tip checks.

Verification

Each fix has a regression observed failing before implementation and passing afterward. Independent review accepted each change.

Focused group	Passed
Diagnostic log server	10
Self-hosted server, including OAuth and SAML	45
Schedule model/runtime, editor, and profile restoration	17
Repository discovery	14
Potential conflicts, using real Git repositories	9
Terminal repository service and porcelain parsing	27
Terminal selection and unstaging, using real Git and Textual Pilot	4
Terminal merge selection and existing branch review, using Textual Pilot	3
Test runner selection, batching, and accounting	25
Total across these focused groups	154

The final application TypeScript check passed with node node_modules/typescript/bin/tsc --noEmit --pretty false. Whitespace checks passed. Focused ESLint found one pre-existing react/jsx-no-bind error in preferences.tsx at line 1178, outside the changed callback; the same code exists at the audit baseline 4403e59. Tests ran on Linux with Node 24.19.0. Desktop tests used the repository's normal test runner; the conflict tests inject real Git execution at the process boundary. Terminal tests used the checkout source with PYTHONPATH=tui/src.

Dependencies were installed from frozen manifests with lifecycle scripts disabled, followed by the required native download and declared vendored JavaScript builds. No dependency manifests or lockfiles changed.

Windows builds were still running or queued at closeout. Linux CI had passed through d063ccd; the documentation deployment for 2fc7f96 also passed. Later runs were still queued or running. No local Windows root build, installer, installed application, or new packaged UI capture was verified in this Linux session. Existing historical release claims are separate.

Remaining verification

All three findings deferred at the first checkpoint were reproduced, fixed, and covered in the resumed pass. The two audit passes do not establish that the repository is free of other defects. Pending work is final remote build results and Windows packaged/installed acceptance, including the earlier independent clone-recovery continuation. Existing broader feature issues stay open; this audit does not claim their acceptance criteria were completed.

New investigation paused when closeout was requested; the subsequent request restored the investigation scope and retained frequent pushes. Existing remote branches, installations, profile recovery records, and the unfinished installed-clone acceptance work were left intact. No temporary task branches, linked worktrees, or stashes were created or deleted.

中文摘要

十五項修正已逐項推送到 main，154 項針對性測試同最終 TypeScript 檢查通過。排程、OAuth、診斷記錄、儲存庫探索同終端 Git 操作嘅回歸都有實際測試。 Windows 建置仍在排隊或執行，安裝程式同真正安裝後介面未喺今次 Linux 工作階段驗證。第一輪保留嘅三項線索已喺獲准繼續後修好；整個儲存庫並未聲稱完全冇其他問題。