| 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 | |
fix(release): assemble container images from native artifacts | 2 months ago | |
docs: correct FreeBSD source-build claims (#1097) FreeBSD stays a source-only target, with no prebuilt asset and no release-matrix row (founder decision 2026-10-25, item 14). This change fixes the claims the issue sweep found to be false or stale: - packaging/freebsd/README.md said x86_64-unknown-freebsd "is validated in CI ... on the release/0.9.5 branch". No job does this: git grep -i freebsd -- .github scripts matches only a YAML comment. The README now says no CI job checks the target and gives the cargo check command to run on a FreeBSD host. - The README pointed to crates/tui/build.rs for the rquickjs bindgen fix. 1582ba9653/5eb0385e8f touch only crates/workflow-js/Cargo.toml, which holds the target_os = "freebsd" bindgen dependency. It now names that file. - The README now states the Rust minimum, 1.89 (Cargo.toml rust-version), and its verification block no longer says ">= 1.88". The matrix list now says Linux musl arm64, which is the target the matrix builds, not gnu. - The release-artifacts.yml build-job comment no longer claims a FreeBSD cargo check. It now says FreeBSD has no prebuilt asset, no npm binary and no CI check. - "OpenBSD" is dropped from the support-table row in docs/INSTALL.md and docs/zh_hans/INSTALL.md. workflow-js has no rquickjs bindgen entry for openbsd, and no OpenBSD build has been verified. Ignore the vendor Ratatui target directory produced by its separate-workspace test command; generated output is preserved in the SSD cache, not committed. Docs, ignore rules and a YAML comment only; no product behaviour changes, so no CHANGELOG bullet. Verified by read-only greps against the worktree. No FreeBSD compile was attempted. Verified as one frozen batch at 7db526a725 plus consensus patch sha256 d6418055436eaada55f4cbedc954a0eeeb51d9d922716a3588006cf7932fab45: - scripts/with-hermetic-test-home.sh scripts/dev-cargo.sh nextest run -p codewhale-tui -p codewhale-localization --lib --locked: 15343 run, 15341 passed, 2 failed, 25 skipped; build 3m41s. The two fixed-width rendered-fixture failures came from the long SSD TMPDIR wrapping paths mid-needle. Same source/binary, shorter SSD TMPDIR, only those two tests rerun: 2 passed, 15312 skipped. Distinct passing coverage across both runs: 15289 TUI + 54 localization tests. - scripts/with-hermetic-test-home.sh scripts/dev-cargo.sh test --manifest-path vendor/codewhale-ratatui/Cargo.toml --locked --all-targets: 145 passed, 0 failed (128 library and 17 example tests). - fmt and diff checks passed; changelog sync passed; runtime boundary PASS (120 closure modules); dead-code budget 212; blocking-call budget 543 across 165 files; locale parity 2583 keys in all 15 packs. - The vocabulary guard initially failed on an already-published advertised legacy alias. Both refuters confirmed the docs-only correction; the unchanged guard then passed. Web prebuild and check-facts passed. Before peer reconciliation, only .gitignore, docs/MODES.md and generated web documentation changed after native tests; frozen compiler inputs were identical. Published peer commits aa45bf84ef/485382f81d then advanced main. Their exact diff was integrated, preserving their ancestry and regenerating web docs. Focused reconciliation nextest (TUI ops/runtime_info/spawn and CLI cloud callers): 117 passed, 0 failed, 15698 skipped; source remained frozen (104 TUI, 13 CLI). Command/filter and source SHA256 are retained in coordination/land-0103-20261025/reconciliation-test-run.json. Final integrated tree f297b67c73d4d863b9a770ae3f4ad64c5c2ac319 is checked against the regenerated commits. macOS ld emitted its __eh_frame size warning. No hosted CI, FreeBSD/Linux compile, paid provider call, install, deploy, or release is claimed. This does not resolve #1097: the npm prebuilt and pkg port asks remain open. Refs #1097 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> | 14 days ago | |
fix(packaging): generate a valid manifest for the published WinGet route [skip ci] The stale singleton had no package locale, exceeded the one-installer schema limit and repeated ZIP installer identities. Match the actual portable x64 contract, VC++ dependency and codewhale command. Look up the exact compatibility asset in the release checksum manifest and keep the mirror byte-identical. Native WinGet 1.29.380 validated the generated 0.10.1 and 0.10.2 manifests against the actual published checksums. Four invalid inputs preserved both outputs. Sixteen ordinary-user checks on Windows 11 ARM64 covered x64 0.10.1 install, upgrade to 0.10.2, payload hashes, candidate owner delegation, removal, and exact user PATH restoration. ShellCheck, bilingual guide rendering and embedded changelog sync passed. Distribution publication and native Windows 10 floor validation remain separate. | 7 days ago |