Commit Graph

3 Commits

Author SHA1 Message Date
DrighnaTechnology 0fbde18c53 Ship Brew Code v0.1.0: Windows fixes, brew UI, and gateway
- Resolve OPENAI_BASE_URL via the .env-aware lookup so non-OpenAI
  providers (Ollama Cloud, etc.) work from .env alone
- Fix the Windows workspace-boundary check for \?\ verbatim paths
- Detect shells with a PATH scan instead of POSIX `sh`, so the
  PowerShell and bash tools work on Windows
- Complete the rebrand: release.yml, rust-ci.yml, LICENSE, .gitignore
- Add the coffee-card startup banner and the heat-shimmer "Brewing"
  processing animation
- Establish the Brew Code identity; never disclose the underlying model
- Add the Cloudflare Worker model gateway under gateway/
- Ignore .brewcode/ local state

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-21 18:27:07 +05:30
DrighnaTechnology 422b46d8f0 Rebrand claw to Brew Code; honor OPENAI_BASE_URL from .env
- Rename binary claw -> brewcode, display name -> Brew Code
- Rename config paths .claw/ -> .brewcode/, CLAW_CONFIG_HOME -> BREWCODE_CONFIG_HOME
- Resolve OPENAI_BASE_URL via the .env-aware lookup used for the API key
2026-05-20 15:27:35 +05:30
Yeachan-Heo 19c6b29524 Close the clawability backlog with deterministic CLI output and lane lineage
Finish the remaining roadmap work by making direct CLI JSON output deterministic across the non-interactive surface, restoring the degraded-startup MCP test as a real workspace test, and adding branch-lock plus commit-lineage primitives so downstream lane consumers can distinguish superseded worktree commits from canonical lineage.

Constraint: Keep the user-facing config namespace centered on .claw while preserving legacy fallback discovery for compatibility
Constraint: Verification needed to stay clean-room and reproducible from the checked-in workspace alone
Rejected: Leave the output-format contract implied by ad-hoc smoke runs only | too easy for direct CLI regressions to slip back into prose-only output
Rejected: Keep commit provenance as free-form detail text | downstream consumers need structured branch/worktree/supersession metadata
Confidence: medium
Scope-risk: moderate
Directive: Extend the JSON contract through the same direct CLI entrypoints instead of adding one-off serializers on parallel code paths
Tested: python .github/scripts/check_doc_source_of_truth.py
Tested: cd rust && cargo fmt --all --check
Tested: cd rust && cargo test --workspace
Tested: cd rust && cargo clippy -p commands -p tools -p rusty-claude-cli --all-targets --no-deps -- -D warnings
Not-tested: full cargo clippy --workspace --all-targets -- -D warnings still reports unrelated pre-existing runtime lint debt outside this change set
2026-04-05 18:41:02 +00:00