Skip to content

docs(updates): fixture temp-root lifetime, frontend-link recovery and published-release wording - #406

Merged
andrescera merged 3 commits into
mainfrom
docs/review-follow-ups-update-system
Oct 22, 2026
Merged

andrescera merged 3 commits into
mainfrom
docs/review-follow-ups-update-system

Conversation

@andrescera

Copy link
Copy Markdown
Member

What

Documentation only. The orchestrator test-helper README now states the temp-root lifetime contract (a root lives for one test and is disposed by the registered disposer); a host-bound timing number is removed from the backend README; docs/BUILD_PIPELINE.md gains the frontend-link repair recovery commands so the user docs and the engineering contract cite the same source; and three places that still called 2026.9.5 the planned first orchestrator release now say it was published on 2026-10-20.

Why

Findings of the independent reviews of the earlier changes (stale owning doc, undocumented lifetime change, an unverifiable host-specific number, duplicated recovery commands).

How to verify

Each statement was checked against the code or the git tags before writing; the repository's documentation contract tests and the agents-budget check pass.

Risks

None for runtime behaviour. No code or test change.

…iming

The orchestrator memory-persistence helper now disposes its temp roots after each test, so the helpers README describes that one-test lifetime, how module-scope fixtures must handle it, which test pins the disposer and what it does not pin. The backend README no longer quotes one host's write timing, the tick-diagnostics coverage line names the real fault detector, and the install-when-idle label says which steps have their own test.
…overy

v2026.9.5 published on 2026-10-20 and is the first tag that ships the update orchestrator, so three places that still called it planned now say so, and UPDATE-RECOVERY notes that its backend already reads receiptBaseline. BUILD_PIPELINE gains the manual frontend-link recovery and pre-drill checks that the user troubleshooting page also gives.
@coderabbitai

coderabbitai Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 2d93c822-edb7-49de-8d64-b40e45dfac1e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@andrescera
andrescera merged commit 2033191 into main Oct 22, 2026
11 checks passed
@andrescera
andrescera deleted the docs/review-follow-ups-update-system branch October 22, 2026 09:14
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