ci: vendor validation scripts and remove remote action pins

[hyperpolymath]

Automated PR to fix CI after deleted actions.

---

Summary by Gitar

• CI / Validation:
  • Added vendored validate-a2ml.sh and validate-k9.sh scripts in .githooks/
  • Replaced remote GitHub Action validation steps with local script executions in .github/workflows/dogfood-gate.yml

_{This will update automatically on new commits.}

[gitar-bot]

Running post-merge workflows

CI failed: CI failed due to a missing Dockerfile during ClusterFuzzLite fuzzer building and formatting violations caught by cargo fmt in the Rust CI check.

Overview

Two distinct change-related failures occurred across the CI jobs: a ClusterFuzzLite build failure due to an absent Dockerfile path, and a Rust formatting check failure from cargo fmt.

Failures

ClusterFuzzLite Dockerfile Not Found (confidence: high)

• Type: build
• Affected jobs: 90125322921
• Related to change: yes
• Root cause: The ClusterFuzzLite action is looking for a Dockerfile in storage/conflow/.clusterfuzzlite/ where it does not exist or was moved.
• Suggested fix: Verify and correct the project-src-path or workflow configuration so that it correctly points to the directory containing the .clusterfuzzlite/Dockerfile.

Rust Formatting Check Failure (confidence: high)

• Type: tooling
• Affected jobs: 90126253169
• Related to change: yes
• Root cause: Files benches/conflow_bench.rs and tests/e2e_test.rs do not adhere to rustfmt formatting standards, causing cargo fmt --all -- --check to fail.
• Suggested fix: Run cargo fmt --all locally to format the code, then commit and push the updated files.

Summary

• Change-related failures: 2 failures (ClusterFuzzLite build failure and cargo fmt formatting errors)
• Infrastructure/flaky failures: 0 failures
• Recommended action: Fix the ClusterFuzzLite project path configuration and run cargo fmt --all locally to resolve formatting issues before pushing again.

Code Review ✅ Approved

Vendors validation scripts into .githooks/ and replaces remote GitHub Action validation steps with local script executions in the CI workflow. No issues found.

Auto-approved: No blocking issues found.
Please see Auto-approve Docs for details on setting custom approval criteria.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[gitar-bot]

Gitar has auto-approved this PR (configure)