Build RAG docs database on release

[ggozad]

• Adds a GitHub Actions workflow that builds a LanceDB database from docs/ on each release
• Uses haiku-ingester run-batch: ingests new and changed docs, and deletes docs that were removed from the tree
• Restores the previous release's database and queue, so only changed docs are re-processed and deletions are detected
• Uploads the database and queue as a release artifact (haiku-rag-docs.tar.gz)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.99%. Comparing base (a0029e9) to head (cb18133).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #334   +/-   ##
=======================================
  Coverage   94.99%   94.99%           
=======================================
  Files         119      119           
  Lines        6473     6473           
=======================================
  Hits         6149     6149           
  Misses        324      324           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[tseaver]

I wonder: could this PR also emit as an artifact a haiku-rags-docs skill, generated from the haiku-rag create-skill command and the ingested lancedb?

[ggozad]

I wonder: could this PR also emit as an artifact a haiku-rags-docs skill, generated from the haiku-rag create-skill command and the ingested lancedb?

It could. I haven't pushed further on this mostly because I am not sure in which shape to ship it. It could be an artifact that is used as part of a tutorial for example, but needs some docs work.
But yes, once the db is ready the skill could be generated by the template. I will revisit asap.