docs(#3343): add prerequisites section to README

[fullsend-ai-coder]

Add a Prerequisites section before the Building heading that lists the required toolchain for building and developing ec-cli: Go 1.25.8+, Make, Podman/Docker, and Node.js 18+. Includes minimum versions derived from go.mod and package.json, and a cross-reference to the Podman troubleshooting section for Fedora/RHEL users.

---

Closes #3343

Post-script verification

• Branch is not main/master (agent/3343-add-prerequisites-readme)
• Secret scan passed (gitleaks — 15814bf9896060ce26a127adc995a1fbb60c3a77..HEAD)
• Pre-commit hooks passed (authoritative run on runner)
• Tests ran inside sandbox

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:26 AM UTC · Completed 10:33 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

Review

Findings

High

• [incorrect prerequisite version] README.md:16 — The PR adds a Prerequisites section stating Go "1.25.8 or later" as the minimum version, but go.mod declares go 1.26.3. Go 1.25.8 is a valid release but belongs to the previous major release line (1.25.x). Since go.mod requires 1.26.3, a contributor using Go 1.25.8 would be unable to build the project.
  Remediation: Change the Go version in the Prerequisites section from "1.25.8" to "1.26.3" to match go.mod, or remove the hardcoded version and direct readers to go.mod to avoid future staleness.

Low

• [stale cross-reference risk] README.md:16 — The Go version is hardcoded in the README Prerequisites section. Since go.mod is the source of truth and is updated independently, any future Go version bump will leave the README stale again. The diff partially mitigates this by including a cross-reference to go.mod, but the hardcoded version number remains.
  Remediation: Consider removing the hardcoded version and stating "Go (see version in go.mod)" instead, or accept the maintenance burden of updating the README on each Go bump.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run

Looks good to me

Low

• [pattern-inconsistency] README.md:18 — The existing README uses * (asterisk with 2-space indent) for bullet lists (lines 6–9), but the new Prerequisites section uses - (hyphen, no indent). This is a minor formatting inconsistency.
  Remediation: Consider using * to match the existing bullet style, or standardize on - throughout.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
acceptance	54.45% <ø> (-0.02%)	⬇️
generative	12.27% <ø> (ø)
integration	23.59% <ø> (ø)
unit	72.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 11:13 AM UTC · Completed 11:24 AM UTC

Commit: 87c4a29 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.91

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[high] incorrect prerequisite version

The PR adds a Prerequisites section stating Go 1.25.8 or later as the minimum version, but go.mod declares go 1.26.3. Go 1.25.8 is a valid release but belongs to the previous major release line (1.25.x). Since go.mod requires 1.26.3, a contributor using Go 1.25.8 would be unable to build the project.

Suggested fix: Change the Go version in the Prerequisites section from 1.25.8 to 1.26.3 to match go.mod, or remove the hardcoded version and state Go (see version in go.mod) to avoid future staleness.

[fullsend-ai-review]

[low] stale cross-reference risk

The Go version is hardcoded in the README Prerequisites section. Since go.mod is the source of truth and is updated independently, any future Go bump will leave the README stale again.

Suggested fix: Consider stating Go (see version in go.mod) instead of hardcoding a specific version number.