| Files | Last commit | Last update |
|---|---|---|
docs: point every link at the codewhale-hq organization Hunter moved the Codewhale repositories to github.com/codewhale-hq on 2026-10-05. Rewrite Hmbown/<moved repo> slugs to codewhale-hq/<repo> in docs, READMEs (all 19), website, CHANGELOGs, workflows, issue templates, Cargo/npm/VS Code/nix/winget metadata, install and updater code, the bundled first-party marketplace catalog and their tests: 1,795 references in 434 files, plus four escaped regex literals. Docker images publish to ghcr.io/codewhale-hq/codewhale from the next release. Old URLs keep working through GitHub's transfer redirects (verified live: API releases/latest, HTML releases/latest, release asset downloads, codeload tarballs, git clone), so released clients keep updating. Left unchanged on purpose: Hmbown/codewhale-cu-plugin (not moved yet; its shipped updater refuses redirects), Hmbown/deepseek-skills, cwc and other repos that did not move; package identities (winget Hmbown.CodeWhale, NSIS publisher); vendor/codewhale-ratatui (frozen reviewed package); and the extension-host GitHub adapter with tools/github/report.rs and their parity fixture, which need a bundle rebuild and move together in a follow-up. README translation stamps updated to the new README.md hash. Validation: npm test (wrapper 101/0, SDK 19/0, extension host 398 passed / 0 failed / 7 skipped, web 763/0) and npm run check:web exit 0 (one pre-existing facts-lib.mjs lint warning). cargo check --workspace --tests --all-features --locked: exit 0. cargo test -p codewhale-cli -p codewhale-release -p codewhale-protocol and the touched codewhale-tui modules (client, cloud_dispatch, commands, dispatch_runner, llm_client::mock, oauth, operate, plugins::marketplace, remote_control, remote_setup, tools::mcp_registry, tools::web::fetch, working_set, tui::ui::tests): all ok, 0 failed. check-readme-translations (18 in sync), readme locales, TUI locale parity, product vocabulary, web locales, contributor credit, plugin claims, release-workflows.test.js and check-versions all pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: CodeWhale Bot <bot@codewhale.net> | 1 month ago | |
ci(codeql): add advanced setup workflow that honours codeql-config.yml Default setup ignores .github/codeql/codeql-config.yml, so alerts kept pointing at test paths. This workflow scans the same languages default setup scans today (actions, javascript-typescript, python, rust; build mode none; default suite) and passes the config file to init. It takes effect only after the repository's code scanning setting is switched from Default to Advanced; until then GitHub rejects its SARIF uploads. That switch is a manual settings change. Checks: actionlint .github/workflows/codeql.yml clean; YAML parses. Not run on hosted CI yet. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> | 1 month ago | |
ci: keep aarch64 release builds alive; align workflow tests [skip ci] Release candidate runs 42381818665 (549ff01ebb) and 42408096045 (b175b1f9ed) both lost the linux-arm64, android-arm64 and ohos-arm64 dist builds to "The runner has received a shutdown signal" (exit 143) 20-40 minutes into the quiet compile of the large crates, with no compiler, linker or disk error. linux-x64 on the same ubuntu-latest image succeeds, and 0.10.2 shipped these targets, so the dist profile (fat LTO, one codegen unit) on a grown workspace exhausting 16 GB runner memory is the likely cause. The three Linux aarch64 legs now add an 8-16 GB swapfile on the largest writable disk before building; the shipped binaries are unchanged. The next release-candidate run is the proof. Also fixes two workflow tests my CI slim-down (99cb5a0f4f) made wrong: release-workflows.test.js now expects the npm wrapper smoke to be manual only (Ubuntu + Windows on dispatch), and agent-task-metadata.test.sh no longer requires the removed agent-task-labels.yml but guards that it stays retired. The stale change-detection path for that workflow is dropped. Verified: node --test .github/scripts/release-workflows.test.js 1/1 pass; d8-executable.test.js 4/4 pass; agent-task-metadata.test.sh pass; actionlint with CI flags passes on ci.yml and release-artifacts.yml. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> | 1 day ago | |
release: support semver prerelease tags (0.10.3-beta.2 path) A GitHub prerelease such as v0.10.3-beta.2 can now be prepared and tagged, publishing a GitHub prerelease and npm next while leaving the plain X.Y.Z path unchanged. - prepare-release, check-versions, verify-remote-tag, the npm tag-checkout gate, ensure-release-assets-absent and auto-tag accept X.Y.Z-prerelease. They still reject build metadata, a missing patch, and v-prefixed values where the convention is bare. - prepare-release also normalizes internal pins in the workspace-member test harnesses (tests/portable-*) when either side is a prerelease: Cargo requires an explicit prerelease requirement, so their stale caret pins could not resolve a prerelease workspace. Both those manifests and their normalization are added to the restore transaction. - release.yml resolves a prerelease output. A prerelease tag skips docker-build, docker, CNB, GitCode, Homebrew and the web release record, creates the GitHub release with prerelease=true, and publishes npm with --tag next. There is no crates.io job, so a prerelease publishes no crates. Stable tags take every existing path with unchanged inputs. - release-artifacts skips AUR metadata for prerelease versions (AUR pkgver cannot carry a prerelease hyphen). - docs/RELEASE_CHECKLIST.md documents the checkpoint flow, including the workspace restore afterwards. Verified with a git-archive fixture of 13858fa8d0 plus these scripts (receipts in CW/artifacts/release-beta-tooling-20261109/): - prepare-release.sh 0.10.3-beta.2 then check-versions.sh --require-dated-release: Version state OK workspace/npm/npm-binary/ lockfile at 0.10.3-beta.2 (66 script-level checks, 0 failures; verify-beta-tooling.log). - prepare-release.sh 0.10.3 restores the tree; the only residual tracked diff is the three tests/portable-* pin files, now tracking 0.10.3. - release.yml resolve step executed against real git tags for push and dispatch paths: prerelease=true for v0.10.3-beta.2, prerelease=false for v0.10.3, and invalid versions rejected. - actionlint clean on the three changed workflows; bash -n/node --check clean; existing prepare-release, verify-remote-tag, require-release-tag-checkout, generate-release-body and ensure-release-assets-absent tests pass. Not proven here: no live GitHub prerelease, npm publish, or hosted release.yml run. The fixture has no .git, so check-versions checks 7/12 were skipped there (they pass on canonical before 34ea11e0a3). | 8 minutes ago | |
docs: document live catalog refresh and 0.10.3 limits [skip ci] Document the landed Engine catalog refresh and Runtime API projection so clients can discover new models on supported routes without replacing the binary. Explain exact-route refresh, freshness, retained snapshots, and the existing desktop picker refresh and revision polling. Carry the EN/ZH durable job receipt and implicit socket contract with native source 821c478eb9. Describe Tinker beta configuration without implying live provider qualification. Align the Chinese provider introduction with the supported-model-list boundary. Keep release limits explicit for plugins, platform qualification, history recovery, long sessions, and rollback. Credit zhuowp's rate-limit recovery contribution and SparkofSpike's proxy privacy report. Sync the embedded changelog and derived web metadata only after Mistral guidance 07853c32661 landed with its live-conversation caveat. Verified: derive-facts and check-facts passed; embedded changelog sync/check and scoped diff whitespace passed. Contributor credit check found all 15 contributors credited, retaining its known Bot/co-author warning. All 22 v11 manifest inputs were independently checked immediately before staging; six catalog/job API source paths matched committed main. Retained development receipts cover nine controlled catalog API assertions, eight mounted picker assertions, and a keyless public Models.dev fetch. These are scoped development observations, not final package or provider inference qualification. Proxy source matches the retained macOS 23/23 existing-test receipt; runtime log capture and other platforms are unqualified. No new maintained tests, native builds, hosted CI, or deployment in this slice. | 2 days ago | |
ci: add advisory Claude PR review workflow (#3456) Wire Claude code review into every non-draft PR as a GitHub Action, since GitHub CODEOWNERS only accepts users/teams (not bots). @Hmbown stays the human owner; the review is advisory and posts alongside it. - claude-review.yml: anthropics/claude-code-action@v1 in review mode with track_progress; auth via CLAUDE_CODE_OAUTH_TOKEN (from claude setup-token). No-ops with a notice until the secret is set, so it's safe to merge first. Codex/ChatGPT review is handled out-of-repo via the ChatGPT Codex cloud integration (chatgpt.com/codex), authed by the ChatGPT subscription, so no OpenAI workflow or repo secret is needed. CODEOWNERS documents the split. The review prompt also guards the v0.8.65 EPIC #2608 routing invariant (provider-prefixed model strings are wire ids/hints, not provider-selection proof). Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> | 4 months ago | |
chore: tidy repo root — move DESIGN/PRODUCT to docs, GitHub meta docs to .github Signed-off-by: CodeWhale Bot <bot@codewhale.net> | 1 month ago | |
chore: tidy repo root — move DESIGN/PRODUCT to docs, GitHub meta docs to .github Signed-off-by: CodeWhale Bot <bot@codewhale.net> | 1 month ago | |
docs: clarify sponsor links | 5 months ago | |
ci: cut PR CI to the fast required set; welcome contributor PRs [skip ci] Founder direction (2026-11-07): remove CI/CD steps that cost time without need, use CI conservatively, and make contributor rules standard and welcoming instead of closing or blocking PRs over CI. A read-only audit of two weeks of run history (Sonnet workflow with an adversarial release- engineer critique) drove the list; nothing release-critical is touched. Removed (enforced nothing, duplicated other checks, or gated contributors): - dco.yml (always exited 0), pr-issue-link.yml (red X on ~8% of contributor PRs), auto-close-harvested.yml, pr-gate.yml / issue-gate.yml / approve-contributor.yml and .github/APPROVED_CONTRIBUTORS (dry-run allowlist gate; drops a pull_request_target surface), agent-task-labels.yml (duplicates triage.yml). Moved to manual (workflow_dispatch) only: - codewhale-review.yml (review bot; AGENTS.md says review bots stay off), main-landing.yml (push trigger; run scripts/preflight.sh --check locally), ci.yml test (Linux suite, 54-94 min per PR), safety-gate (18-29 min), msrv, mobile-smoke, npm-wrapper-smoke (macOS leg dropped from the dispatch matrix; the release artifacts cover macOS). - The PR feature release-note receipt step is advisory (continue-on-error). - spam-lockdown keeps only unambiguous spam patterns. Unchanged: Lint and the compile-only Test (windows-latest) stay the required PR checks; release-candidate, release-artifacts, release-parity, release, the mirrors, OHOS and the Windows import guard are untouched. The branch ruleset drops "npm wrapper smoke (ubuntu-latest)" next (founder approved "Lint + 1 compile"). Rules: AGENTS.md, CONTRIBUTING.md, the PR template, AGENT_ETHOS.md and the cw-land skill now say contributor PRs are never closed or blocked because CI is slow, flaky or red for a reason they did not cause; nothing closes a PR automatically; harvesting is a rare, asked-first fallback with the contributor as author; the PR issue line is optional; maintainers reply generously. web/data/agent-docs.generated.json is regenerated from a clean export of main plus this change only. Verified: actionlint with CI's flags (-ignore SC2129/SC2221/SC2222) over all workflows passes; web/scripts/check-facts.mjs passes on the isolated export; only the contribution entry of agent-docs.generated.json changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> | 1 day ago | |
docs: point every link at the codewhale-hq organization Hunter moved the Codewhale repositories to github.com/codewhale-hq on 2026-10-05. Rewrite Hmbown/<moved repo> slugs to codewhale-hq/<repo> in docs, READMEs (all 19), website, CHANGELOGs, workflows, issue templates, Cargo/npm/VS Code/nix/winget metadata, install and updater code, the bundled first-party marketplace catalog and their tests: 1,795 references in 434 files, plus four escaped regex literals. Docker images publish to ghcr.io/codewhale-hq/codewhale from the next release. Old URLs keep working through GitHub's transfer redirects (verified live: API releases/latest, HTML releases/latest, release asset downloads, codeload tarballs, git clone), so released clients keep updating. Left unchanged on purpose: Hmbown/codewhale-cu-plugin (not moved yet; its shipped updater refuses redirects), Hmbown/deepseek-skills, cwc and other repos that did not move; package identities (winget Hmbown.CodeWhale, NSIS publisher); vendor/codewhale-ratatui (frozen reviewed package); and the extension-host GitHub adapter with tools/github/report.rs and their parity fixture, which need a bundle rebuild and move together in a follow-up. README translation stamps updated to the new README.md hash. Validation: npm test (wrapper 101/0, SDK 19/0, extension host 398 passed / 0 failed / 7 skipped, web 763/0) and npm run check:web exit 0 (one pre-existing facts-lib.mjs lint warning). cargo check --workspace --tests --all-features --locked: exit 0. cargo test -p codewhale-cli -p codewhale-release -p codewhale-protocol and the touched codewhale-tui modules (client, cloud_dispatch, commands, dispatch_runner, llm_client::mock, oauth, operate, plugins::marketplace, remote_control, remote_setup, tools::mcp_registry, tools::web::fetch, working_set, tui::ui::tests): all ok, 0 failed. check-readme-translations (18 in sync), readme locales, TUI locale parity, product vocabulary, web locales, contributor credit, plugin claims, release-workflows.test.js and check-versions all pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: CodeWhale Bot <bot@codewhale.net> | 1 month ago | |
docs: 0.10.1 credit accuracy and pre-tag doc fixes - Credit @Water-Run's #6400/#6402 under 0.10.1 (they landed after the v0.10.0 tag); the 0.10.0 entry keeps #6401. Added to the [Unreleased] contributors, docs/CONTRIBUTORS.md v0.10.1 and UNRELEASED_CONTRIBUTORS. - Hand-port the one missing v0.9.1 credit from the #4667 audit: @stream2stream's legacy-session report (#4032) behind #4539. - THIRD_PARTY_NOTICES: Apache-2.0 entry for openai/codex, the source of frame_rate_limiter.rs. - INSTALL.md: node is a dependency of the Hmbown/deepseek-tui tap formula only; the tested-version wording no longer reads as current. - FLEET.md: ChildGrant (#5633, 966ef974e1) and ShellGrant::Verify shipped in v0.10.0; #6298 is re-scoped to the real 0.11 remainder. - web docs: admin access is the /admin login form, not ?token= in the URL. - RUNTIME_API.md: document the /v1/commands composer fields (#6230). - golden_harness.rs: the ink-plane comment no longer describes removed code. - dependabot: ignore rusty_alloc-api >= 2, which fails to compile on macOS (see #6599). Checks: npm test -> 67 + 14 node tests passed, 498 vitest passed, 0 failed; npm run check:web passed; web public-copy vitest 6 passed; check-contributor-credit v0.10.0 OK; check-versions --range-audit-advisory OK; sync-changelog + derive-changelog/facts/install regenerated; blocking-calls, dead-code, command-crate-boundaries, module_graph --check and cargo fmt --check all clean. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> | 1 month ago |
| Files | Last commit | Last update |
|---|---|---|
| 1 month ago | ||
| 1 month ago | ||
| 1 day ago | ||
| 8 minutes ago | ||
| 2 days ago | ||
| 4 months ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 5 months ago | ||
| 1 day ago | ||
| 1 month ago | ||
| 1 month ago |