docs: publish DataFusion 55.0.0 and 55.1.0 snapshots

[yiaany]

Summary\n\nThis publication PR adds complete generated documentation snapshots under:\n\n- �ersions/55.0.0/ from tag 55.0.0\n- �ersions/55.1.0/ from tag 55.1.0\n\nBoth snapshots were built from their exact release tags with the existing docs/build.sh and the small versioned-docs configuration overlay from PR apache#24792. The generated pages use version-prefixed canonical URLs and include the version switcher.\n\nThe snapshots were checked locally over HTTP, including version switching, missing-page fallback, search, static assets, and both release roots. No .buildinfo file was published.\n\nThis targets the fork's �sf-site branch so the layout can be reviewed before publication to Apache's �sf-site.

[ecc-tools]

ECC Tools / Security Evidence

Commit: 04c8f683cf9e3f838ad34f71c788275c118b6d33

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 522 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Risk Taxonomy

Commit: 04c8f683cf9e3f838ad34f71c788275c118b6d33

PR taxonomy review recommended (neutral)

Detected 3 PR taxonomy bucket(s): CI/CD Recommendation, Cost/Token Risk, PR Review/Salvage Evidence.

Scanned 522 changed file(s).

Roadmap taxonomy buckets:

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

• Regression coverage may lag behind the diff
• User-facing UI changes may ship without browser coverage
• CLI changes may ship without shell or end-to-end coverage
• 0 CI or workflow path(s) changed

Paths:

• .asf.yaml
• searchindex.js
• versions/55.0.0/_static/base-stemmer.js
• versions/55.0.0/_static/doctools.js
• versions/55.0.0/_static/documentation_options.js
• versions/55.0.0/_static/english-stemmer.js
• versions/55.0.0/_static/language_data.js
• versions/55.0.0/_static/scripts/bootstrap.js

Cost/Token Risk

AI routing, usage, and token-budget changes should include budget or usage-limit evidence.

Signals:

• Cost or token-risk changes may ship without budget evidence
• 0 cost/token path(s) changed

Paths:

• .asf.yaml
• _downloads/1e336e540124589d1e27210fa4f805f6/rust_lint.sh
• _sources/contributor-guide/api-health.md.txt

PR Review/Salvage Evidence

PR review, stale-closure, and triage automation should carry stale-closure, reviewer-thread, and reopen-flow evidence so useful closed work can still be salvaged.

Signals:

• PR review or stale-closure automation may ship without salvage evidence
• 6 PR review/salvage path(s) changed

Paths:

• _sources/contributor-guide/pr_review.md.txt
• contributor-guide/pr_review.html
• versions/55.0.0/_sources/contributor-guide/pr_review.md.txt
• versions/55.0.0/contributor-guide/pr_review.html
• versions/55.1.0/_sources/contributor-guide/pr_review.md.txt
• versions/55.1.0/contributor-guide/pr_review.html

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Reference Set Readiness

Commit: 04c8f683cf9e3f838ad34f71c788275c118b6d33

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 522 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Hosted Promotion Readiness

Commit: 04c8f683cf9e3f838ad34f71c788275c118b6d33

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 522 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[yiaany]

Closing this publication PR because it was based on the Apache asf-site branch while the PR base was the fork's stale asf-site branch. I am recreating it from the correct fork base so the review contains only the two versions/ snapshot directories and one publication commit.