26 commits

Author	SHA1	Message	Date
lefarcen	98a2c63973	feat(daemon): add Antigravity agent adapter (#3157) ... * feat(daemon): add Antigravity agent adapter Adds Google Antigravity (`agy` CLI) as a coding-agent runtime. Detection picks up `agy` on PATH, the daemon spawns `agy -p "<prompt>"` for a single non-interactive turn, and the assistant text reply streams back on stdout. OAuth is shared with the Antigravity IDE through the system keyring, so users who have signed into the desktop app are authenticated on first run with no extra step. `agy` v1.0.3 has no JSON / stream-json / ACP output mode (upstream issue #119), no `--model` flag (issue #35), and no MCP forwarding hook yet — the adapter ships with `streamFormat: 'plain'` and a single `default` fallback model so the model picker doesn't mislead users into thinking their choice is wired through. We will upgrade buildArgs + add a dedicated event parser when upstream ships structured output. Also gitignores `.antigravitycli/`, the project-local config directory `agy` auto-creates on every run (upstream issue #175). * fix(daemon): Antigravity adapter — stdin prompt, brand icon, form loop, empty-output guard - Switch prompt delivery from argv to stdin (`agy -p -`) to avoid the 30KB maxPromptArgBytes limit that blocked real-world composed prompts - Add official Antigravity brand SVG icon to agent picker - Fix repeated question-form loop for plain agents by injecting an OVERRIDE block when form answers are already present in the transcript - Add empty-output guard for plain agents so expired auth or silent failures surface a user-visible error instead of a blank "Done" turn * feat(daemon): expand Antigravity adapter — model picker, form-loop fix, OAuth launcher, log-file classification PR #3157 follow-up integrating four iterations from end-to-end manual testing on Gemini 3.5 Flash + GPT-OSS 120B Medium through `agy` v1.0.3. Each section is independently verifiable; combined they're what made the first successful artifact generation work end-to-end. ## Model picker via settings.json (agy has no --model flag) agy v1.0.3 ships no `--model` CLI flag (upstream issue #35), but the TUI Switch-Model picker writes the chosen label to `~/.gemini/antigravity-cli/settings.json`'s `"model"` field, and every `-p` invocation re-reads that file on startup — verified by capturing the `--log-file` line `Propagating selected model override to backend: label="<model>"`. Antigravity's `fallbackModels` now lists the 8 labels its TUI exposes (Gemini 3.1 Pro / 3.5 Flash variants, Claude Sonnet/Opus 4.6 Thinking, GPT-OSS 120B Medium) and `buildArgs` persists the user's choice to settings.json right before spawn. The synthetic `default` id is preserved — picking it leaves settings.json untouched so a user who switches models from agy's own TUI keeps their choice. Introduces `RuntimeAgentDef.supportsCustomModel?: boolean`. AMR's hardcoded blocklist in `SettingsDialog.tsx` migrates to the declarative flag (it rejects free-form ids at the ACP layer), and antigravity opts out because its label set is a server-side enum that silently fails on unrecognised strings. ## Form-loop fix (transcript sanitizer + stronger OVERRIDE) The discovery form loop on weak/medium plain-stream models (GPT-OSS 120B Medium, Gemini 3.5 Flash) had two reinforcing causes: 1. `buildDaemonTranscript` packed the prior assistant turn's literal `<question-form>` markup into the user request on the next turn, giving the model a template to echo. New `sanitizePriorAssistantTurnForTranscript` strips `<question-form>...</question-form>` blocks and ```json fences that match form-schema shape, replacing them with a brief placeholder. User content is preserved verbatim (a user who legitimately mentions `<question-form>` in chat keeps their message intact). 2. The OVERRIDE block on form-answered turns was 4 lines and only banned the bare `<question-form>` tag — models still emitted the fenced JSON, form-asking prose ("Got it — tell me the following"), and fake system events ("subagents stopped"). The new `FORM_ANSWERED_SYSTEM_OVERRIDE` enumerates each anti-pattern and pins them via tests, so silently weakening any line reintroduces the regression. Also adds RuntimeAgentDef.resumesSessionViaCli + RuntimeContext. hasPriorAssistantTurn as forward-looking abstractions (skipTranscript option on composeChatUserRequestForAgent). Antigravity does NOT opt in — agy's `-c` resume activates an internal agentic loop with tool retries and fallback-to-cached-response on tool errors that the OD system prompt cannot steer; reverted after seeing byte-identical form re-emissions caused by agy's own retry logic, not OD's transcript. ## One-click OAuth via system terminal agy print mode can't complete Google Sign-In on its own (the OAuth callback page asks the user to paste an auth code back into agy, but `-p` has no input field). Before this commit the auth banner only told the user to "open a terminal yourself." Adds `POST /api/agents/antigravity/oauth-launch` and a cross-platform launcher in `runtimes/terminal-launch.ts`: - macOS: osascript → Terminal.app `do script "agy"` + activate - Linux: tries x-terminal-emulator, gnome-terminal, konsole, xfce4-terminal, xterm in order - Windows: `cmd /c start "Open Design" cmd /k agy` The endpoint hardcodes the `agy` command (no user input → no shell injection surface) and is loopback-gated like the other daemon endpoints. The chat's `AGENT_AUTH_REQUIRED` banner now renders a "Sign in via terminal" button next to Retry; clicking it spawns the terminal so the user can finish OAuth in one click. ## Silent-failure classification (auth vs quota via --log-file) agy print mode is silent on stdout/stderr for both missing-OAuth AND quota-exhausted failures — the upstream `RESOURCE_EXHAUSTED (code 429): Individual quota reached` and the `not logged into Antigravity` line only surface in agy's `--log-file`. Without log inspection the daemon misread quota as "auth required" and showed the wrong banner. `RuntimeContext.agentLogFilePath` carries a daemon-owned per-run temp path that antigravity's buildArgs translates to `--log-file <path>`. The empty-output guard now reads that log on a `code === 0 && !childStdoutSeen` exit, feeds the tail to `classifyAgentServiceFailure`, and routes: - "not logged into Antigravity" → AGENT_AUTH_REQUIRED with antigravityAuthGuidance - "RESOURCE_EXHAUSTED" / "quota" / → RATE_LIMITED with "Individual quota reached" antigravityQuotaGuidance - none of the above (rare) → fall back to auth guidance as the most likely cause Both surface a terminal launcher in the auth banner: auth gets "Sign in via terminal", quota gets "Switch model in terminal" — same endpoint, contextual label. The handler is identical (open agy in a terminal); the user either signs in or uses agy's Switch Model picker to pick a model with available quota. ## Validation - `pnpm guard` pass - `pnpm --filter @open-design/daemon` runtime + telemetry suites: 192 passed, 1 skipped (the 1 pre-existing `task-type` failure on origin/main is unrelated to this change) - `pnpm --filter @open-design/web` typecheck pass; sse / amr-guidance / AgentIcon suites pass (51 web tests) - Manual end-to-end on darwin + Gemini 3.5 Flash and GPT-OSS 120B Medium: turn-1 question-form rendered correctly, turn-2 produced `<artifact>` with full HTML (3.3KB Modern Minimal design) instead of re-emitting the form. agy `--log-file` content correctly classified as RATE_LIMITED when Gemini Pro quota was exhausted, and as AGENT_AUTH_REQUIRED when keychain was cleared. * fix(web/test): align amrAgent fixture with supportsCustomModel contract The AMR agent definition in the daemon ships `supportsCustomModel: false` so the Settings model picker hides the free-text "Custom…" option. The PR changed `allowCustomModel` from `selected.id !== 'amr'` (hardcoded) to `selected.supportsCustomModel !== false` (declarative), but the test fixture was not updated to carry the same field — causing the `__custom__` sentinel to appear in the picker under test. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): align formAnswerTransition wording with main + scope build directive to discovery CI surfaced two failures on the merge with main: - chat-route.test marks submitted discovery form answers ... expected the main-version wording 'Do not emit another <formId> form.' - telemetry-message-finalization keeps non-discovery form answers active ... expected task-type to fall through the else branch ('Treat these form answers as the active user turn'), not the discovery RULE 2/RULE 3 build branch. The colleague's earlier fba1e40b form-loop fix tightened both pieces (stronger wording + grouped discovery|task-type into the build branch) but didn't update the tests that pin the contract. Revert the transition wording to main and re-scope the build directive to 'discovery' only. The aggressive form-loop suppression we added in this PR now lives in the system-prompt FORM_ANSWERED_SYSTEM_OVERRIDE block, which is far stronger than the user-request transition text this commit reverts. * fix(daemon): scope formOverride by form id, detach Linux terminal, move agy log cleanup to finally - FORM_ANSWERED_GENERIC_OVERRIDE: new exported constant for non-discovery/ non-task-type form ids; contains only the "do not re-ask" suppression without the RULE 2 / RULE 3 / artifact directive. - formAnswerTransitionForCurrentPrompt: extend build-transition branch to include task-type alongside discovery, keeping user-turn and system override consistent. - Prompt assembly (server.ts ~10848): derive formOverride from the parsed form id — FORM_ANSWERED_SYSTEM_OVERRIDE for discovery/task-type, FORM_ANSWERED_GENERIC_OVERRIDE for all other form ids, empty otherwise. - launchOnLinux: replace execFileAsync (waited for terminal exit, 3 s cap) with spawn({ detached: true, stdio: 'ignore' }) + unref(); resolve on the 'spawn' event so long-lived interactive terminals (xterm, konsole) are not killed mid-OAuth-flow. - Antigravity log cleanup: move fs.promises.unlink(agentLogFilePath) into a try/finally wrapper around the close handler so every exit path (success, failure, cancel, non-zero exit) cleans up the per-run temp file, preventing unbounded /tmp accumulation. - Tests: rename task-type case to assert build-transition behaviour; add generic-form-id case (preferences) pinning the non-build path; add FORM_ANSWERED_GENERIC_OVERRIDE content assertions. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): switch Antigravity buildArgs to chat subcommand invocation Replace top-level `-p -` with `agy chat [--log-file …] -` so the adapter uses the documented chat subcommand and stdin sentinel instead of the unrecognised global -p flag. Update the agent-args test description and all four deepEqual assertions to assert the ['chat', '-'] shape. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * test(daemon): drop real-platform default-launch assertion from terminal-launch suite The removed test called launchAgentInSystemTerminal('agy') with no platform override, which invokes the real system terminal on every developer machine running the daemon test suite (Terminal.app on macOS, cmd.exe on Windows, xterm/gnome-terminal on Linux). That is an unacceptable OS side effect for a unit test. The behaviour being asserted — that omitting platform selects process.platform — is a TypeScript default-parameter guarantee, not a runtime invariant that needs an integration test. The remaining 'aix' case continues to pin the unsupported-platform failure shape. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): buffer Antigravity stdout to suppress auth URL before close-time classifier The plain-stream close handler at code===0 can detect an agy OAuth prompt in agentStdoutTail and emit AGENT_AUTH_REQUIRED, but by the time close fires the stdout chunk has already been forwarded to the client via the plain-stream `send('stdout', { chunk })` path. This leaves both the raw OAuth URL and the terminal-launch guidance visible in chat. Buffer all stdout chunks for the `antigravity` agent instead of forwarding them immediately. The existing close-time auth-prompt guard (code===0, !trackingSubstantiveOutput, childStdoutSeen) returns early when it detects the auth pattern, leaving the buffer unflushed and the OAuth URL out of the SSE stream. For legitimate assistant output the buffer is flushed in order just before design.runs.finish so the chunks still arrive before the run's finished event. Adds a chat-route integration test using a fake `agy` that exits 0 after printing the canonical auth prompt; asserts that the run emits AGENT_AUTH_REQUIRED with no event: stdout delta containing the URL. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * test(daemon): isolate antigravity buildArgs argv test from real settings file Pass a temp antigravitySettingsPath in the RuntimeContext for the withModel argv assertion so unit tests do not touch ~/.gemini/antigravity-cli/settings.json. Adds the optional antigravitySettingsPath field to RuntimeContext and threads it through buildArgs to writeAntigravityModelSelection; production callers leave it undefined, preserving the existing default path. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): revert Antigravity buildArgs to `-p -` (the only working agy v1.0.3 invocation) The looper-reviewer-bot reported `chat` as agy's headless subcommand based on its environment's agy build, and looper-fixer applied that shape. The installed CLI (`agy --version` reports `1.0.3`) does NOT expose a `chat` subcommand — `agy --help`'s `Available subcommands` section lists only `changelog / help / install / plugin / update`, and `agy chat - < prompt` exits 0 with empty stdout (the daemon then forwards it as a 'successful' empty reply, exactly the failure mode the auth/quota guard at server.ts ~12090 is meant to catch — for the wrong reason). `-p` is the documented print-mode flag (`Short alias for --print`) and `agy -p -` reads the prompt from stdin and prints the model reply, which the entire end-to-end test sequence in this PR has verified against (form-loop fix, settings.json model routing, log-file classification all confirmed working on Gemini 3.5 Flash + GPT-OSS 120B Medium with this invocation). Updates the agent-args test to pin `['-p', '-']` instead of `['chat', '-']` and adds an inline comment in antigravity.ts noting that `chat` may exist in a future agy build but is not the contract on the installed CLI today. * fix(daemon): serialize Antigravity concrete-model spawns to dodge settings.json race Reviewer (looper) flagged a concurrency race in the model-routing path: ~/.gemini/antigravity-cli/settings.json is process-global, so two OD runs starting close together with different concrete models can race the file — run A writes model A, run B writes model B, then A's agy finally reads settings.json and executes on model B. The Settings model picker becomes nondeterministic under parallel conversations. Adds a per-process promise chain in antigravity.ts: - acquireAntigravityModelLock(): chain-await + return release fn - waitForAgyToReadModel(logPath, expected): polls agy's --log-file for the upstream signal 'Propagating selected model override to backend: label="<X>"' which model_config_manager.go emits once agy has finished reading settings.json. Returns true on observed match, false on timeout. Regex-escapes the expected label so '(' / ')' in 'GPT-OSS 120B (Medium)' match literally, not as a capture group. server.ts spawn pipeline now acquires the lock BEFORE buildArgs (which performs the settings.json write) and schedules a release-once handler that fires when EITHER (a) the log-file confirms agy read the model or (b) the child exits — the exit fallback prevents a stuck/crashed agy from starving the queue for every subsequent antigravity spawn. Default-model spawns bypass the lock entirely: their buildArgs doesn't touch settings.json, so there's nothing to serialize. Tests pin: - FIFO ordering across 2 / 3 concurrent acquirers - Wait helper's regex correctly matches parenthesized labels - Wait helper does NOT match a different model with shared prefix - Wait helper swallows missing-log-file errors and returns false on timeout (no spawn-pipeline crash if the log never appears) 194 → 198 passing runtime tests, 0 regressions. * fix(daemon): close Antigravity lock release race on slow agy startup (looper #263fd2fe7) Reviewer flagged that the previous serialization scheduled `releaseOnce` in `.finally()` on waitForAgyToReadModel — meaning the helper's `false` timeout return ALSO released the lock. If agy took longer than the 15s polling window to read settings.json (cold start, swap-thrash, slow network handshake to the upstream backend), run A's lock dropped at 15s, run B rewrote settings.json with model B, and run A's still-starting agy then read the wrong model. Same race the original mutex was meant to close. Fix the release semantics to be release-on-confirmation-only: - waitForAgyToReadModel: `false` now strictly means 'I gave up polling,' not 'agy definitely did not read this.' Document the contract so a future caller can't conflate the two. Add an optional AbortSignal so server.ts can stop polling when the child exits — without it, the leftover watcher could outlive the run and accidentally match a later concurrent run's log content, releasing the wrong lock. - server.ts: schedule `releaseOnce` only when waitForAgyToReadModel returns true. The exit handler (which fires for crashes, fast exits, normal completion) is now the canonical fallback that releases the lock no matter what — the queue can't starve permanently because agy always exits eventually. The exit handler also fires the AbortController so the watcher cleans up. New tests pin: - timeout returns false WITHOUT any release-implying side effect - already-aborted signal short-circuits (no readFile calls) - abort mid-poll wakes the helper from its setTimeout (no multi-hundred-ms hang waiting out a poll interval that no longer matters) 198 → 201 passing runtime tests, 0 regressions. --------- Co-authored-by: qiongyu1999 <2694684348@qq.com>	2026-05-29 05:43:37 +00:00
Jane	439f071cb0	feat(landing-page): replicate #2469 SEO content with deploy + regression fixes (#2605) ... * chore(landing-page): bring PR #2469 content wholesale onto post-revert main Step 1 of replicating @pftom's #2469 work without the deploy-blocking issues that forced #2603. This commit copies the full \`apps/landing-page/\` diff from #2469's HEAD (`9d2a4f1`) onto current main verbatim — every i18n bundle, every page rewrite, every \`[locale]/\` wrapper. Subsequent commits on this branch then surgically restore the SEO fixes that #2469 silently regressed and configure the sitemap to survive the Cloudflare Pages 25 MiB limit, so deploy is healthy when this lands. What's in this commit - Tom's i18n bundle: \`i18n.ts\` (5377 lines), \`home-page-i18n.ts\`, \`info-page-i18n.ts\`, \`landing-ui-i18n.ts\`, \`content-i18n.ts\` (~10K lines total of locale data) - 18 landing-page locales: en, zh, zh-tw, ja, ko, de, fr, ru, es, pt-br, it, vi, pl, id, nl, ar, tr, uk - All existing pages rewritten to consume the new i18n bundle - Full \`[locale]/<route>/\` wrapper tree for every catalog page - \`plugin-registry.ts\` rewrite, \`catalog.ts\` adjustments - \`astro.config.ts\` route + sitemap reconfiguration - \`public/_headers\`, \`public/_redirects\`, \`public/favicon.svg\` adds - \`_components/locale-switcher-script.astro\` add What's intentionally NOT done in this commit (handled in follow-ups on this same branch): - Restore brand mark 44px + rounded corners (was lost from #2588) - Restore HA SoftwareApplication \`alternateName\` array (was lost from #2566) - Restore HA \`url\` canonical pointing at the landing page (was lost from #2586) - Restore Product/Library/Tutorials/Blog nav grouping (was lost from #2588) - Restore catalog-card padding 24px (was lost from #2600) - Configure sitemap to filter \`[locale]/\` routes so the generated XML stays under 25 MiB and Cloudflare Pages accepts the deploy - Add \`/zh-CN/* → /zh/*\` redirects for backwards-compatibility with any externally-linked OD-canonical locale URLs Validation so far - \`pnpm --filter @open-design/landing-page typecheck\` — 0 errors * fix(landing-page): unblock deploy + restore SEO regressions on top of #2469 Step 2 of replicating @pftom's #2469. The previous commit on this branch brings #2469's content wholesale; this commit applies the surgical fixes that make the result actually deploy and preserves the SEO improvements that #2469 silently regressed. Fix 1 — sitemap stays under Cloudflare Pages 25 MiB upload limit - `astro.config.ts` `filter` now drops every `/{locale}/...` route so the sitemap only emits canonical English URLs. - Locale variants are still discoverable via the `<xhtml:link rel="alternate" hreflang="...">` annotations the `namespaces.xhtml: true` option emits inside each canonical entry. This is Google's recommended pattern for a multi-language site. - Verified: post-fix `out/sitemap-0.xml` = 179 KB (was 38.4 MiB on the prior attempt that forced #2603's revert). Fix 2 — header brand block restored to the polished version - Logo `width/height` 36 → 44 (matches PR #2588's brand-mark refresh for visual weight against the new black speech-bubble glyph) - `.brand-meta` block ("Studio Nº 01 · Berlin / Open / Earth") removed from the header bar; the same editorial flourish still lives on the rotated `.side-rail .rail-text` pseudo-elements at page edges. Fix 3 — header nav grouped into Library + standalone Tutorials/Blog - Skills / Systems / Templates / Craft are now children of a Library dropdown (matches PR #2588's grouping). Each row keeps its count badge inline; the trigger highlights when any of the four facet pages is active. - Tutorials and Blog stay as standalone top-row items (PR #2588's original decision after Joey's review on the Learn dropdown). - Contact removed from the header — it was a same-page anchor that the footer already surfaces. - Hardcoded "Library" / "Tutorials" labels match the brand-name pattern: unlocalized across all 18 landing-page locales. Fix 4 — HA SoftwareApplication entity canonicalized on the LP again - `alternateName` is back to an explicit array of real query variants `["html anything", "html-anything", "htmlanything", "HTML Anything Editor", "The agentic HTML editor"]`. #2469 re-routed it through `copy.schemaAlternateName` which dropped the literal alias declarations Google needs for spaced-vs- hyphenated-vs-joined matching. (Restores PR #2566.) - `url` flips back from `HA_URL` (the GitHub repo) to the LP URL itself, matching the `BreadcrumbList` block on the same page. GitHub repo lives in `sameAs` as a peer surface. (Restores PR #2586. Without this, Google credits the GitHub repo as canonical for the entity, which is the opposite of what this surface exists for.) Fix 5 — catalog-card horizontal padding unified at 24 px - featured-card 22 → 24, template-card 20 → 24, system-card 18 → 24, source-card 28 → 24. - For template-card, also moved horizontal padding into the group rule exclusively so future siblings join without re-asserting margin shorthands. (Restores PR #2600.) Fix 6 — `_redirects` for the locale-code rename - This bundle uses `zh` / `zh-tw` / `pt-br` / `es` (the codes Tom's i18n.ts ships). The previous OD landing-page used `zh-CN` / `zh-TW` / `pt-BR` / `es-ES`. Externally-indexed and inbound-linked URLs against the old prefixes now 301 to the new canonical. Validation - `pnpm --filter @open-design/landing-page typecheck` — 0 errors - `pnpm --filter @open-design/landing-page build` — completed successfully; 18,204 pages built; sitemap-0.xml is 179 KB (well under the 25 MiB Cloudflare Pages limit). * docs: promote 'open-source alternative to Claude Design' to README H1 Brings the missing README and .gitignore changes from #2469 that the first wholesale-checkout in this branch missed (the auto-pulled diff scope was filtered to apps/landing-page/ initially). What - Every README.*.md (13 locale variants) now leads with the "open-source alternative to Claude Design" tagline as a subtitle to the project name in the H1 / first paragraph. This was @pftom's brand-positioning commit (`ee851dc`) on the original #2469 branch. - `.gitignore` adds `growth/**` to keep growth-research scratch out of the repo. Why - The README is one of the highest-PageRank surfaces a GitHub project exposes to Google. Promoting the "alternative to Claude Design" framing into the H1/subtitle position makes the project surface for exactly the query the SEO work in this PR is trying to capture. - Without this commit, the replicated #2469 in this branch would still rank against the previous H1 ("Open Design") on GitHub crawls, letting the SEO win at the LP fall short on the GitHub surface. This is a strict subset of #2469's content — pure docs, no code, no behavior change beyond what GitHub renders on the repo overview. --------- Co-authored-by: Joey-nexu <joeylee12629@gmail.com>	2026-05-22 00:59:11 +08:00
Jane	eefaf4504a	Revert "Enhance landing page with SEO-focused content and FAQ section (#2469)" (#2603) ... This reverts commit 26ee030b4c. Co-authored-by: Joey-nexu <joeylee12629@gmail.com>	2026-05-22 00:23:37 +08:00
Tom Huang	26ee030b4c	Enhance landing page with SEO-focused content and FAQ section (#2469) ... * Enhance landing page with SEO-focused content and FAQ section - Updated `.gitignore` to include growth directory. - Modified `astro.config.ts` to prioritize high-intent landing pages for SEO. - Added new FAQ styles and layout in `globals.css` for better user experience. - Implemented FAQ section in `page.tsx`, ensuring it aligns with structured data requirements. - Created dedicated pages for agents and alternatives to Claude Design, enhancing SEO and user navigation. - Introduced comparison page for evaluating Open Design against competitors. - Added favicon links component for consistent branding across all pages. * Add SVG favicon and update favicon links for improved branding * Enhance landing page with official source pillars for improved branding and navigation - Added five canonical "official source" pillars to the homepage, reinforcing key links: official site, GitHub repository, releases, documentation, and Discord community. - Updated URLs for releases, issues, documentation, and license to streamline access and improve user experience. * Add locale support and enhance landing page with language switcher - Introduced locale management with a new i18n module, defining multiple languages for the landing page. - Implemented a locale switcher in the topbar and header, allowing users to select their preferred language. - Updated global styles for the locale selector and adjusted layout for better responsiveness. - Enhanced SEO by ensuring localized content is served based on user selection. - Added a script for automatic locale detection and persistence in local storage. * Implement localized routing and enhance navigation with href utility - Added `stripLocaleFromPath` and `localizedHref` functions to manage locale-based URL paths. - Updated `localePath` to normalize paths based on the detected locale. - Refactored links in the header, footer, and main page components to utilize the new `localizedHref` function for improved navigation. - Introduced locale-aware routing for new pages, ensuring consistent user experience across different languages. - Enhanced SEO with alternate links for localized content in the sub-page layout. * Update header component to use new logo format - Replaced favicon image with a new logo in WebP format for improved performance and quality. - Ensured consistent branding across the landing page with the updated logo. * Enhance landing page with localization and new UI components - Introduced a comprehensive localization schema for content management, allowing for multilingual support across various sections. - Updated the blog and collection schemas to include internationalization (i18n) fields for better content localization. - Implemented a new official source strip for improved navigation and branding, linking to key resources like the official site and documentation. - Enhanced the locale switcher functionality, allowing users to select their preferred language with improved UX. - Updated styles for the locale switcher and added new components for better responsiveness and accessibility. - Refactored existing components to utilize localized URLs, ensuring a consistent user experience across different languages. * Implement comprehensive localization and enhance landing page UI - Introduced new localization features, including `EXTRA_LOCALIZED_HOME_BODY_COPY` and `EXTRA_LOCALIZED_LANDING_UI_COPY`, to support multilingual content across the landing page. - Updated `astro.config.ts` to integrate internationalization (i18n) settings for the sitemap, improving SEO for localized content. - Created new files for home page and info page internationalization, defining structured content for various languages. - Enhanced the locale switcher functionality with improved UX, allowing users to easily select their preferred language. - Refactored existing components to utilize localized content and URLs, ensuring a consistent experience across different languages. - Made CSS adjustments for better responsiveness and accessibility in the UI components. * Enhance landing page with new design templates and localization improvements - Added support for design templates in the content management system, allowing for better organization and access to design resources. - Implemented comprehensive localization for blog topics, enhancing multilingual support across various sections of the landing page. - Updated the header component to include new product menu items, improving navigation and user experience. - Refactored CSS for improved responsiveness and accessibility, including a new sticky chrome bar for better navigation. - Enhanced the locale switcher functionality, ensuring a seamless experience for users selecting their preferred language. * docs(readme): promote 'open-source alternative to Claude Design' tagline to subtitle across locales	2026-05-21 23:40:58 +08:00
Eli-tangerine	8193981511	Keep PR 2400 changes without folder pickers (#2462) ... * feat(daemon): add project working directory management and editor hand-off functionality - Introduced new flags for project commands to manage working directories, including `--working-dir` and `--dir`. - Implemented API routes for listing available editors and opening projects in selected editors. - Added a hand-off button in the ChatPane header to facilitate opening project folders in local applications. - Enhanced the HomeHero component to include working directory and design system settings, improving user experience in project creation. - Created HomeHeroSettingsChips component for inline management of working directory and design system selection. * feat(chat): implement voice transcription proxy and enhance UI components - Added a new API route for voice transcription using OpenAI's `/audio/transcriptions` endpoint, allowing users to send audio blobs directly for transcription. - Integrated multer for handling audio file uploads in memory, ensuring efficient processing without disk storage. - Updated the HomeHero component to include example prompt suggestions for plugins, enhancing user interaction. - Introduced the EditorIcon component to visually represent different editors in the hand-off menu, improving the user experience. - Refined the HandoffButton component to utilize the new EditorIcon, providing a more cohesive interface for selecting editors. - Enhanced CSS styles for various components to improve layout and responsiveness, including adjustments to tab and button sizes for better usability. * style(workspace-shell): enhance layout and overflow handling - Updated CSS for .workspace-shell to ensure full viewport width and height, with proper overflow management. - Adjusted grid layout to prevent content overflow and maintain responsiveness. - Modified styles for .workspace-tabs-chrome to improve width handling and prevent overflow issues. * refactor(chat): remove voice transcription proxy and related components - Deleted the voice transcription proxy implementation, including the associated API route and multer configuration. - Removed the MicButton component from the ChatComposer and HomeHero components to streamline the UI. - Updated HomeHero to include example suggestions without the voice input functionality. - Adjusted CSS styles for various components to maintain layout consistency after the removal of the MicButton. * feat(daemon): implement minting of HMAC tokens for working directory management - Added a new function `mintImportTokenFromCurrentSecret` to generate HMAC tokens bound to a specified base directory, enhancing security for working directory operations. - Updated the `desktop-auth.ts` file to include the new token minting functionality, which returns structured errors when the desktop auth secret is cleared. - Introduced new IPC message types for minting import tokens in the sidecar protocol, allowing seamless integration with the daemon's working directory management. - Enhanced the `WorkingDirPill` component to utilize the new token minting flow for secure directory selection in desktop builds. - Updated CSS styles for the HomeHero component to accommodate new example suggestion features and maintain layout consistency. * fix(HomeView): import HOME_HERO_CHIPS constant for improved chip management - Updated the HomeView component to import the HOME_HERO_CHIPS constant from the chips module, enhancing the management of hero chips within the component. * feat(daemon): implement mintImportTokenViaSidecar for secure working directory management - Introduced the `mintImportTokenViaSidecar` function to facilitate the minting of HMAC tokens for desktop-import operations via the daemon's sidecar IPC. This allows CLI commands to bypass authentication when the desktop-auth gate is active. - Updated the CLI to utilize the new token minting function when setting the working directory, ensuring secure access to trust-gated API endpoints. - Enhanced the sidecar server to handle minting requests and return structured error messages for improved user feedback. - Added tests to validate the new token minting functionality and its integration with the working directory management process. - Refactored related components to support the new token flow, improving overall security and user experience. * feat(HomeHero): enhance UI components and styles for improved user experience - Updated HomeHero component to replace active dot indicators with Plug icons for better visual representation of active plugins. - Adjusted CSS styles for various elements, including padding and dimensions, to enhance layout consistency and responsiveness. - Introduced new styles for active type icons and improved hover effects for buttons. - Updated HomeHeroSettingsChips to change button titles and icons for clarity. - Added tests to ensure proper rendering and functionality of updated components. * feat(ProjectDesignSystemPicker): enhance design system selection with preview functionality - Updated the ProjectDesignSystemPicker component to include a preview feature for design systems, allowing users to see a preview of the selected design system. - Implemented hover functionality to update the preview based on the hovered design system. - Added fullscreen preview capability for a more immersive experience. - Enhanced CSS styles for the design system picker to improve layout and responsiveness. - Introduced tests to validate the new preview functionality and ensure proper interaction within the component. * feat: refactor project metadata handling and enhance design system picker - Updated the default scenario plugin ID retrieval to use project metadata, improving the logic for determining the appropriate plugin based on project intent. - Enhanced the ProjectDesignSystemPicker and related components to support localized design system summaries and categories, improving user experience. - Introduced new translations for working directory and design system picker components, ensuring better accessibility and usability across different locales. - Added a new 'live-artifact' project type to the HomeHero chips, expanding the functionality for users creating refreshable artifacts. - Updated tests to validate the new project metadata handling and design system picker functionalities. * feat: enhance localization and styling for design system components - Added French translations for working directory and design system picker components, improving accessibility for French-speaking users. - Updated CSS styles for the pet task item to ensure consistent padding and layout. - Introduced a new test suite for HomeHeroSettingsChips to validate localization and design system selection functionality. - Enhanced ProjectDesignSystemPicker tests to ensure proper localization and interaction with design system categories. * fix: update .gitignore to include all claude-sessions directories and remove specific session files - Modified .gitignore to ensure all claude-sessions directories are ignored by using a wildcard pattern. - Deleted two specific claude-sessions markdown files to clean up unnecessary session data. * fix: repair home automation ci regressions * fix: stabilize artifact consistency e2e * Remove folder picker changes from PR 2400 --------- Co-authored-by: pftom <1043269994@qq.com> Co-authored-by: qiongyu1999 <2694684348@qq.com>	2026-05-20 22:07:30 +08:00
lefarcen	5172e37217	Merge origin/main into release/v0.7.0 to prepare merge-back PR ... Resolves 7 conflicts via hybrid strategy: - apps/web/src/components/EntryView.tsx: take main (Discord+X pills are forward feature) - apps/web/src/components/Icon.tsx: take main (switch-case refactor) - apps/web/src/components/NewProjectPanel.tsx: take release (preserve #1514 dropdown UX validated in 0.7.0 acceptance) - apps/web/src/index.css: take main (project-target-platforms / instructions chip styles) - apps/web/tests/components/FileViewer.inspect-empty-hint.test.tsx: accept main's deletion - nix/package-daemon.nix, nix/package-web.nix: take main pnpmDepsHash Non-conflicting hunks from #1519 (AppChromeHeader), #1428 (PostHog analytics call sites), and #1540 (release light background) are preserved via auto-merge.	2026-05-13 18:19:47 +08:00
kami	4f76e836ae	feat(audio): add ElevenLabs audio support (#1384) ... * docs: add ElevenLabs audio support design * docs: add ElevenLabs audio implementation plan * feat(daemon): add ElevenLabs speech renderer * feat(daemon): add ElevenLabs sound effects renderer * fix(daemon): preserve ElevenLabs sfx durations * feat(web): expose ElevenLabs media providers * feat(daemon): document ElevenLabs audio contract * feat(audio): add ElevenLabs voice selection * chore: ignore superpowers scratch docs * fix(daemon): cache ElevenLabs voice options * fix(audio): expand ElevenLabs voice and SFX selection * fix(audio): align ElevenLabs SFX controls * fix(audio): tighten ElevenLabs SFX prompt budget * fix(audio): preflight ElevenLabs SFX prompt length * fix(audio): surface ElevenLabs lookup failures * fix(audio): sanitize ElevenLabs prompt errors	2026-05-13 15:53:41 +08:00
lefarcen	e1bc83a476	feat(analytics): PostHog product analytics (P0 events, consent-gated, packaged) (#1428) ... * feat(analytics): scaffold PostHog product-analytics integration - Add @open-design/contracts/analytics subpath with the 17 P0 event payload types, header constants, and code↔CSV enum mapping helpers. - Add apps/daemon/src/analytics.ts with env-gated posthog-node client, request-scoped analytics context reader, and artifact-id anonymizer. - Expose GET /api/analytics/config so the web bundle never embeds the PostHog key at build time; daemon owns POSTHOG_KEY / POSTHOG_HOST. - Add apps/web/src/analytics module (identity + lazy posthog-js client + React provider) and mount it under <I18nProvider> in app/layout. No event wiring yet — that lands in the next commit alongside trigger points (App.tsx, EntryView, NewProjectPanel, SettingsDialog, FileViewer, runs.ts). * feat(analytics): wire app_launch, home_view, home_click, project_create_result - App.tsx: fire app_launch once after first effect tick. handleCreateProject now emits project_create_result on both success and failure paths. - EntryView.tsx: home_view (page) gated on agents loading so has_available_cli isn't transiently false; home_view (asset_panel) fires per top-tab change with the right result_count. - NewProjectPanel.tsx: home_click create_button fires before delegating to the parent; a fresh request_id is generated here and threaded through onCreate so the matching project_create_result stitches via $insert_id. - contracts/analytics: tighten createTabToTracking and topTabToTracking for the worktree branch's renamed tabs (live-artifact, templates). * feat(analytics): wire settings_view + 3 settings_click events - settings_view fires on dialog mount and on every section switch, carrying the active section (mapped via settingsSectionToTracking for the 16-section worktree layout), execution_mode, and the selected CLI provider id when present. - settings_click execution_mode_tab: setMode now emits before/after values whenever the user toggles between Local CLI and BYOK. - settings_click cli_provider_card: agent card onClick reports cli_provider_id via agentIdToTracking (kiro → other). - settings_click byok_field: onFocus added to api_key, model select, and base_url inputs; provider_id widened to include google so the worktree's Gemini protocol slot type-checks. * feat(analytics): wire studio_view + studio_click chat, studio_view artifact - packages/contracts/src/analytics/artifact-id.ts: FNV-1a 64-bit helper produces a 16-hex anonymized id for (projectId, fileName). Stable cross-platform so the daemon and the web bundle resolve the same id without a Web Crypto round-trip; daemon now re-exports it. - ChatComposer: studio_view chat_panel fires once per project mount, studio_click chat_composer fires on attachment + send buttons with estimated user_query_tokens (length/4) and has_attachment. - FileViewer: studio_view artifact fires once per (project, file) at the dispatcher level, before any sub-viewer renders, with artifact_kind derived from the renderer registry / file.kind table. - Widen TrackingExportFormat to include markdown and cloudflare_pages so the worktree branch's full share menu can emit verbatim. * feat(analytics): wire studio_click share_option + artifact_export_result HtmlViewer's share menu now emits both events per click via a fireShareExport helper: - studio_click share_option fires immediately on click with the chosen export_format and a fresh request_id. - artifact_export_result fires when the export resolves — success for sync exporters (html, markdown, template) the moment the call returns, success/failed for async exporters (pdf, zip, deploy) via .then/.catch. The same request_id threads both events so PostHog stitches click → result via $insert_id. DEPLOY_PROVIDER_OPTIONS maps to the CSV's vercel / cloudflare_pages slots; markdown is now a first-class export_format value. Also ignore .env.local so local POSTHOG_KEY / .env-style secrets don't get committed. * feat(analytics): emit run_created and run_finished from the daemon POST /api/runs now reads the analytics context off the x-od-analytics-* headers the web client sets on every fetch, then: - Captures run_created with project_id, conversation_id, run_id, model_id, agent_provider_id (mapped via agentIdToTracking), skill_id, design_system_id, plus the token_count_source marker. - Schedules a run_finished capture on runs.wait(run) resolution, mapping succeeded/canceled/failed to success/cancelled/failed and reporting total_duration_ms. Both events use a stable insert_id derived from the same uuid so PostHog dedupes the daemon-side mirror against any future web-side capture without double-counting. Token sub-fields (user_query_tokens/system_prompt_tokens/...) stay omitted in v1 — the claude-stream parser only exposes input/output totals today. See tracking-doc-issues.md §3.2. * feat(analytics): emit settings_cli_test_result + settings_byok_test_result The original BLOCKING-list assumed these CSV P0 events were not implementable in this branch because main lacked Test buttons. The worktree HEAD actually wires `handleTestAgent` and `handleTestProvider` in SettingsDialog, so both events are now in scope. - handleTestAgent emits settings_cli_test_result on success and failure paths with cli_provider_id mapped via agentIdToTracking, result drawn from result.ok / catch branch, error_code from result.kind or the thrown error name, and duration_ms timed via performance.now(). - handleTestProvider emits settings_byok_test_result analogously, using apiProtocol (anthropic|openai|azure|ollama|google) directly as provider_id — wider than the CSV's 5-value enum, documented in tracking-doc-issues.md §2.5. Contracts: add SettingsCliTestResultProps / SettingsByokTestResultProps plus matching track* helpers. AnalyticsEventName union now covers all 14 P0 events this branch supports. * feat(analytics): gate PostHog on the existing telemetry.metrics consent The integration now reuses the same first-launch privacy banner + Settings → Privacy toggle that gates Langfuse, so a single user decision controls both telemetry sinks. - /api/analytics/config now consults the persisted AppConfigPrefs: it returns enabled=true only when POSTHOG_KEY is set AND the user has chosen "Share usage data" (telemetry.metrics === true). The response also echoes installationId so the web client uses the same anonymous id Langfuse keys off of — one identity per install, shared across both sinks. - Web AnalyticsProvider: - Bootstrap fetch resolves installationId and threads it through the x-od-analytics-anonymous-id header on every /api/* fetch, so daemon-side captures (run_created / run_finished / project_create_result) land on the same person record. - Exposes a setConsent(granted) method that calls posthog-js's opt_in_capturing / opt_out_capturing, wired from App.tsx via a useEffect watching config.telemetry?.metrics. Toggling Privacy → metrics now stops/resumes events immediately, no reload. - app_launch additionally gates on telemetry.metrics so a freshly- declined user fires nothing, and a freshly-opted-in user fires on the next reload. * feat(packaging): bake POSTHOG_KEY into packaged daemon spawn env Wires PostHog product analytics through the same Langfuse-style build- secret pipeline so official Open Design builds ship with the key while fork builds compile without it (the integration short-circuits cleanly when POSTHOG_KEY is absent). tools/pack - resolveToolPackConfig reads POSTHOG_KEY / POSTHOG_HOST from process.env at packaging time, validates them (no whitespace in the key, http(s) URL for host, trailing-slash strip), and stamps them on ToolPackConfig. Fork builds without the env vars simply omit the fields; the daemon-side gate keeps things off in that case. - Mac, Windows, and Linux packaged-config writers each append the two fields to open-design-config.json next to the existing telemetryRelayUrl entry. apps/packaged - RawPackagedConfig / PackagedConfig surface posthogKey / posthogHost so the Electron entry and headless entry both forward them to the daemon sidecar. - buildPackagedDaemonSpawnEnv emits POSTHOG_KEY / POSTHOG_HOST into the daemon child env when present. The daemon's existing analytics module reads these via process.env — no daemon-side changes needed. - The headless packaged path falls back to process.env for fields the builder hasn't injected, mirroring how OPEN_DESIGN_TELEMETRY_RELAY_URL is read there. CI - release-beta.yml and release-stable.yml expose POSTHOG_KEY (secret) and POSTHOG_HOST (var) at workflow-env scope so every packaging job inherits them. PR / fork builds without these set simply skip the bake step. Tests - tools/pack: config.test.ts covers bake-through, fork-build omission, whitespace rejection, invalid-URL rejection, and trailing-slash normalization. - apps/packaged: sidecars.test.ts covers buildPackagedDaemonSpawnEnv forwarding the keys when present and omitting them when null. * feat(analytics): enable PostHog autocapture + perf + exceptions Flip on the PostHog SDK's automatic diagnostic features so we capture click paths, page transitions, web vitals, dead clicks, and browser exceptions without scattering instrumentation through the codebase. Privacy defense lives in one place — apps/web/src/analytics/scrub.ts — wired in via posthog-js's `before_send` hook so every outgoing event passes through the same audit point: - $autocapture / $rageclick / $dead_click / $copy_autocapture: strips $el_text and value/placeholder/aria-label attrs from any input, textarea, password input, or contenteditable element. PostHog autocapture does not capture input.value by default, but $el_text on a <textarea> reflects the typed content — that's the prompt body for us, so it has to be scrubbed every time. - $pageview / $pageleave: drops query string and fragment from $current_url / $referrer so any future ?q=… can't leak. - $exception: rewrites file:// and absolute filesystem paths in stack frames to app://apps/<repo-relative> so we don't ship the user's home directory. - Suppresses $opt_in entirely — duplicate of our explicit setConsent toggle in App.tsx. Element-level defense in depth is limited to the single most sensitive surface: the chat composer textarea gets `ph-no-capture` so PostHog never even generates an event for clicks inside that subtree. Every other input relies on scrub.ts — sprinkling the class through every form would be noisy and easy to forget on new surfaces. The existing Privacy → "Share usage data" toggle continues to gate every new feature: posthog-js's opt_out_capturing() halts autocapture, $pageview, $exception, web vitals, and dead clicks alongside the explicit capture() calls — one global switch. 11 unit tests pin the scrub rules in apps/web/tests/analytics-scrub.test.ts. * ci(nix): bump pnpmDepsHash for posthog-js + posthog-node additions Adding posthog-js to apps/web and posthog-node to apps/daemon changed pnpm-lock.yaml, which Nix's fixed-output pnpmDeps derivation pins by sha256. The CI nix flake check failed with: specified: sha256-KF3Mld72/iau+pJmA7HvnanRx8VLtDP0N624SKrtrrc= got: sha256-PGFgX4lYyeH2TRAXfUq52A3EOa6bb1gO59hPsXhEk3s= Copy the new hash into both nix/package-web.nix and nix/package-daemon.nix per the procedure documented in nix/README.md §"First-build hash pinning". * feat(analytics): unify PostHog identity with Langfuse installationId PostHog's distinct_id is the installationId stamped by /api/analytics/ config; Langfuse already reads the same id off app-config.json to populate trace.userId. With both sinks keying off the same anonymous identity, dashboards can correlate user actions (PostHog events) with LLM runs (Langfuse traces) without re-identifying. Two gaps closed: 1. applyConsent(false) — clear posthog-js's persisted ph_*_posthog localStorage entry on opt-out via posthog.reset(). Without this, a user who opts out, then clicks Delete my data, then re-opts in would see PostHog stitch their new session to the deleted identity because bootstrap.distinctID only takes effect on first init. 2. applyIdentity(newInstallationId) — Delete my data rotates the installationId in app-config; App.tsx now watches config.installationId and calls posthog.reset() then identify(newId) so the next event batch is fully decoupled from the deleted one. Idempotent on same-id re-renders so benign config refreshes don't churn PostHog identities. The fetch wrapper's x-od-analytics-anonymous-id header also flips to the new id on rotation so daemon-side captures (run_created / run_finished) land on the same person record from the very next API call, not after a reload. The end-to-end rotation flow is verified against a live PostHog project; these unit tests pin the safety guards (no-client paths, null inputs) since stubbing posthog-js's init-loaded callback chain is brittle. * fix(langfuse): require both metrics AND content consent for trace reports Tightens the Langfuse gate so a user who shares anonymous metrics but NOT conversation content stops emitting Langfuse traces entirely — Langfuse is used for turn-quality evals which only make sense with prompt/output bodies. PostHog (product analytics, content-free) stays gated on `metrics` alone and is unaffected. i18n: "Conversation content" → "Conversation and tool content" with hints expanded to mention tool inputs/outputs so the consent surface matches what the trace actually carries (en + zh-CN). Bundled here per PR scope — change originated outside this PostHog PR but lands cleanly on the same files; gating Langfuse strictly on `content` makes the dual-sink consent model (PostHog = metrics, Langfuse = metrics + content) symmetric across both i18n locales and the daemon-side gate. * feat(analytics): wire byok_provider_option + fix PR review P1s Adds the BYOK protocol-chip click event (5-value provider_id mirroring the apiProtocol Settings UI) and resolves four P1 review threads on PR #1428. byok_provider_option: - New SettingsClickByokProviderOptionProps in contracts (provider_id = anthropic|openai|azure|google|ollama; maps to CSV's 5 values per tracking-doc-issues.md §2.5). - trackSettingsClickByokProviderOption helper in apps/web/src/analytics. - SettingsDialog hooks it on the protocol-chip onClick alongside the existing setApiProtocol call; is_selected reflects whether the chip was already active. Review fixes: 1. client.ts (Siri-Ray): clear `initPromise` when the resolution is null so a Privacy → metrics opt-in after a previous decline triggers a fresh /api/analytics/config fetch. Without this, the disabled response was cached forever — first-session opt-in needed a reload to start sending PostHog events. 2. provider.tsx (Siri-Ray): replace `url.includes('/api/')` with a strict same-origin + /api/ pathname check (shared `isSameOriginApiCall` helper). Outbound third-party URLs containing `/api/` (e.g. provider.example.com/api/x) no longer receive our x-od-analytics-* headers. 3. provider.tsx (codex-connector, lefarcen): gate header injection on `resolvedAnonId` being non-null. When Privacy → metrics is off, /api/analytics/config returns enabled=false → resolvedAnonId stays null → wrapper never installs → daemon can't read consent-bearing headers → no daemon-side PostHog event. setConsent now also clears resolvedAnonId on opt-out and re-fetches on opt-in. 4. daemon/analytics.ts (defense in depth): createAnalyticsService now takes dataDir and capture() re-reads app-config to check telemetry.metrics inside the fire-and-forget wrapper. Even if a stale header somehow reaches the daemon after opt-out, the capture is dropped before posthog-node.capture is called. * fix(web): place "Share usage data" on the right in privacy consent banner Swap button order in PrivacyConsentModal and the in-settings ConsentCard so the affirmative "Share usage data" lands on the right and "Not now" on the left. Matches the OK-on-the-right pattern users expect for primary actions. Both buttons keep equal visual prominence (same .privacy-consent-action styling) so the swap doesn't change the EDPB equal-prominence stance called out in the original Langfuse telemetry spec. * feat(analytics): populate run_finished token totals from claude-stream usage Daemon's claude-stream parser already emits agent usage events with input_tokens / output_tokens totals; the run service buffers them in run.events and Langfuse reads them out the same way. The run_finished PostHog event was leaving these fields empty. Scan run.events for the most recent agent usage frame on terminal transition and emit input_tokens / output_tokens / total_tokens when present. token_count_source flips to 'provider_usage' only when at least one count landed; runs without provider-side usage data keep 'unknown'. Provider does not break the input down into the 7 sub-fields the tracking doc lists (memory / context / attachment / system_prompt / …); those stay omitted until a parser change exposes them. * feat(analytics): estimate user_query_tokens from prompt length The user_query_tokens field for run_created / run_finished was hardcoded to 0. We can't tokenize without bundling a model-specific tokenizer, but the character/4 heuristic is the industry-standard estimate when one isn't available and is enough for funnel analysis (prompt-length cohorts, short-vs-long-query conversion rates). Extracted from req.body via the same telemetryPromptFromRunRequest pattern the daemon already uses for langfuse-bridge (currentPrompt then message fallback). Only the integer count goes to PostHog — the prompt text itself never leaves the daemon. token_count_source flips appropriately: - run_created with a prompt: 'estimated' (was 'unknown') - run_created with no prompt: 'unknown' - run_finished with provider usage: 'provider_usage' (overrides baseProps' 'estimated' value) - run_finished without provider usage: inherits 'estimated' or 'unknown' from baseProps so input/output absent doesn't mask the estimate.	2026-05-12 22:32:42 +08:00
Joey-nexu	5077a1cd38	feat(landing-page): split catalog into per-facet pages + auto-deploy on content changes (#1158) ... * feat(landing-page): split catalog into per-facet pages + auto-deploy on content changes Convert the single-page landing into a content-driven multi-page site sourced directly from the canonical Markdown bundles in the repo root, and close the deploy loop so contributor edits go live without manual follow-up. ## What's new - `/skills/`, `/systems/`, `/craft/`, `/templates/` index + detail pages, generated from `skills/<slug>/SKILL.md`, `design-systems/<slug>/DESIGN.md`, `craft/*.md`, and `templates/live-artifacts/<slug>/README.md` via Astro content collections (`app/content.config.ts`). No mirroring of content into the landing-page package — `glob` re-scans on every build. - Faceted sub-routes generated from frontmatter: - `/skills/mode/<slug>/` — 8 pages (deck, prototype, image, …) - `/skills/scenario/<slug>/` — 18 pages after alias collapse - `/systems/category/<slug>/` — 21 pages Each page owns its own `<title>`, meta description, and `CollectionPage` JSON-LD; chips on the parent index pages are now real anchors that link to these facet routes. - Updated top-bar nav (`_components/header.tsx`) to point at the new internal routes with live counts pulled from the catalog. Counts in the homepage hero meta description likewise driven by `getCatalogCounts()` so they never drift. - Per-skill / per-template thumbnails. A Playwright generator (`scripts/generate-previews.ts`) walks every `example.html` and `templates/live-artifacts/<slug>/index.html`, screenshots them at 1440×900@2x, and writes PNGs to `public/previews/`. The catalog data layer auto-detects presence and degrades gracefully when an artifact has no renderable HTML. ## Plumbing the auto-update loop - `landing-page-deploy.yml` and `landing-page-ci.yml` now trigger on changes under `skills/`, `design-systems/`, `craft/`, and `templates/`. Without this, a contributor adding a new SKILL.md to `main` would silently skip the deploy and the published site would fall behind. - Both workflows now install Playwright Chromium (cached by version) and run `pnpm previews` before `astro build`, so generated thumbnails ship in `out/previews/` automatically. Preview generation is `continue-on-error: true` — a single broken example.html should not block the deploy of the rest of the catalog. - `apps/landing-page/public/previews/` is gitignored: the directory is owned by CI and would otherwise add ~70MB of binary churn to the repo on every regeneration. ## Tag canonicalization - `app/_lib/catalog.ts` adds a small per-scope alias table so authoring drift like `od.scenario: operation` vs `operations`, or `live` vs `live-artifacts`, collapses to a single canonical route instead of leaking two near-empty pages. Mode and category alias tables are scaffolded but currently empty. ## Validation - `pnpm --filter @open-design/landing-page typecheck` — 0 errors, 0 warnings, 0 hints across 25 Astro files - `pnpm --filter @open-design/landing-page build` — 341 pages built (1 home + 8 mode + 18 scenario + 21 category + N detail pages + sitemap + RSS), zero external JS, ≥16 Cloudflare-resized hero image URLs intact ## Why this matters After merge, any push to `main` that adds, removes, or edits a skill, design system, craft principle, or live-artifact template automatically triggers a fresh build that: 1. picks up the new Markdown via the content-collection glob, 2. regenerates thumbnails for any matching example.html, 3. emits new sitemap entries and JSON-LD, 4. and ships to Cloudflare Pages — no landing-page-side change required. * fix(landing-page): address review feedback on PR #1158 Five fixes from the review pass — none change scope, all close the "contradictory totals" / "stale data" / "silent CI failure" gaps the reviewers flagged. ## Hero / catalog claims now read live counts everywhere `apps/landing-page/app/page.tsx` previously hardcoded `31` skills and `72` systems in the hero copy and stat rings, while the nav and meta description had already moved to `getCatalogCounts()`. After this PR every visible "X skills / Y systems" claim — hero lead, hero stat rings, capabilities cards body copy, labs section meta + filter pills, selected-work fractions, the labs CTA, and the footer Library — reads from a single `counts` prop. `Header` and `Page` now both require `counts` (no optional fallback) so a future caller can never silently publish stale numbers. The labs-section filter pills also stop being decorative buttons: they now link to the actual `/skills/mode/<slug>/` and `/skills/` catalog routes the new multi-page architecture exposes. ## Craft README no longer publishes `apps/landing-page/app/_lib/catalog.ts` filtered out `e.id !== 'README'`, but Astro normalizes `craft/README.md`'s id to lowercase `readme`, so the published site shipped `/craft/readme/` as a public craft principle and the nav badge counted 12 instead of 11. Compare case-insensitively (`e.id.toLowerCase() !== 'readme'`) so any future README casing is also filtered out. Verified locally: `apps/landing-page/out/craft/` now contains exactly 11 entries. ## Preview URL preserves actual file extension `listPreviews()` was already discovering `.png`, `.webp`, `.jpg`, and `.jpeg`, but `previewUrlFor()` always emitted `.png`, so a future sharp/webp post-processor (or a manually committed template asset) would mark the record as available while the rendered `<img src>` 404'd. Switched the structure from `Set<slug>` to `Map<slug, filename>` and emit the actual on-disk filename verbatim. ## Preview script: per-artifact soft, systemic hard Previously any single failed `example.html` capture exited the script non-zero, which forced both workflows to mark the entire preview step `continue-on-error: true`. That blanket tolerance also masked systemic generator failures — a chromium launch that never finds the browser binary would silently ship a deploy with zero thumbnails. `scripts/generate-previews.ts` now distinguishes: - per-artifact failures → logged and skipped, exit 0 (catalog degrades gracefully for those skills), - discoverJobs / chromium.launch / 100%-failure run → exit 1 (systemic, must fail the build). Both workflows drop their `continue-on-error: true` flags so a real problem actually surfaces. ## AGENTS.md reflects the multi-page architecture `apps/landing-page/AGENTS.md` previously declared the landing page single-route ("Not multi-page. There is exactly one route ('/')"). That guidance is now wrong — there are six top-level route groups (`/`, `/skills/`, `/systems/`, `/craft/`, `/templates/`, plus their facet variants). Updated to describe content-collection sourcing, the no-mirror rule, the auto-deploy workflow contract, and the "never hardcode catalog claims" boundary. ## Validation - `pnpm --filter @open-design/landing-page typecheck` — 0 errors, 0 warnings, 0 hints across 25 Astro files - `pnpm --filter @open-design/landing-page build` — 340 pages built (was 341 before the README filter; the README route is now correctly absent), live counts visible in the built `out/index.html`: `driven by 125 composable skills and 149 brand-grade design systems` - Verified `out/craft/` no longer contains `readme/` - Verified preview URLs resolve to the actual on-disk filename via the regenerated catalog index page * fix(landing-page): clean up live-artifact template name + summary parsing Address @mrcfps's follow-up review on `0715d8c`. The `shapeLiveArtifactTemplate()` parser was passing the README's H1 verbatim (literal backticks intact) and using the first non-empty post-H1 line as the summary, even when that line was the `> Category: **Live Artifacts**` editorial blockquote. Result: `/templates/live-otd-operations-brief/` was shipping a `<meta name="description" content=">">` and a card title with raw Markdown noise — a regression for both SEO snippets and the templates catalog at-a-glance scan. ## Two new shared helpers - `stripMarkdownInline()` — strip backticks, asterisks, and link wrappers so `# \`otd-operations-brief\` · live-artifact template` becomes `otd-operations-brief · live-artifact template` before any further trimming. - `extractFirstProseParagraph()` — walk the body after the H1 and skip blockquotes (`>`), list markers, table rows, fenced code, and HR rules. Stop at the first contiguous prose paragraph and pass it through `stripMarkdownInline()` so the result is human-readable. Both helpers live next to `titleizeSlug()` and are used by `shapeCraft()` and `shapeLiveArtifactTemplate()` so they share one implementation. ## Live-artifact title boilerplate trim Live-artifact READMEs commonly title themselves `# \`<slug>\` · live-artifact template`. After stripping the inline backticks the trailing `· live-artifact template` is redundant ("Templates" already groups them) and adds a wide noisy suffix on catalog cards. Removed it via a narrow regex tail-strip. ## Result on the existing fixture Verified locally for `templates/live-artifacts/otd-operations-brief/`: - before: `<title>\`otd-operations-brief\` · live-artifact template …</title>`, `<meta name="description" content=">">` - after: `<title>otd-operations-brief — Open Design template</title>`, `<meta name="description" content="A drop-in html_template_v1 live-artifact template for an editorial On-Time Delivery brief. It ships:">` Typecheck 0/0/0, build 340 pages. --------- Co-authored-by: Joey <joey@cursor.so> Co-authored-by: Joey-nexu <236967869+joeylee12629-star@users.noreply.github.com>	2026-05-12 19:24:50 +08:00
Chris Tam	c61ba320fd	feat(nix): Add official flake with home-manager and NixOS support (#402) ... * nix: add official flake with home-manager and nixos modules * Pin pnpm version * Format README.md * Populate PATH files to discover installed CLIs * Revert "Populate PATH files to discover installed CLIs" This reverts commit 18d88781a88b8781913cf5a8b680dfb38eabf7e4. * Fix missing sqlite issue * Fix system issue * Reapply "Populate PATH files to discover installed CLIs" This reverts commit d02ea994e6. * Handle different ports for web frontend * Provide documentation for getting pnpm hash * Enable nix flake checks for code changes * Set `OD_WEB_PORT` on daemon when declared * fix: Fix environmentFile for macOS targets * chore: Ignore nix and direnv related files * fix: Read version directly from `package.json` * feat: Make nix shell entry prettier * chore: Update pnpm hashes * chore: Bump `pnpm` hashes * docs: Add blurb about dev shell in `README.md` * Address review comments * Add support for `OD_WEB_ORIGINS` * Fix `isLocalSameOrigin` * Update pnpm checksums * docs: Update documentation on host origins * Move allowedOrigins mapping out of the webFrontend.enable guard * fix: Bump pnpm hashes * Remove changes to `daemon` with `main` changes `main` merged a feature that addressed our need for allowed origins. Since this feature branch no longer needs it, remove any remaining changes in `daemon` code so that this is a pure Nix change. * Update documentation around `OD_DAEMON_URL` * Rewrite option docs to match same-origin proxy contract The port, webFrontend, and webFrontend.port option descriptions still described OD_DAEMON_URL as the runtime contract for the SPA, but the SPA issues relative /api/*, /artifacts/*, /frames/* requests and there is no runtime daemon-URL injection. Rewrite the three blocks to describe what the caddy / custom proxy must actually do. * Document daemon-side requirements for custom-server proxy paths The bring-your-own-server path in section (3) and the same-origin contract in section (4) understated what the daemon needs: any proxy whose origin differs from the daemon's bind (including loopback split-port like 127.0.0.1:8080 while the daemon stays on :7457) is 403'd by the daemon's same-origin gate until told about that origin. Add a callout under section (3)'s table, expand section (4) with a decision table covering same-port, loopback split-port (OD_WEB_PORT or webFrontend.allowedOrigins), and non-loopback (webFrontend.allowedOrigins) cases, and rewrite the webFrontend.allowedOrigins option description to enumerate the cases where it's required and surface OD_WEB_PORT as an alternative for the loopback split-port case. --------- Co-authored-by: lefarcen <935902669@qq.com>	2026-05-09 23:50:16 +08:00
ferasbusiness666	1e8926271b	Harden security scan findings and upgrade dependencies (#806) ... * feat: add accent color control and launcher for Open Design * fix: remove launcher binary from PR * test: cover accent appearance edge cases * Harden security scan findings and upgrade deps * Address proxy security review * Pin jsdom for web test stability --------- Co-authored-by: ferasbusiness666 <ferasbusiness666@users.noreply.github.com> Co-authored-by: lefarcen <935902669@qq.com>	2026-05-08 19:46:34 +08:00
kami	2eae7da24b	feat: support Cloudflare Pages custom domains (#851) ... * Support Cloudflare Pages custom domains without hiding pages.dev fallback Keep the default Pages preview as the first public link while optional owned-zone binding provisions DNS and Pages custom-domain state in parallel. Constraint: Cloudflare deploys must use the existing direct-upload API path with no Wrangler dependency. Constraint: pages.dev must stay visible even while custom-domain verification is pending. Rejected: Vercel custom-domain support | outside requested Cloudflare-only scope. Rejected: overwriting arbitrary CNAME records | risks taking over user-managed DNS. Confidence: high Scope-risk: moderate Directive: Do not expose providerMetadata through public deploy contracts; keep custom-domain DNS ownership checks conservative. Tested: pnpm --dir apps/daemon exec vitest run -c vitest.config.ts tests/deploy.test.ts tests/deploy-routes.test.ts Tested: pnpm --filter @open-design/contracts build && pnpm --filter @open-design/contracts typecheck && pnpm --filter @open-design/contracts test Tested: pnpm --filter @open-design/web typecheck && pnpm --filter @open-design/web test -- providers/registry.test.ts components/FileViewer.test.tsx i18n/locales.test.ts Tested: pnpm i18n:check && pnpm guard && pnpm typecheck Tested: pnpm --filter @open-design/daemon build && pnpm --filter @open-design/web build && git diff --check Not-tested: real Cloudflare account/token/domain smoke test * Preserve Cloudflare fallback correctness under large accounts and races Constraint: Cloudflare Pages keeps pages.dev as the primary usable fallback while custom domains remain optional typed metadata. Rejected: Treating custom-domain DNS or binding failure as a top-level deployment failure | pages.dev can still be ready and usable. Confidence: high Scope-risk: moderate Directive: Keep custom-domain finality tied to Cloudflare Pages API active status plus URL reachability; do not expose providerMetadata. Tested: pnpm --dir apps/daemon exec vitest run -c vitest.config.ts tests/deploy.test.ts tests/deploy-routes.test.ts; pnpm --filter @open-design/web test -- components/FileViewer.test.tsx i18n/locales.test.ts providers/registry.test.ts; pnpm --filter @open-design/daemon typecheck; pnpm --filter @open-design/web typecheck; pnpm i18n:check; git diff --check; pnpm guard; pnpm typecheck; pnpm --filter @open-design/daemon build; pnpm --filter @open-design/web build Not-tested: Real Cloudflare token/account/zone smoke test. * Keep impeccable design notes local Constraint: .impeccable.md is local assistant/design context and should not be part of the PR diff. Rejected: Keeping the file tracked while adding it to .gitignore | tracked files are not ignored by Git. Confidence: high Scope-risk: narrow Directive: Keep .impeccable.md untracked and ignored; do not rely on it for required project documentation. Tested: git check-ignore -v .impeccable.md; git diff --check Not-tested: Full workspace tests not rerun for ignore-only metadata change.	2026-05-08 11:11:22 +08:00
Feroomon2010	576dfed9e1	feat: add accent color control and launcher for Open Design (#683) ... * feat: add accent color control and launcher for Open Design * fix: remove launcher binary from PR * test: cover accent appearance edge cases --------- Co-authored-by: ferasbusiness666 <ferasbusiness666@users.noreply.github.com>	2026-05-06 23:14:21 +08:00
PerishFire	f1cdb2844a	test(e2e): gate beta packaged runtime (#637) ... * test(e2e): gate beta mac packaged runtime * test(e2e): separate ui automation layout * test(e2e): move localized content coverage * chore(release): prepare packaged 0.4.1 beta validation * test(e2e): keep ui lane playwright-only * fix(web): keep chat recoverable after conversation load failure * fix(desktop): honor native mac quit	2026-05-06 17:44:29 +08:00
alburt	b4e69ac61b	fix(copilot): copilot prompt processing with correct command format (#466)	2026-05-05 00:28:42 +08:00
Tom Huang	da2b007a43	feat(daemon): add DeepSeek TUI as a code agent adapter (#439) ... * feat(daemon): add DeepSeek TUI as a code agent adapter Register `deepseek` (with `deepseek-tui` cargo-only fallback) in AGENT_DEFS via `deepseek exec --auto [--model X] <prompt>` and plain-text streaming. Ships `deepseek-v4-pro` / `deepseek-v4-flash` as fallback model hints; users can paste any other id (incl. NIM / Fireworks / SGLang routes) via the custom-model input. Web UI gets a DeepSeek-blue gradient icon, label/alias mapping, and docs/agent-adapters.md §5.9 documents the auth state, prompt-as-argv Windows size limit, and the upstream gap that prevents stdin delivery today (clap declares `prompt: String` as a required positional). Adds .deepseek/ to .gitignore alongside the other per-agent runtime data dirs so first-launch trust files don't leak into git. * fix(daemon): drop unsupported deepseek-tui fallback bin The `deepseek` dispatcher owns `exec` / `--auto`; `deepseek-tui` is the runtime companion it invokes. Listing `deepseek-tui` in fallbackBins advertised availability for a host that only had the TUI binary, but buildArgs still emitted `<resolved> exec --auto <prompt>` — which deepseek-tui itself doesn't accept, so the first /api/chat run would fail. Upstream documents both binaries as required (npm and cargo paths install them together), so the fallback didn't correspond to a supported install. Pin the absence in the agents test and update docs §5.9 + the adapter table to match. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * fix(daemon): pre-flight DeepSeek TUI prompts against argv byte budget DeepSeek's exec mode requires the prompt as a positional argv arg (no `-` stdin sentinel upstream), so a fully composed OD prompt — system text + history + skills + design-system content + the user message — can blow Windows' ~32 KB CreateProcess limit (or Linux MAX_ARG_STRLEN on extreme edges) and surface as a generic spawn failure instead of a DeepSeek-specific, user-actionable message. The adapter now declares `maxPromptArgBytes = 30_000` (leaves ~2.7 KB argv headroom for `exec --auto --model <id>` and Windows quoting), and the /api/chat spawn path checks the composed prompt against that budget before calling `spawn`. Oversized prompts fail fast with `AGENT_PROMPT_TOO_LARGE` and guidance to reduce skills/design context or pick an adapter with stdin support. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * test(daemon): pin DeepSeek argv-budget guard with regression tests The previous spawn-path guard inlined the byte-budget check in the chat handler, so the only safety net for the DeepSeek argv-only prompt-delivery shape was a static "the field exists" assertion — nothing actually exercised the AGENT_PROMPT_TOO_LARGE path or the short-prompt happy path. Extract the check into a pure `checkPromptArgvBudget(def, composed)` helper in agents.ts, call it from /api/chat before bin resolution (so the guard is order- independent and fires regardless of whether the adapter binary is on PATH in CI), and add a regression test that exercises both the oversized-prompt branch (over the conservative under-Windows- CreateProcess budget) and the short-prompt branch, plus a UTF-8 byte-vs-codepoint case and a stdin-adapter no-op case so the guard can't silently regress or leak onto adapters that ship the prompt over stdin. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * fix(daemon): pre-flight DeepSeek prompts against Windows .cmd-shim quoting The first-pass argv-byte guard only inspects the raw composed prompt, so on Windows an npm-installed `deepseek` resolves to a `.cmd` shim and the spawn path then wraps the call in `cmd.exe /d /s /c "<inner>"` with every embedded `"` doubled by `quoteWindowsCommandArg`. A quote-heavy prompt (code blocks, JSON-shaped skill seeds) under the 30,000-byte budget can therefore still expand past CreateProcess's 32_767-char `lpCommandLine` cap and surface as a generic spawn ENAMETOOLONG instead of the DeepSeek-named, actionable `AGENT_PROMPT_TOO_LARGE` the budget guard was meant to provide. Add a second pure helper `checkWindowsCmdShimCommandLineBudget(def, resolvedBin, args)` that mirrors the platform layer's per-arg quoting and recomputes the would-be command line length whenever the resolved binary is a `.cmd` / `.bat` shim, and call it from `/api/chat` after `buildArgs` / `resolveAgentBin` so the same SSE error fires before `spawn`. Pin the new path with a quote-heavy regression (prompt is under the byte budget but doubles past the kernel cap) plus no-op tests for non-`.cmd` resolutions, null bin, and stdin-only adapters so the guard can't drift back. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * fix(daemon): extend DeepSeek argv guard to direct .exe Windows installs The cmd-shim guard added in 9011361 early-returned for non-`.cmd` / `.bat` resolutions, so a Windows host that resolved `deepseek` directly to a `.exe` (cargo-installed CLI, hand-built release, anything outside the npm shim path) bypassed the post-`buildArgs` budget check entirely. Direct `.exe` spawns skip the `cmd.exe /d /s /c "<inner>"` wrap, but Node/libuv still composes a CreateProcess `lpCommandLine` by walking each argv element through `quote_cmd_arg` — every embedded `"` becomes `\"`, backslashes adjacent to a quote get doubled. A quote-heavy prompt (code blocks, JSON-shaped skill seeds) under the 30,000-byte `maxPromptArgBytes` budget can therefore still expand past the kernel's 32_767-char cap on those installs and surface as a generic spawn ENAMETOOLONG instead of the actionable `AGENT_PROMPT_TOO_LARGE` the guard was meant to provide. Add a sibling pure helper `checkWindowsDirectExeCommandLineBudget(def, resolvedBin, args)` that mirrors libuv's quoting math (empty -> `""`; no whitespace/quote -> pass-through; quote-only -> simple wrap; otherwise per-char escape with backslash-doubling around quotes and trailing backslashes) and recomputes the would-be command line length whenever the resolved binary is a non-shim Windows install. The two Windows guards are mutually exclusive: the cmd-shim guard owns `.bat` / `.cmd`, the direct-exe guard owns everything else, so a single oversized prompt never double-emits an SSE error. POSIX paths on POSIX hosts still skip both guards (no CreateProcess in play), and stdin-delivered adapters still skip the entire post-buildArgs path. Wire the new helper into `/api/chat` after the cmd-shim check, pin the path with a quote-heavy regression on a `C:\Program Files\DeepSeek\deepseek.exe` resolved bin (prompt under the byte budget but past the kernel cap once libuv-quoted), plus no-op tests for ordinary prompts, `.cmd`/`.bat` resolutions, POSIX paths, null/empty bin, and stdin-only adapters, plus a mutual-exclusivity assertion so the two guards' division of labour can't drift. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * fix(daemon): neutralize cmd.exe %var% expansion in DeepSeek argv Wrap each `%` in `"^%"` inside `quoteWindowsCommandArg` so cmd.exe's percent-expansion can't substitute env values into a `.cmd`-shim spawn when the DeepSeek argv carries a prompt mentioning `%DEEPSEEK_API_KEY%`. Mirror the change in the agents.ts helper used by the budget guard, add `AGENT_PROMPT_TOO_LARGE` to the contracts so typed SSE consumers recognize the existing daemon error code, and pin the literal-prompt contract with regression tests. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code)	2026-05-05 00:08:26 +08:00
Tom Huang	6c2a8ba09f	feat(editorial-collage): introduce Atelier Zero style landing page as… (#366) ... * feat(editorial-collage): introduce Atelier Zero style landing page assets and documentation - Added new design system for Atelier Zero, including a detailed `DESIGN.md` file. - Created an `editorial-collage` skill with associated assets for a magazine-grade landing page. - Included example HTML and image assets for various sections (hero, about, capabilities, etc.). - Updated README files to guide usage and customization of the new skill and design system. - Introduced a new image generation prompt pack for consistent visual style across the landing page. * fix(i18n): cover atelier-zero design system and editorial-collage skill in German content Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * fix(editorial-collage): align manifest with shipped assets and address PR review - Update image-manifest.json widths/heights/ratios to match the actual PNGs on disk: hero/about/cap/testimonial/cta = 1024x1024 (1:1), method-1..4 = 816x816 (1:1), lab-1..5 and work-1..2 = 768x1024 (3:4). Mirror the new dimensions in imagegen-prompts.md headings and in README.md. - Mark testimonial.png as rekey_on_brand_change so the manifest agrees with SKILL.md's "regenerate at minimum testimonial.png" guidance, and add work-1/work-2 to the rekey list in SKILL.md and README.md. - Add a Hero (I.) sec-rule and renumber every following section II..VIII in example.html so the eight sections walk sequentially I -> VIII and the page-of-008 counter starts at 001. - Delete editorial-artifact-system/ (16 duplicate PNGs + index.html + skills.md draft) — the canonical version is skills/editorial-collage/ and the duplicate had no consumer references. - DESIGN.md: spell out which dimensions of each magazine reference (Monocle/Apartamento/IDEA), document the rationale for single-accent vs multi-accent, and extend the anti-pattern list with AI-image-gen artifacts the system explicitly rejects. - SKILL.md: add italic_words validation guidance (trim, cap at 4, verb->noun rewrite, punctuation strip) and replace the broken-image fallback with an inline SVG placeholder sized to the slot's manifest aspect ratio. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * fix(daemon): serve skill example assets via stable API route Skill example HTML such as `skills/editorial-collage/example.html` references shipped images via `./assets/*.png`. The web app loads the example into a sandboxed iframe via `srcdoc`, where relative URLs resolve against `about:srcdoc` and the PNGs render as broken images in the Examples preview. Add a `GET /api/skills/:id/assets/*` route that serves files under the skill's `assets/` directory with path-traversal guards, and rewrite `src='./assets/<file>'` / `href='./assets/<file>'` in the example response to point at that route. The disk preview keeps working because the on-disk files are unchanged. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * feat(landing-page): add new static Next.js 16 site for Open Design marketing - Introduced a new landing page application using Next.js 16, featuring a static export setup. - Added essential files including `package.json`, `next.config.ts`, and TypeScript configuration. - Implemented global styles in `globals.css` to match the Atelier Zero design system. - Created a detailed `AGENTS.md` for module-level boundaries and purpose. - Included various image assets for the landing page, ensuring a visually cohesive experience. - Established a root layout and main page structure to support the marketing content. * style(landing-page): enhance topbar layout and improve responsiveness - Added nowrap styling to topbar elements to prevent text overflow. - Introduced media query to hide mid text in the topbar for screen widths between 1200px and 1280px. - Updated layout.tsx to suppress hydration warnings for better rendering consistency. - Removed redundant "Compiled by Open Design" text from the page component. * feat(landing-page): implement scroll-reveal animations for enhanced user experience - Added a new `RevealRoot` component to manage scroll-triggered reveal animations. - Updated `globals.css` with styles for elements using the `data-reveal` attribute, including opacity, translation, and scaling effects. - Modified `layout.tsx` to include the `RevealRoot` component for managing animations. - Enhanced `page.tsx` by adding `data-reveal` attributes to various elements for staggered reveal effects. - Implemented reduced motion support to ensure accessibility for users with motion sensitivity. * fix(landing-page): update import paths and enhance link styles - Changed the import path in `next-env.d.ts` to reference the correct routes type definition. - Enhanced `globals.css` with new styles for topbar links, work cards, and partner elements, improving hover effects and transitions. - Updated `page.tsx` to include canonical project URLs and made various links point to these URLs for better navigation and accessibility. * feat(landing-page): implement headroom-style sticky header with live GitHub star count - Introduced a new `Header` component to manage sticky navigation behavior on scroll, enhancing user experience. - Updated `globals.css` to style the sticky header, including transitions and visibility toggling based on scroll direction. - Modified `page.tsx` to replace the static header with the new `Header` component, which fetches and displays the live GitHub star count. - Ensured accessibility by providing a fallback for users who prefer reduced motion. * feat(landing-page): enhance editorial landing page with global ticker and new styles - Updated `next-env.d.ts` to reference the correct routes type definition for development. - Enhanced `globals.css` with new styles for the global ticker, including responsive design and improved overflow handling. - Introduced a new `WIRE_CITIES` and `WIRE_CONTRIBS` data structure in `page.tsx` to display a counter-scrolling marquee of cities and contributors. - Added a ghost button style for the navigation call-to-action in the header. - Updated various sections in `page.tsx` to integrate the new ticker and improve overall layout and accessibility. * refactor(landing-page): update paper texture overlay and remove multica-ai link - Enhanced comments in `globals.css` to clarify the purpose and behavior of the paper texture overlay. - Adjusted z-index of the overlay to ensure proper layering with other elements. - Removed the `multica-ai` partner link from `page.tsx` to streamline the partner section. * feat(landing-page): implement dynamic contributor marquee with GitHub integration - Added a new `Wire` component to display a counter-scrolling marquee of cities and contributors. - The contributor list is fetched live from the GitHub API, ensuring up-to-date information. - Updated `page.tsx` to integrate the `Wire` component, replacing the static contributor list with dynamic content. - Enhanced comments for clarity regarding the functionality and purpose of the global wire. * fix(i18n): add German display copy for editorial-collage-deck skill The Validate workspace test asserts that GERMAN_CONTENT_IDS.skills covers every curated skill on disk; the new editorial-collage-deck skill was missing from DE_SKILL_COPY, causing src/i18n/content.test.ts to fail. Generated-By: looper 0.4.0 (runner=fixer, agent=claude-code) * feat(landing-page): migrate marketing site to Astro * perf(landing-page): remove React client runtime * perf(landing-page): serve images from Cloudflare resizing * fix(pr): address landing page review feedback --------- Co-authored-by: mrcfps <mrc@powerformer.com>	2026-05-04 13:39:58 +08:00
PerishFire	c6d11018a0	Refresh desktop integration control plane (#123) ... * feat(dev): add desktop tools-dev control plane * refactor(sidecar): split Open Design contracts Move Open Design-specific sidecar protocol definitions into @open-design/contracts so sidecar and platform can remain descriptor-driven primitives. * refactor(daemon): organize package sources Keep daemon app code, tests, and sidecar entrypoints in separate package directories so each layer can be built and verified independently. * chore(repo): streamline maintenance entrypoints Centralize agent guidance by directory and reduce root command chains while preserving the existing build scope. * docs: translate agent guidance to English * fix(sidecar): tolerate stale IPC sockets Remove stale Unix socket files only after confirming no listener is active, so tools-dev can restart after unclean shutdowns.	2026-04-30 14:23:53 +08:00
nettee	56d08b8c5f	Add shared contracts and migrate project code to TypeScript (#118)	2026-04-30 13:01:15 +08:00
shangxinyu1	751c9de56d	Add UI e2e automation suite and reporting (#64) ... * test: add e2e ui automation suite * fix review feedback for ui e2e suite Resolved the FileWorkspace.tsx merge-marker issue and kept the intended combination of multiple, accept="image/*", and data-testid. Updated the e2e port handling so the test config no longer relies on a single hardcoded app port. It now resolves an available port first and passes the same port selection through the dev server and Playwright base URL. Since main has moved to the Next.js dev stack, this was also adapted from the old Vite-based flow to NEXT_PORT. Kept test:ui serialized so cleanup completes before Playwright starts. Updated reset-e2e-artifacts.mjs so cleanup failures are surfaced with a warning instead of being silently swallowed, except for the expected ENOENT case.	2026-04-29 23:31:17 +08:00
Tom Huang	4db0483721	chore: migrate frontend toolchain from Vite to Next.js 16 App Router (#66) ... * Refactor project name from "Open Claude Design" to "Open Design" - Updated project name in package.json, package-lock.json, and README files. - Changed CLI commands and references from "ocd" to "od". - Adjusted file structure references in documentation and code to reflect new naming conventions. - Enhanced .gitignore to include new runtime data files. - Updated metadata in LICENSE file to match new project name. * chore: migrate frontend toolchain from Vite to Next.js 16 App Router Replace the Vite SPA scaffold with Next.js 16 App Router while keeping the existing daemon as the API/SSE/sqlite backend. The whole client tree now mounts under a single optional catch-all route (app/[[...slug]]) loaded with ssr:false; static export emits one shell HTML the daemon serves as the SPA fallback for deep links. Dev uses next.config rewrites to proxy /api, /artifacts, /frames to the daemon, matching the previous Vite setup. Made-with: Cursor * fix: address Next migration review feedback * fix: serve static export in preview script --------- Co-authored-by: mrcfps <mrc@powerformer.com>	2026-04-29 21:33:21 +08:00
nettee	f24bb669a7	feat: Add Hermes and Kimi runtime adapters (#71)	2026-04-29 20:53:44 +08:00
PerishFire	3447af23f4	chore: add release beta workflow placeholder (#36)	2026-04-29 16:00:24 +08:00
Tom Huang	1c942e6cb7	Feat/support star us (#5) ... * Refactor project name from "Open Claude Design" to "Open Design" - Updated project name in package.json, package-lock.json, and README files. - Changed CLI commands and references from "ocd" to "od". - Adjusted file structure references in documentation and code to reflect new naming conventions. - Enhanced .gitignore to include new runtime data files. - Updated metadata in LICENSE file to match new project name. * Add contributing guidelines in English and Chinese - Introduced CONTRIBUTING.md and CONTRIBUTING.zh-CN.md to provide clear instructions for contributors. - Outlined contribution types, local setup instructions, and merging criteria for skills and design systems. - Enhanced README files to reference the new contributing guidelines. * Update README and documentation for deck framework directives - Clarified DECK_FRAMEWORK_DIRECTIVE description in both English and Chinese README files to specify conditions for deck kind without a skill seed. - Added detailed workflow instructions in deck-framework.ts to emphasize the importance of copying the framework before adding content. - Enhanced discovery.ts to reinforce the framework-first approach for deck projects. - Updated system.ts to ensure proper handling of deck projects with and without bound skills, preventing re-authorship of scaling and navigation logic. * Update README and documentation for deck framework directives - Clarified DECK_FRAMEWORK_DIRECTIVE description in both English and Chinese README files to specify conditions for deck kind without a skill seed. - Added detailed workflow instructions in deck-framework.ts to emphasize the importance of copying the framework before adding content. - Enhanced discovery.ts to reinforce the framework-first approach for deck projects. - Updated system.ts to ensure proper handling of deck projects with and without bound skills, preventing re-authorship of scaling and navigation logic. * Enhance README and add star promotion assets - Added a "Star us" section in both English and Chinese README files to encourage users to star the project on GitHub. - Included a new image asset for the star promotion. - Introduced a new HTML file for a dedicated star promotion page. - Updated .gitignore to exclude new cursor-related files.	2026-04-28 21:00:33 +08:00
Tom Huang	6f6bf31dd2	Refactor project name from "Open Claude Design" to "Open Design" (#1) ... * Refactor project name from "Open Claude Design" to "Open Design" - Updated project name in package.json, package-lock.json, and README files. - Changed CLI commands and references from "ocd" to "od". - Adjusted file structure references in documentation and code to reflect new naming conventions. - Enhanced .gitignore to include new runtime data files. - Updated metadata in LICENSE file to match new project name. * Add contributing guidelines in English and Chinese - Introduced CONTRIBUTING.md and CONTRIBUTING.zh-CN.md to provide clear instructions for contributors. - Outlined contribution types, local setup instructions, and merging criteria for skills and design systems. - Enhanced README files to reference the new contributing guidelines.	2026-04-28 16:03:35 +08:00
pftom	a98096a042	Add initial project structure with essential files ... - Created .gitignore to exclude build artifacts and dependencies. - Added index.html as the main entry point for the application. - Included LICENSE file with Apache 2.0 terms. - Initialized package.json and package-lock.json for project dependencies. - Added pnpm-lock.yaml for package management. - Created QUICKSTART.md for setup instructions. - Added README.md and README.zh-CN.md for project documentation in English and Chinese.	2026-04-28 12:25:59 +08:00