Claude/hacker news ready v ro2 j#2
Conversation
- Delete clippy_round9.txt, test_round9.txt, sample.mhtml, verify_fix.sh - Move POLICY_CPU.toml, POLICY_VRAM.toml to docs/policies/ - Move wrangler.toml to web/ (Cloudflare Pages config) - Move SOUL.md to docs/agent-personas/CUDACLAW.md - Remove .wrangler/ build cache from tracking - Update .gitignore: add .wrangler/, node_modules/, *.mhtml https://claude.ai/code/session_01GaTFACsLyjr4f3qM9woEYm
- Complete README rewrite: honest scope, runnable examples, proper benchmarks - Drop hallucination language, NumPy comparison framing, dead related-project links - Version 1.0.0 → 0.1.0 (research release, not stable API) - Add keywords, categories, rust-version to Cargo.toml - Upgrade #![warn(missing_docs)] to #![deny(missing_docs)] - Rewrite CHANGELOG to reflect actual 0.1.0 state - Remove 11 development-round summary files from crates/ https://claude.ai/code/session_01GaTFACsLyjr4f3qM9woEYm
- Add CONTRIBUTING.md with build/test/PR process/code style guidelines - CI: fmt check, clippy -D warnings, tests on stable+nightly matrix - CI: remove aspirational wasm/python/node/browser jobs - Deploy: remove non-existent wasm/python/docker deploy jobs - Add DEPLOY_INSTRUCTIONS.md for Cloudflare Pages troubleshooting https://claude.ai/code/session_01GaTFACsLyjr4f3qM9woEYm
- Replace hypey announcement with factual Show HN title candidates - Write authentic first-comment emphasizing fishing background - Pre-write responses to predictable HN criticism - Remove old press kit, Discord setup, launch checklists https://claude.ai/code/session_01GaTFACsLyjr4f3qM9woEYm
…cs/web - Add REPO_METADATA_TODO.md with manual GitHub UI instructions - docs/README.md: clean table of contents for essential docs - docs/research/README.md: note that these are working papers - web/index.html: clean landing page with 3 curated demos All checks pass: clippy clean, 82 tests green, docs build, publish dry-run OK. https://claude.ai/code/session_01GaTFACsLyjr4f3qM9woEYm
These were accidentally committed earlier and are covered by .gitignore patterns. https://claude.ai/code/session_01GaTFACsLyjr4f3qM9woEYm
|
cleaning up |
1 similar comment
|
cleaning up |
|
cleaning up |
| ~/.cargo/registry | ||
| ~/.cargo/git | ||
| crates/constraint-theory-core/target | ||
| key: ${{ runner.os }}-cargo-${{ matrix.rust }}-${{ hashFiles('**/Cargo.lock') }} |
There was a problem hiding this comment.
🟡 CI cache key uses hashFiles('**/Cargo.lock') but the crate's Cargo.lock is no longer tracked
This PR removed crates/constraint-theory-core/Cargo.lock from git tracking (commit b231e87) but the CI cache key still uses hashFiles('**/Cargo.lock'). The only remaining tracked Cargo.lock is crates/gpu-simulation/Cargo.lock, which belongs to a completely different crate. This means the CI cache for constraint-theory-core is keyed off an unrelated crate's dependency graph — it won't bust when constraint-theory-core's dependencies change (e.g., bumping rand), and will bust unnecessarily when gpu-simulation's dependencies change. The practical impact is low because the crate has zero production dependencies and Cargo detects stale builds regardless of cache, but the cache key is semantically wrong.
| key: ${{ runner.os }}-cargo-${{ matrix.rust }}-${{ hashFiles('**/Cargo.lock') }} | |
| key: ${{ runner.os }}-cargo-${{ matrix.rust }}-${{ hashFiles('crates/constraint-theory-core/Cargo.toml') }} |
Was this helpful? React with 👍 or 👎 to provide feedback.
Description
Type of Change
Related Issues
Fixes #
Related to #
Motivation and Context
How Has This Been Tested?
Test Environment:
Screenshots / Logs (if applicable)
Checklist
Performance Impact
Breaking Changes
What breaks?
How do users migrate?
Mathematical Rigor (if applicable)
Additional Notes
Reviewers
@reviewer1 @reviewer2
Thank you for your contribution! 🚀
The revolution is not in the computing, but in the geometry.