Skip to content

docs: restore scope caveats and stamp make check with the commit - #59

Merged
Vonng merged 2 commits into
mainfrom
docs/restore-scope-caveats
Nov 10, 2026
Merged

Vonng merged 2 commits into
mainfrom
docs/restore-scope-caveats

Conversation

@Vonng

@Vonng Vonng commented Nov 10, 2026

Copy link
Copy Markdown
Member

Summary

Two small follow-ups from a review of the 20261026 documentation.

Restore scope caveats (EN/ZH). The style rewrites in e051dbb and ec52311 dropped a few statements that bound what the published evidence proves. No fact changed, but the pages no longer said so next to the claims:

  • blog/release/silo-20261026: local protocol fixtures do not certify real cloud accounts or backend crash durability; a later unconditional PUT is not ordered after an unresolved request; the candidate checks describe dependency compatibility only and do not certify the final Server source.
  • compatibility/server (20261026 upgrade checks): a timeout does not prove that I/O stopped, and delayed rollback remains possible. Added to the paragraph below the table, so the table is untouched.
  • blog/release/pkg-3.15.2: no new CVE fix is claimed for the SDK patches.

The wording follows the text that was on the site before the rewrite.

Stamp make check. The target now prints git rev-parse HEAD and git status --short --branch before the build, so a saved local log identifies the commit and any uncommitted or untracked files. It is informational only: a dirty tree does not fail the check, and a failure outside a Git checkout is ignored. The workflow is unchanged; hosted runs are already bound to a commit by the runner.

Verification

make check on a9e99410f399863cc18d97e4b3289de833a65c18 with a clean tree (local Hugo 0.169.0 extended; CI uses the pinned 0.168.0):

  • 25 unit tests pass, all modules verified
  • 1444 EN / 1470 ZH pages, same as main
  • internal link check passed: 626727 rendered internal references across 1836 HTML files

🤖 Generated with Claude Code

Vonng and others added 2 commits November 10, 2026 16:32
The style rewrites in e051dbb and ec52311 removed a few statements that
bound what the published evidence proves. No fact changed, but a reader
could take candidate-stage dependency checks and local KES fixtures as
proof of the final artifacts or of a real cloud backend, and the
compatibility page no longer said that a timeout leaves I/O unresolved.

Restore them in English and Chinese, next to the claims they qualify:

- 20261026 notes: local protocol fixtures do not certify real cloud
  accounts or backend crash durability; a later unconditional PUT is not
  ordered after an unresolved request; candidate checks describe
  dependency compatibility only.
- Server compatibility: a timeout does not prove that I/O stopped, and
  delayed rollback remains possible.
- silo-pkg 3.15.2 notes: no new CVE fix is claimed for the SDK patches.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: Feng Ruohang <rh@vonng.com>
A saved `make check` log could not be tied to the source it checked: it
recorded neither the commit nor whether the tree had uncommitted or
untracked files, and an untracked page is enough to change the build.
Hosted CI is bound to a commit by the runner, but a local log is the only
evidence for work that cannot be pushed yet.

Print `git rev-parse HEAD` and `git status --short --branch` before the
build. The line is informational: a dirty tree is the normal state when
checking before a commit, and a failure outside a Git checkout is ignored.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: Feng Ruohang <rh@vonng.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying silo-pgsty-com with  Cloudflare Pages  Cloudflare Pages

Latest commit: a9e9941
Status: ✅  Deploy successful!
Preview URL: https://dfcd9340.silo-pgsty-com.pages.dev
Branch Preview URL: https://docs-restore-scope-caveats.silo-pgsty-com.pages.dev

View logs

@Vonng
Vonng merged commit 5b53e60 into main Nov 10, 2026
2 checks passed

Vonng commented Nov 10, 2026

Copy link
Copy Markdown
Member Author

Resolution. The scope and safety caveats removed during the documentation rewrite were restored in 36f99424, with corresponding English and Chinese updates.

The documentation now states that local KES/Moto protocol fixtures do not certify real cloud accounts or backend crash durability; candidate dependency checks describe compatibility only and do not validate the final Server source; a timeout does not prove that disk or RPC I/O has stopped; delayed commits and rollbacks remain possible; a later unconditional PUT does not establish ordering against an unresolved request; and the release does not add distributed fencing or automatically repair previously inconsistent data.

The related wording was reviewed and merged through site PR #59. H-06 is closed with the original evidence boundaries restored.

Vonng commented Nov 10, 2026

Copy link
Copy Markdown
Member Author

Resolution. The site make check target now records both the checked commit and the worktree state before running the build. This was implemented in a9e99410 and merged through PR #59:

git rev-parse HEAD
git status --short --branch

I reran make check on the current site main at 0aef637b. The log recorded the exact commit and ## main...origin/main, then passed 25 unit tests, module verification, the Hugo build, and the internal-link check covering 633,886 rendered references across 1,852 HTML files.

This fixes the traceability gap for future local logs. Historical logs created before the change remain historical evidence and are not retroactively relabeled. Hosted release verification is separately bound to the release commit d9982923 through the linked GitHub Actions runs. H-08 is closed.

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