Skip to content

Explain duplicate checks and regression candidates in run history - #977

Merged
zlareb1 merged 11 commits into
mainfrom
docs/run-history-capability-summary
Nov 21, 2026
Merged

zlareb1 merged 11 commits into
mainfrom
docs/run-history-capability-summary

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Changelog category

  • Documentation

Changelog entry

Explain duplicate bug checks and regression candidate ranking in the run-history guide and its agent-readable summary.

Why

The run-history opening describes recording but omits duplicate checking and regression candidate ranking. It also asks which change introduced a regression without distinguishing candidates from proof.

Scope and risk

State both existing capabilities in the opening and its generated llms.txt entry. Keep the recording switches, registered tracker and namespace access prerequisites explicit. Link the existing bug-draft walkthrough and state that ranking neither runs a bisect nor proves causation.

The documentation changes the use-case opening, factual search title/description and corresponding agent-readable summary. The metadata names run history, duplicate checks and regression candidates without claiming proven causation. The existing operation details, measurements and setup links remain. There are no API, storage, permission, provider, package or generated translation changes.

Compatibility, rollout and rollback

  • Wire: none.
  • Operator steps: none.
  • Rollback: revert the two text changes.

Tests

  • Target-page Prettier check, prose and diff whitespace checks pass.
  • The existing page-summary helper produces the exact changed llms.txt entry from this page; all other entries are unchanged.
  • The walkthrough path and anchor resolve in the current tree.
  • No local test suite, application, provider call or model evaluation was run. Full GitHub CI is required on this head.
  • An earlier head failed with a mypy internal error. This head includes the merged per-test cache isolation from SDK typing tests use separate mypy caches #925; it leaves the typing assertions unchanged. The original crash cause remains unconfirmed.

The prior b22f161471 full CI failed during the initial memory write in an integration fixture, before its restore step. The cancellation cause remains unestablished. The metadata is not claimed as a fix; the fixture prerequisite below resolves a separate diagnosed missing-table failure. Complete new-head CI is required. No unchanged-head CI rerun was requested.

Main includes the replicated-erasure fixture's lease-table repair from #1076. This PR uses main's exact fixture and changes no test or erasure source; the standalone fixture regression remains in #1077. The use-case page and this PR's llms.txt row match the previously reviewed feature; all other index rows are inherited from main. Full CI and fresh independent reviews must qualify this new composition.

The c057f2f592 composition failed the existing Python lane-linearity check; its largest sample did not finish. The translations check passed in that job. No parser, timing guard or parse limit changes here, and this main composition is not claimed as a repair.

AI assistance in the code

  • AI-generated: Codex drafted the wording and checked it against the tracker and PR-history documentation.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • Full format, lint, typecheck and unit checks pass in GitHub CI.
  • No production runtime, migration, generated translation or plugin changes.
  • Existing prerequisites and candidate-ranking limits remain explicit.
  • Public text passes prose checks.
  • Commits are signed off.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@vercel

vercel Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
loom-docs Ready Ready Preview Nov 20, 2026 11:59pm UTC

Request Review

Build this guide with the documentation application used by previews.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Fenced memory inserts require a lease table in the selected schema. Give each fixture database its own Keeper root while preserving the replicated content checks.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The fixture repair is on main. Its standalone regression remains in #1077; the feature diff retains its original tests.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The documentation branch needs the shared workflow checks and checkout credential controls before its final CI qualification.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@zlareb1
zlareb1 merged commit 9af0d68 into main Nov 21, 2026
52 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant