docs(hackathon): refresh stale + overclaimed submission facts - #13
Conversation
- deadline: Jul 9 -> Jul 20, 2026 (Devpost extension, with link) - repo URL: github.com/heyoub/texo -> github.com/freebatteryfactory/texo (matches the actual git remote) - deployment/Qwen: soften present-tense "is deployed on ECS" / "runs on qwen3.7-max" to honest framing (scripted + committed, provisioning pending) since nothing is provisioned yet; add a TODO to flip back to present tense once the instance is live and a Qwen Cloud run is verified - BatPak: "ships/remains on 0.9.0 by choice" -> now builds on 0.10.0 (Cargo.toml is 0.10.0); reconcile the blog narrative; historical changelog entries left past-tense - dependency count: 492 -> 222 corrected to 492 -> 324 (current Cargo.lock) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughHackathon documentation was updated with the extended deadline, repository URL, batpak-family version, Alibaba Cloud deployment details, revised rebuild metrics, and current provisioning status. ChangesHackathon submission documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d680b2bea4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Deployment update (Jul 6 rebuild closeout) | ||
|
|
||
| The deployed service is now one binary: `/opt/texo/bin/texo serve`. The systemd | ||
| The deploy ships a single binary: `/opt/texo/bin/texo serve`. The systemd |
There was a problem hiding this comment.
The current deployment does not ship a single binary: deploy/deploy.sh builds and copies texo, texo-bvisor-extractor, and bvisor-linux-launcher (lines 12–17 and 33–37). This statement therefore gives submission readers an inaccurate description of the deployment artifact set; describe texo as the single service entrypoint while acknowledging its two confinement companion binaries.
Useful? React with 👍 / 👎.
|
|
||
| All three LLM roles — claim extraction, the relation judge, and chat — run on `qwen3.7-max`; the cosine prefilter uses `text-embedding-v4`. Both are served through Qwen Cloud's DashScope OpenAI-compatible mode (`dashscope-intl`, Singapore). The agent backend is deployed on an Alibaba Cloud ECS instance in Singapore (`ap-southeast-1`), same region as the model endpoint; the deploy configuration is committed in the repo. | ||
| <!-- TODO: confirm ECS deployment details + repo path of deploy script before submitting --> | ||
| All three LLM roles — claim extraction, the relation judge, and chat — are wired to Qwen models on Qwen Cloud's DashScope OpenAI-compatible mode (`dashscope-intl`, Singapore); the cosine prefilter uses `text-embedding-v4`. The agent backend targets an Alibaba Cloud ECS instance in the same Singapore region (`ap-southeast-1`) as the model endpoint; the deployment is fully scripted and committed to the repo (`deploy/provision-ecs.sh`, `deploy/deploy.sh`), with provisioning pending. |
There was a problem hiding this comment.
From a fresh checkout, the cited deployment script is not yet complete: ui/dist is ignored and untracked, while deploy/deploy.sh:40 attempts to copy it without running the UI build or documenting that prerequisite. In that environment the advertised deployment stops at scp, so either add the UI build to the script/documented workflow or avoid claiming that provisioning is the only remaining step.
Useful? React with 👍 / 👎.
| texo now builds on batpak family 0.10.0; see ROADMAP.md for the remaining | ||
| substrate work (hostbat manifest remount, MemFs/SimFs test stores, and SSE | ||
| replay). |
There was a problem hiding this comment.
The hostbat manifest remount is no longer remaining work: src/host/module.rs:25-31 builds a HostModule, and src/host/mod.rs:245-247 mounts it into HostBuilder before deriving the hostbat fingerprints. The referenced ROADMAP.md item is stale, so repeating it here contradicts the current implementation and the updated blog statement that the interim fingerprint has served its purpose.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@HACKATHON.md`:
- Around line 227-231: Update the deployment artifact description in
HACKATHON.md to state that texo is the service binary while the deployment also
includes the supporting texo-bvisor-extractor and bvisor-linux-launcher
executables; remove the inaccurate “only the texo binary” wording.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 4dc2df23-70cc-4f5d-8454-c3b26d7dd333
📒 Files selected for processing (4)
HACKATHON.mdhackathon/ALIBABA-CLOUD-USAGE.mdhackathon/blog-post.mdhackathon/devpost-description.md
| The deploy ships a single binary: `/opt/texo/bin/texo serve`. The systemd | ||
| unit still uses the `texo-agent` service name for operational continuity, but | ||
| the workspace and env file move to `/opt/texo/`. The deploy script stops the | ||
| old service, preserves the durable journal workspace, migrates a live env file | ||
| when present, and ships only the `texo` binary. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Correct the deployment artifact description.
deploy/deploy.sh also copies texo-bvisor-extractor and bvisor-linux-launcher into /opt/texo/bin/, so “ships only the texo binary” is inaccurate. Clarify that texo is the service binary while the deployment includes these supporting executables.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@HACKATHON.md` around lines 227 - 231, Update the deployment artifact
description in HACKATHON.md to state that texo is the service binary while the
deployment also includes the supporting texo-bvisor-extractor and
bvisor-linux-launcher executables; remove the inaccurate “only the texo binary”
wording.
1 participant
Refreshes the hackathon submission docs so every present-tense claim is true today, ahead of the Jul 20 deadline. Docs-only; no code changes.
What changed
HACKATHON.mdheyoub/texo→freebatteryfactory/texo(matches the real remote)HACKATHON.mdqwen3.7-max" → scripted + committed, provisioning pendingdevpost-description.md,blog-post.md,ALIBABA-CLOUD-USAGE.md,HACKATHON.mdCargo.tomlis 0.10.0); blog narrative reconciledHACKATHON.md,blog-post.mdCargo.lock)devpost-description.md,blog-post.mdRationale
The submission docs asserted a live ECS deployment and a running Qwen config that don't exist yet (the Alibaba account is under risk-control review; nothing is provisioned). Claiming a live deployment to judges is an integrity risk, so those are reworded to truthful "ready/scripted, pending" framing, with a
TODOmarker to flip them back to present tense once the instance is live and a Qwen Cloud run is verified end-to-end.Deliberately left alone
Follow-ups (not in this PR)
qwen3.7-maxis unverified end-to-end;qwen3.7-plushangs the sync HTTP client — aflash-class model worked in fallback testing).Summary by CodeRabbit
Greptile Summary
This PR refreshes the hackathon submission documents to match the project's current state. The main changes are:
Confidence Score: 5/5
This looks safe to merge.
No blocking issues found in the changed documentation. The package count matches the current lockfile. The BatPak statement matches the current manifests. The cloud wording distinguishes committed configuration from a live deployment.
What T-Rex did
Important Files Changed
Reviews (1): Last reviewed commit: "docs(hackathon): refresh stale + overcla..." | Re-trigger Greptile