Align local validation with CI and draft public repo description

[rlancaster243]

Summary

• Align scripts/validate.sh with the full GitHub Actions gate: Ruff, format, mypy, pytest, fixture smoke test, dbt build, Terraform fmt/init/validate
• Fail clearly when Terraform is missing locally (CI uses 1.9.8)
• Draft GitHub About text for when the repo goes public (paste into Settings → General)

GitHub About (paste when going public)

Description (≤350 chars):

Production-oriented SEC/XBRL data engineering reference: fixture-first ingestion, dbt/DuckDB modeling, CI validation, Docker, Airflow example, and parameterized GCP IaC.

Topics:

sec-edgar
xbrl
data-engineering
dbt
python
duckdb
terraform
gcp
airflow
portfolio

These match the README framing (reusable reference / portfolio case study) and avoid implying a live managed deployment.

Acceptance criteria

• Local bash scripts/validate.sh exercises the same checks as .github/workflows/ci.yml (minus Actions-only artifact uploads)
• CONTRIBUTING / OPERATIONS expectations for fixture + dbt + Terraform remain accurate
• Draft description is ready to paste into GitHub About before flipping visibility

Scope

No application logic, fixture, or model changes. Repo visibility and GitHub About metadata are left for the maintainer (this environment cannot update them).

  

[coderabbitai]

Warning

Review limit reached

@rlancaster243, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 94119bb4-438b-42c7-9c3b-427f9706abe9

📥 Commits

Reviewing files that changed from the base of the PR and between 320fd8b and 0190f7d.

📒 Files selected for processing (1)

• scripts/validate.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/align-validate-and-description-6745

---

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