Skip to content

chore: clean up zeroclawed name remnants #81

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bglusman merged 1 commit into from
Apr 29, 2026
Merged

chore: clean up zeroclawed name remnants #81

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions .gitleaks.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
# Rules here catch the SHAPE of disclosure (private-IP ranges, generic
# credential-in-header patterns), not any specific user's identifiers.

title = "zeroclawed secret + infra-leak rules (public, generic)"
title = "calciforge secret + infra-leak rules (public, generic)"

# Start from gitleaks' curated default rules (40+ cloud/tool token patterns).
[extend]
Expand Down Expand Up @@ -87,7 +87,7 @@ paths = [
'''package-lock\.json$''',
'''yarn\.lock$''',
'''bun\.lock$''',
# zeroclawed-secret-paste lib.rs: contains pure-function predicate
# paste-server lib.rs: contains pure-function predicate
# tests for is_localhost_origin that, by construction, must use
# literal RFC 1918 / CGNAT IPs to test that the predicate accepts
# private and rejects CGNAT. Substituting RFC 5737 docs IPs would
Expand Down Expand Up @@ -118,10 +118,9 @@ regexes = [
'''192\.168\.1\.42''',
'''192\.168\.1\.100''',
'''user:pass@evil\.com''',
# Pre-existing leaks inherited from main (rename PR re-touched
# files containing them; they were already there). Tracked for
# sanitization in a follow-up PR. Specific values only — keeps
# the rest of the 10/8 + 192.168/16 ranges tight.
# Example private IPs used in test fixtures and docs — generic
# placeholders, not real deployment addresses. Specific values only;
# keeps the rest of the 10/8 + 192.168/16 ranges tight.
'''10\.0\.0\.1''',
'''10\.0\.0\.10''',
'''10\.0\.0\.20''',
Expand Down
10 changes: 5 additions & 5 deletions BACKLOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@
- [ ] Test end-to-end: Telegram → calciforge → claw-code → security proxy → provider
- [ ] Document claw-code integration in `docs/claw-code-setup.md`

### ZeroClaw (zeroclawlabs) Integration
- [ ] Install zeroclawlabs on 210 via deploy script (`--with-zeroclaw`)
- [ ] Configure zeroclawlabs gateway URL to use Calciforge security proxy
### ZeroClaw Integration
- [ ] Install zeroclaw on 210 via deploy script (`--with-zeroclaw`)
- [ ] Configure zeroclaw gateway URL to use Calciforge security proxy
- [ ] Create wrapper script: `zeroclaw-wrapped` → routes through Calciforge security proxy
- [ ] Test: Telegram → calciforge → zeroclaw → security proxy → provider
- [ ] Document zeroclaw integration
Expand Down Expand Up @@ -91,10 +91,10 @@
- [x] Remove vendored zeroclaw crate (use upstream)
- [x] Remove robot-kit, aardvark-sys (use upstream)
- [x] Remove local clash (use crates.io)
- [x] Update deps: zeroclawlabs 0.6.8, clash 0.6.2
- [x] Update deps: zeroclaw 0.6.8, clash 0.6.2
Comment thread
bglusman marked this conversation as resolved.
- [x] Sanitize deploy scripts (move to infra/, gitignore)
- [x] Git history filter to remove secrets/artifacts
- [x] CI cleanup (remove zeroclaw from matrix)
- [x] CI cleanup (remove zeroclaw from CI matrix)

---

Expand Down
Loading