| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
docs(web): explain plugins and MCP with verified Computer Use setup [skip ci] Answer the integration chooser, actual catalog prerequisites, supported plugin formats, direct-versus-plugin MCP authentication and troubleshooting on the existing paper/blue pages. Link the plugin guide from docs navigation and refresh its plain-text index. Add explicit Computer Use GitHub/contributor links in all18locales and version-aware direct-MCP setup for published CLI0.10.2, whose older built-in bundle is not upgraded by catalog installation. Reconcile repository EN/ZH docs for config precedence, validation/reload, URL-only servers, environment credentials, trust hashes, pinned-source updates and catalog freshness. Current marketplace and unreleased source remain separate from installed-release claims; DSH and MCPApps are not presented as universally qualified. Verified locally:47existingwebtests passed (26dictionary/copy+21llms/docsIA); focused ESLint, TypeScript, locale/GT checks and diff check passed. Initial custom test harness missed Vite alias configuration in2suites; corrected harness passed those21checks. Desktop1280/mobile390 EN/ZH browser review passed; stale development module hydration mismatch cleared after owned dev-server restart. Published CLI0.10.2 discovered current CU0.16.1 tools and executed request_access through a local synthetic model:ok=true/viaapp, accessibilitygranted, screen-captureprobeok. No input or provider spend. Credential-free Cloudflare Docs MCP discovery listed2tools. Existing-helper setup is not clean-Mac/app-task qualification. Generated agent documentation uses51hashedinputs: our5revieweddocs plus committed da143039f79 content for all other inputs, excluding active peer GUIDE/feature/native drafts. Full clean web validation/deployment follows this frozen commit; no Engine release qualification. CU setup README is carried separately by codewhale-cu-plugin afb98e8. Evidence:CW/artifacts/plugin-mcp-discoverability-20261107. Tracking:CW-7848; CU acceptance remains CW-6732. | 2 天前 | |
feat(web/i18n): route fr, de, ca, hi, tr, it, pl, and ar (RTL) as partial locales Wave-2 website localization, reaching parity with the v0.9.2 TUI packs and adding the missing major languages: - Full chrome + home + docs-guide dictionaries for fr, de, ca, hi, tr, it, pl (native rewrites; product nouns and commands stay literal, terminology aligned with crates/tui/locales/<pack>.json). - ar: same dictionaries plus minimal RTL plumbing — LocaleEntry gains a dir field (defaulting ltr) and the root [locale] layout derives the html dir attribute from the registry (ar renders dir="rtl"). - Statuses flipped planned -> partial; partial keeps the honest switcher badge and English fallback for page bodies (shipped requires translated first-class page bodies, per the zh precedent). - Registered in dictionaries/index.ts; OG locale tags added; hreflang and sitemap coverage derives from ALL_LOCALES and needs no edit (verified). - Tests updated to the new registry: dictionary set, detection of the new routed tags, wave-2 partial assertions, dir derivation, and a documented German loanword exception (Community). | 2 个月前 | |
web(geo): advertise only translated page variants Keep partial-locale routes available while canonicalizing English fallbacks to their source. Generate sitemap and hreflang entries from page-body translation coverage and omit synthetic last-modified timestamps. Verified with the complete web gate: generated facts, facts/docs/locale checks, 267 tests, lint, and the production build. Signed-off-by: Hunter Bown <hunter@hunterbown.com> | 2 个月前 | |
web: index the feature catalogue and agent documentation Make the 72 registry capabilities findable in the catalogue and docs search. Derive status, surface badges and documentation links through the existing facts pipeline. Add /features.json, 26 raw Markdown topic routes and /llms-full.txt; align navigation, sitemap and explicit crawler policy. Release JSON-LD uses only stable rows with a declared since version at or before the published install version. Put the coding-agent category in home metadata and identity across the actual 18 routed locale packs. Correct session receipts, default Auto routing, ACP and read-only MCP server claims; mark Computer Use preview. Document request preview, LSP, execution policy, skills and the reviewed Claude Code import subset. Ratatui component indexing becomes English-only; its hub retains existing locale coverage. Root gate on base9ebbb063da plus 137 frozen web paths and the separately frozen Q13/X2 native/doc inputs: 1,312 passed; 0 failed; 7 skipped (wrapper101, SDK19, extension host413, security7, Vitest772). Actual receipt lines: "# pass 413" "# fail 0" "# skipped 7" "Tests 772 passed (772)" npm ci, facts/latest-release/docs/local GT catalogs, lint, tsc and production build passed. One existing lint warning. Final LLMS-only copy correction: "Tests 3 passed (3)"; fresh production build passed. The existing buildFacts comment was moved back to its owner without an executable change. Local browser inspection: 36 pages at 375/768/1280 in en/zh/ja/ar, each captured full-page and viewport. All72 feature queries and26 raw Markdown routes passed; every raw topic appears in the full export; zero page errors and no horizontal overflow. The harness disables speculative link prefetch and answers local telemetry with204. This does not establish deployed-site, crawler indexing, WAF or Search Console acceptance. No new tests or code comments; obsolete existing assertions updated. No deployment. | 28 天前 | |
fix(web): honour Accept-Language q weights in locale detection Defect: detectLocaleFromHeaders read Accept-Language positionally — acceptLanguage.split(",").map((s) => s.split(";")[0]) — and returned the first routed tag it saw. The weights were parsed off and thrown away, so: * Accept-Language: en;q=0.2, ja;q=0.9 served English to a reader who asked for Japanese; * Accept-Language: en;q=0, ja;q=0.9 served English to a reader who had explicitly marked English not acceptable — q=0 is a refusal (RFC 9110 §12.4.2), not a low preference. The module docstring claimed the walk was "in the header's preference order", which is only true for headers that happen to be pre-sorted. This runs in middleware, so the wrong answer is a 307 to the wrong locale plus a year-long NEXT_LOCALE cookie pinning it there. Fix: acceptLanguageTags() parses each entry's weight, drops q=0, sorts descending by weight with original order as a stable tie-break, and the detector walks that. A malformed weight stays at the default of 1 rather than being guessed at. Evidence: four new cases in lib/i18n/detect.test.ts. Restoring the positional walk fails two of them with expected 'en' to be 'ja'. The pre-existing ordered-header cases still pass unchanged. npm test 317 passed, npm run lint clean, npx tsc --noEmit clean. Implemented with agent assistance. Signed-off-by: Hunter Bown <hmbown@gmail.com> | 2 个月前 | |
fix(web): honour Accept-Language q weights in locale detection Defect: detectLocaleFromHeaders read Accept-Language positionally — acceptLanguage.split(",").map((s) => s.split(";")[0]) — and returned the first routed tag it saw. The weights were parsed off and thrown away, so: * Accept-Language: en;q=0.2, ja;q=0.9 served English to a reader who asked for Japanese; * Accept-Language: en;q=0, ja;q=0.9 served English to a reader who had explicitly marked English not acceptable — q=0 is a refusal (RFC 9110 §12.4.2), not a low preference. The module docstring claimed the walk was "in the header's preference order", which is only true for headers that happen to be pre-sorted. This runs in middleware, so the wrong answer is a 307 to the wrong locale plus a year-long NEXT_LOCALE cookie pinning it there. Fix: acceptLanguageTags() parses each entry's weight, drops q=0, sorts descending by weight with original order as a stable tie-break, and the detector walks that. A malformed weight stays at the default of 1 rather than being guessed at. Evidence: four new cases in lib/i18n/detect.test.ts. Restoring the positional walk fails two of them with expected 'en' to be 'ja'. The pre-existing ordered-header cases still pass unchanged. npm test 317 passed, npm run lint clean, npx tsc --noEmit clean. Implemented with agent assistance. Signed-off-by: Hunter Bown <hmbown@gmail.com> | 2 个月前 | |
docs(web): prepare simpler Computer Use onboarding (CW-6732) [skip ci] Describe the ordinary Computer Use plugin and persistent native host approval across apps, models and tasks. Make the background diagnostic optional by removing it from the default onboarding sequence in all 18 locales. Explain the compact controller, global Stop and saved-access settings; retain the optional live preview. Validation: release validators 26/26, dictionary checks 20/20 after updating the existing onboarding step-count assertion, locale completeness and GT catalog parity pass. Final headline edits only simplify prose; keys and flow structure are unchanged. Source preparation only. Deploy this wording with the qualified CU 0.13.0 release and normal-plugin installation route; the current published 0.12.0 helper does not implement this flow. No website deployment or CU publication performed. | 14 天前 | |
Improve product copy and use the founder terminal screenshot Lead with creating and automating using the models the user chooses. Remove the hero tagline, use connected prose, welcome issues and PRs, and carry the same home/footer changes across18 locale dictionaries. Update all19 README screenshots to the supplied unmodified171acee689aa image and keep its0.9.12 preview identity distinct from unreleased0.9.13. Verified final source411 web tests passed,0failed; locale/GT and TypeScript checks passed; lint0errors/2existing image warnings. All68 files remain byte-identical to the verified pause manifest. Fresh browser review confirms hero, transparent mark and legible supplied screenshot. Earlier EN/ZH360px checks passed without horizontal overflow. Whitespace check passed. Root npm test/check:web unavailable (scripts absent); no root npm gate pass claimed. No public push or deploy. | 2 个月前 | |
fix(web): resync the GT catalogs and keep generated data out of the isZh ceiling The release-candidate npm test failed 2 of 772 web tests, both left by 8c6e61c82a (CW-7497, per-release notes pages). Web vitest is not a CI job, so neither surfaced. - gt-site: 8c6e61c82a added six changelog dictionary keys (versionMetaTitle, versionMetaDescription, versionKicker, versionLead, versionLeadUndated, allReleasesLink) without re-exporting gt-catalog/{en,zh}.json. Exported with npm run i18n:gt -- export, the command the check names. - iszh-ceiling: 8c6e61c82a also generates lib/release-notes.generated.ts (gitignored, written by prebuild) from CHANGELOG.md, whose prose mentions "isZh" in two old entries. The ceiling counts isZh *branching*, so it now skips *.generated.* files the same way it skips *.test.* files. The ceiling stays 2. The failure only appeared after a local build had written the file, so a clean checkout passed and a built one did not. Checks: npm --prefix web test = 74 files, 772 passed, 0 failed (was 2 failed). Root npm test before this fix: workspace and extension-host node suites 101/101, 19/19, 413 passed + 7 skipped of 420, 7/7; npm run check:web exit 0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> | 18 天前 | |
fix(web): recover warm paper and original water accents [skip ci] Restore the founder-selected warm-paper website after reviewing the existing Moda boards, stored homepage capture, Claude design files and historical water source. Reuse the eight original hero paths from48140294df0 and its fading footer current texture. Keep the original C-whale, current typography, genuine terminal gallery, concise product copy, Computer Use and automatic releases. Use instance-specific SVG filter IDs, static pointer-inert decoration and forced-color hiding. Keep reading sections on paper and scope dark roles to the actual terminal frame and closing sea. Recover earlier paper neutrals and the readable1877c9-to0b48bb blue action ramp; retain the shared geometry tokens. Use five primary nav links so translated desktop chrome fits at1024px without shrinking controls; keep Changelog in the compact menu, release section and footer. Correct the existing focus-role and paper-color contract assertions. Consolidate the three superseded website changelog bullets into one accurate entry and mechanically sync the embedded changelog. Verified: scoped ESLint and TypeScript --noEmit --incremental false passed; 153 existing tests across16 relevant suites passed (the paper expectation was corrected and its five-test role suite rerun); embedded changelog --check and git diff --check passed. Real browser: EN desktop,390px mobile, Spanish1024px single-row header, ZH dark, current terminal/CU versions, pointer-inert water, forced-colors/reduced-motion behavior, no sampled page overflow or JS errors. Native PNG color-profile verification also found that earlier JPEG previews dropped Rec2020 ICC data and shifted blues; review artifacts now retain the native profile. Existing Moda preview updated in42 free deterministic edits, zero skipped ops and clean desktop/mobile renders. Historical audit and exact receipts: CW/artifacts/website-repair-20261106/. Final protected web validation/publication follows this source commit. No Engine release qualification or publication is claimed. | 2 天前 | |
docs(web): stop steering visitors into paused accounts; say what 0.10.2 adds Codewhale accounts, account key storage and the paid product are paused until a frontier security review is available (CURRENT_DECISIONS §38, 2026-10-18). The live site still sent every visitor toward them, and several pages presented 0.10.2 as released. The plan came from a read-only audit of README, site and GitHub copy against the code and CHANGELOG (artifacts/readme-site-20261019/plan.md). Account pause (honesty): - Masthead and mobile menu: "Sign in" removed. - Home and /product: "Create an account" link, the account sentence and the Cloud computers row removed. Hosted web is "In development, not open yet" and points to codewhale web. The desktop row describes what the unreleased app does. - /signin lede and meta: new accounts are not open. /signup redirects to /signin and leaves the sitemap and llms.txt. The signup-counting disclosure copy is updated. - /docs/computers (account-only cloud agents) redirects to Fleet. - Auth docs: "Codewhale accounts", never needed and not open. The account-keys row is gone. - docs/INSTALL.md and zh_hans: "One account for your provider keys" is replaced by "No account needed". docs/CONFIGURATION.md and zh_hans: the account-key section no longer promotes account key storage and keeps only list/remove for existing accounts. Release labels (honesty): - docs/features.toml: chat-color and terminal-dock carry since 0.10.2; the account-login summary is corrected. - /features shows rows newer than the latest published release as source candidates. - /changelog marks a candidate version with the unreleased note and hides compare links to tags that do not exist. - Runtime page "Source version"; FAQ provider count is "the current source declares". - Review and pet docs say what 0.10.1 does and what 0.10.2 adds. Excitement through specifics: - Hero: "The open-source coding agent for any model"; heading "Build and automate from your terminal"; footer tagline to match. - Model facts name the default: deepseek-flash, now DeepSeek-V4.1-Flash. New fact: ChatGPT plan sign-in (experimental). The models page says what changed on 2026-10-17 and titles its table "source v{version}". - New "Coming in v0.10.2" band (lib/content/release-highlights.ts): /pet on, /workbar terminal, /undo, Plan to Work, the curl/wget credential hold and DeepSeek Search. It flips to "New in" at the tag and hides itself when stale. - Community line renders the contributor count from data. - web/MESSAGING.md synced. Every changed dictionary value is translated in all locales; deleted keys are removed everywhere. Generated files come from their generators (prebuild, i18n:gt export). Coded by GPT-6 Astra (codex, workspace-write). Claude added the CONFIGURATION.md sections Astra flagged, regenerated, and ran the gate. Verification: - npm test (repo root): node suites 101/19/413 (7 skipped)/7 passed, 0 failed; Vitest 74 files, 772 tests passed - npm run check:web: production build succeeded - web: check:locales PASS, check:facts OK, check:docs PASS, lint and tsc clean - cargo test -p codewhale-tui --test feature_registry: 2 passed Not done: no visual render check, and no deploy. The live site changes only when a maintainer runs web.yml. Outside this repo, app.codewhale.net/signup still serves "Create account". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NBKbhx19BRbZtvWK8rVKjz | 21 天前 | |
fix(web): restore clickable controls on non-English routes Signed-off-by: Hunter Bown <hmbown@gmail.com> | 2 个月前 | |
fix(web): restore clickable controls on non-English routes Signed-off-by: Hunter Bown <hmbown@gmail.com> | 2 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 天前 | ||
| 2 个月前 | ||
| 2 个月前 | ||
| 28 天前 | ||
| 2 个月前 | ||
| 2 个月前 | ||
| 14 天前 | ||
| 2 个月前 | ||
| 18 天前 | ||
| 2 天前 | ||
| 21 天前 | ||
| 2 个月前 | ||
| 2 个月前 |