docs: add GitHub workflow guide for AI docs#252
Conversation
Adds a friendly Git/GitHub intro for FileMaker devs anchored to the shared user model they know, with light/dark themed diagrams via a new ThemedImage MDX component. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@proofkit/better-auth
@proofkit/cli
create-proofkit
@proofkit/fmdapi
@proofkit/fmodata
@proofkit/typegen
@proofkit/webviewer
commit: |
📝 WalkthroughWalkthroughThis PR adds a "GitHub Workflow" MDX guide and registers it in docs metadata; introduces a theme-aware ThemedImage component and registers it for MDX; adds typed env schema and generated env.d.ts, applies varlock Next integration and pnpm overrides; switches PostHog reads to typed ENV and adds download tracking; implements UI primitives (Button/Dialog/Select) and a dialog-driven download flow. ChangesGitHub Workflow Guide, ThemedImage, Env/Varlock, UI, and Analytics
🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs:
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
- replace direct download links with email capture - wire docs to varlock env loading - add shared dialog and select primitives
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
apps/docs/src/components/DownloadButton.tsx (1)
17-63: ⚡ Quick winUse const assertions on immutable config maps.
These objects are static lookup tables;
as const+satisfieswill preserve literal types and prevent accidental widening/mutation.♻️ Proposed type-tightening
-const platformOptions: Record<Platform, { label: string; icon: React.ReactNode }> = { +const platformOptions = { mac: { label: "Download for macOS", icon: <Download className="size-5" />, }, win: { label: "Download for Windows", icon: ( <svg aria-hidden="true" className="size-5" fill="none" viewBox="0 0 24 24"> <path d="M4 5.5h7v6H4zM13 5.5h7v6h-7zM4 13h7v5.5H4zM13 13h7v5.5h-7z" stroke="currentColor" strokeWidth="1.8" /> </svg> ), }, -}; +} as const satisfies Record<Platform, { label: string; icon: React.ReactNode }>; -const variantStyles: Record<DownloadButtonVariant, { primary: string; chevron: string }> = { +const variantStyles = { dark: { primary: "h-12 border border-white/15 bg-white/[0.06] px-6 text-white shadow-[inset_0_1px_0_rgba(255,255,255,0.08),0_0_36px_rgba(255,255,255,0.08)] backdrop-blur-md transition hover:border-white/25 hover:bg-white/[0.1]", chevron: "h-12 border border-white/15 border-l-0 bg-white/[0.06] px-3 text-white shadow-[inset_0_1px_0_rgba(255,255,255,0.08),0_0_36px_rgba(255,255,255,0.08)] backdrop-blur-md transition hover:border-white/25 hover:bg-white/[0.1]", }, light: { primary: "h-12 border border-gray-900 bg-gray-900 px-6 text-white shadow-lg transition hover:bg-gray-800 dark:border-white/15 dark:bg-white/[0.06] dark:shadow-[inset_0_1px_0_rgba(255,255,255,0.08),0_0_36px_rgba(255,255,255,0.08)] dark:hover:border-white/25 dark:hover:bg-white/[0.1]", chevron: "h-12 border border-gray-900 border-l-0 bg-gray-900 px-3 text-white shadow-lg transition hover:bg-gray-800 dark:border-white/15 dark:border-l-0 dark:bg-white/[0.06] dark:shadow-[inset_0_1px_0_rgba(255,255,255,0.08),0_0_36px_rgba(255,255,255,0.08)] dark:hover:border-white/25 dark:hover:bg-white/[0.1]", }, -}; +} as const satisfies Record<DownloadButtonVariant, { primary: string; chevron: string }>;As per coding guidelines, "Use const assertions (
as const) for immutable values and literal types".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/docs/src/components/DownloadButton.tsx` around lines 17 - 63, The platformOptions and variantStyles lookup objects should be made immutable and have tightened literal types: change their declarations to use const assertions and the satisfies operator (e.g., declare platformOptions as `const platformOptions = { ... } as const satisfies Record<Platform, { label: string; icon: React.ReactNode }>` and variantStyles as `const variantStyles = { ... } as const satisfies Record<DownloadButtonVariant, { primary: string; chevron: string }>`), which preserves literal strings, prevents widening/mutation, and still checks the shape against the existing Record types; no runtime behavior changes required.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/docs/.env.schema`:
- Line 8: Remove the concrete analytics token from the schema and replace the
hardcoded value for NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN with a placeholder or
empty value (e.g. NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN=) so the key remains defined
but no real secret is committed; ensure the real token is provided via
deployment environment or CI secrets and update any README/deployment docs to
instruct developers to set NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN in their
environment.
In `@apps/docs/src/components/ui/button.tsx`:
- Around line 31-33: Button currently destructures { className, variant, size,
...props } so the ButtonProps.color ends up in ...props and is passed to the DOM
instead of being used by buttonVariants; update the Button component to also
destructure color from props, pass color into buttonVariants (e.g.
buttonVariants({ variant, size, color, className })), and keep color out of the
remaining ...props so it is not rendered as a raw DOM attribute; reference the
Button function, ButtonProps, and buttonVariants (as SearchToggle already uses
color correctly) when making the change.
In `@apps/docs/src/lib/analytics.ts`:
- Around line 33-37: trackDownloadRequest currently sends raw email to PostHog
(posthog.identify) and as an event property (captureEvent) without consent;
change trackDownloadRequest to accept an explicit consent flag (or read a
consent getter) and only call posthog.identify when that consent is true, and
never include the email in captureEvent payload—send only non-PII like {
platform }; also update the caller (DownloadDialog.tsx) to pass the user’s
explicit analytics consent into trackDownloadRequest.
In `@package.json`:
- Line 59: The root-level overrides entry "@next/env":
"npm:`@varlock/nextjs-integration`" is too broad; remove this override from the
monorepo root package.json and instead add the override only to the
`@proofkit/docs` workspace package.json (or the docs workspace manifest) so only
the docs package uses the npm:`@varlock/nextjs-integration` replacement; update
the docs workspace's package.json overrides to include the "@next/env":
"npm:`@varlock/nextjs-integration`" mapping and run a fresh install to verify only
`@proofkit/docs` is affected.
---
Nitpick comments:
In `@apps/docs/src/components/DownloadButton.tsx`:
- Around line 17-63: The platformOptions and variantStyles lookup objects should
be made immutable and have tightened literal types: change their declarations to
use const assertions and the satisfies operator (e.g., declare platformOptions
as `const platformOptions = { ... } as const satisfies Record<Platform, { label:
string; icon: React.ReactNode }>` and variantStyles as `const variantStyles = {
... } as const satisfies Record<DownloadButtonVariant, { primary: string;
chevron: string }>`), which preserves literal strings, prevents
widening/mutation, and still checks the shape against the existing Record types;
no runtime behavior changes required.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: b7041659-a7c7-48ec-91ee-d7c9f4c21cb2
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (13)
apps/docs/.env.schemaapps/docs/env.d.tsapps/docs/next.config.tsapps/docs/package.jsonapps/docs/src/components/DownloadButton.tsxapps/docs/src/components/DownloadDialog.tsxapps/docs/src/components/ui/button.tsxapps/docs/src/components/ui/dialog.tsxapps/docs/src/components/ui/select.tsxapps/docs/src/instrumentation-client.tsapps/docs/src/lib/analytics.tsbiome.jsonpackage.json
✅ Files skipped from review due to trivial changes (2)
- apps/docs/src/components/DownloadDialog.tsx
- apps/docs/env.d.ts
| # --- | ||
|
|
||
| # type=string @required @public | ||
| NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN=phc_CRjEA3E6xegbZegA9ZjsCREfuuR8XdTJ72CkBeukd5hQ |
There was a problem hiding this comment.
Do not commit a live analytics token in the schema file.
Line 8 contains a concrete token value. Keep the key definition in source, but inject the actual value via deployment environment to avoid accidental exposure/misuse and cross-env coupling.
Suggested change
# type=string `@required` `@public`
-NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN=phc_CRjEA3E6xegbZegA9ZjsCREfuuR8XdTJ72CkBeukd5hQ
+NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN=📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN=phc_CRjEA3E6xegbZegA9ZjsCREfuuR8XdTJ72CkBeukd5hQ | |
| NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN= |
🧰 Tools
🪛 Betterleaks (1.1.2)
[high] 8-8: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
(generic-api-key)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/docs/.env.schema` at line 8, Remove the concrete analytics token from
the schema and replace the hardcoded value for NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN
with a placeholder or empty value (e.g. NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN=) so
the key remains defined but no real secret is committed; ensure the real token
is provided via deployment environment or CI secrets and update any
README/deployment docs to instruct developers to set
NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN in their environment.
| function Button({ className, variant, size, ...props }: React.ComponentProps<"button"> & ButtonProps) { | ||
| return <button className={cn(buttonVariants({ variant, size, className }))} {...props} />; | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify impact: locate Button call sites passing `color=`
rg -n --type=tsx '<Button[^>]*\bcolor\s*='Repository: proofsh/proofkit
Length of output: 1955
🏁 Script executed:
find . -name "button.tsx" -path "*/docs/*" 2>/dev/null | head -5Repository: proofsh/proofkit
Length of output: 101
🏁 Script executed:
cat -n ./apps/docs/src/components/ui/button.tsxRepository: proofsh/proofkit
Length of output: 1606
🏁 Script executed:
rg -n "Button[^>]*\bcolor\s*=" --type=tsx --type=jsxRepository: proofsh/proofkit
Length of output: 88
🏁 Script executed:
rg "Button.*color\s*=" -A 2 -B 2Repository: proofsh/proofkit
Length of output: 42
🏁 Script executed:
rg "<Button" -t ts -t js -A 1 -B 1 | head -50Repository: proofsh/proofkit
Length of output: 4012
🏁 Script executed:
rg "import.*Button" apps/docs -A 1 -B 1Repository: proofsh/proofkit
Length of output: 2524
🏁 Script executed:
rg "color=" apps/docs/src -A 2 -B 2 | head -80Repository: proofsh/proofkit
Length of output: 42
🏁 Script executed:
rg "Button" apps/docs/src/components -A 3 | grep -A 3 "Button"Repository: proofsh/proofkit
Length of output: 13594
🏁 Script executed:
cat -n ./apps/docs/src/components/search-toggle.tsxRepository: proofsh/proofkit
Length of output: 2570
color prop is exposed but never applied to variants.
ButtonProps exposes color as a variant option, but the Button component does not pass it to buttonVariants(...). The color prop becomes a raw DOM attribute instead of applying the intended styling. This is inconsistent with how SearchToggle correctly uses color directly with buttonVariants.
💡 Suggested fix
-function Button({ className, variant, size, ...props }: React.ComponentProps<"button"> & ButtonProps) {
- return <button className={cn(buttonVariants({ variant, size, className }))} {...props} />;
+function Button({ className, variant, size, color, ...props }: React.ComponentProps<"button"> & ButtonProps) {
+ return <button className={cn(buttonVariants({ variant, size, color, className }))} {...props} />;
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| function Button({ className, variant, size, ...props }: React.ComponentProps<"button"> & ButtonProps) { | |
| return <button className={cn(buttonVariants({ variant, size, className }))} {...props} />; | |
| } | |
| function Button({ className, variant, size, color, ...props }: React.ComponentProps<"button"> & ButtonProps) { | |
| return <button className={cn(buttonVariants({ variant, size, color, className }))} {...props} />; | |
| } |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/docs/src/components/ui/button.tsx` around lines 31 - 33, Button
currently destructures { className, variant, size, ...props } so the
ButtonProps.color ends up in ...props and is passed to the DOM instead of being
used by buttonVariants; update the Button component to also destructure color
from props, pass color into buttonVariants (e.g. buttonVariants({ variant, size,
color, className })), and keep color out of the remaining ...props so it is not
rendered as a raw DOM attribute; reference the Button function, ButtonProps, and
buttonVariants (as SearchToggle already uses color correctly) when making the
change.
| export function trackDownloadRequest(properties: { email: string; platform: string }) { | ||
| if (isPostHogEnabled) { | ||
| posthog.identify(properties.email); | ||
| } | ||
| captureEvent("proofkit_download_request", properties); |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Verify where trackDownloadRequest is called and whether consent is checked upstream.
rg -n -C3 --type=ts --type=tsx '\btrackDownloadRequest\s*\(' apps/docs/src
# Verify all places where raw email is sent to PostHog.
rg -n -C3 --type=ts --type=tsx 'posthog\.identify\s*\(|captureEvent\s*\(.*email|proofkit_download_request' apps/docs/srcRepository: proofsh/proofkit
Length of output: 88
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Search for trackDownloadRequest calls and usage (using ts for both ts and tsx files)
echo "=== Searching for trackDownloadRequest calls ==="
rg -n -C3 'trackDownloadRequest\s*\(' apps/docs/src -t ts
echo ""
echo "=== Searching for posthog.identify calls ==="
rg -n -C3 'posthog\.identify' apps/docs/src -t ts
echo ""
echo "=== Searching for captureEvent calls ==="
rg -n -C3 'captureEvent' apps/docs/src -t ts
echo ""
echo "=== Checking analytics.ts for full context ==="
cat -n apps/docs/src/lib/analytics.tsRepository: proofsh/proofkit
Length of output: 4944
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "=== Full DownloadDialog.tsx content ==="
cat -n apps/docs/src/components/DownloadDialog.tsx
echo ""
echo "=== Search for consent-related code ==="
rg -n -i 'consent' apps/docs/src -t ts
echo ""
echo "=== Search for analytics consent or user agreement ==="
rg -n -i 'agree|permission|opt.?in' apps/docs/src -t tsRepository: proofsh/proofkit
Length of output: 4452
Avoid sending raw email to analytics without explicit consent gating.
Lines 35 and 37 transmit email to PostHog in two ways—as user identity and as event property—without any consent check. This is a privacy and compliance risk. Add a consent gate and minimize the event payload to exclude PII:
- Check for analytics consent before identifying the user and capturing the event
- Send only non-PII data (e.g.,
platform) in the event properties
No consent mechanism exists in the codebase or call site (DownloadDialog.tsx). The email must be gated on explicit user consent before transmission.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/docs/src/lib/analytics.ts` around lines 33 - 37, trackDownloadRequest
currently sends raw email to PostHog (posthog.identify) and as an event property
(captureEvent) without consent; change trackDownloadRequest to accept an
explicit consent flag (or read a consent getter) and only call posthog.identify
when that consent is true, and never include the email in captureEvent
payload—send only non-PII like { platform }; also update the caller
(DownloadDialog.tsx) to pass the user’s explicit analytics consent into
trackDownloadRequest.
| }, | ||
| "pnpm": { | ||
| "overrides": { | ||
| "@next/env": "npm:@varlock/nextjs-integration", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Verify whether workspaces besides `@proofkit/docs` depend on next / `@next/env`.
fd -HI '^package\.json$' -E node_modules | while read -r file; do
jq -r --arg file "$file" '
.name as $name |
(.dependencies.next // .devDependencies.next // "") as $next |
(.dependencies["@next/env"] // .devDependencies["@next/env"] // "") as $nextEnv |
if ($next != "" or $nextEnv != "") then
"\($name)\t\($file)\tnext=\($next)\t@next/env=\($nextEnv)"
else empty end
' "$file"
doneRepository: proofsh/proofkit
Length of output: 509
Scope the @next/env override to docs instead of the whole monorepo.
Line 59 sets a root-level override that affects every workspace depending on Next.js, not just @proofkit/docs. The verification found 6 workspaces with Next.js dependencies (@proofkit/docs, @proofkit/cli, @proofkit/cli-old, plus multiple template packages), so this override creates an unnecessary broad blast radius.
Suggested change
"pnpm": {
"overrides": {
- "@next/env": "npm:`@varlock/nextjs-integration`",
+ "@proofkit/docs>@next/env": "npm:`@varlock/nextjs-integration`",
"shiki": "3.13.0",
"@shikijs/types": "3.13.0",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "@next/env": "npm:@varlock/nextjs-integration", | |
| "@proofkit/docs>@next/env": "npm:`@varlock/nextjs-integration`", |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 59, The root-level overrides entry "@next/env":
"npm:`@varlock/nextjs-integration`" is too broad; remove this override from the
monorepo root package.json and instead add the override only to the
`@proofkit/docs` workspace package.json (or the docs workspace manifest) so only
the docs package uses the npm:`@varlock/nextjs-integration` replacement; update
the docs workspace's package.json overrides to include the "@next/env":
"npm:`@varlock/nextjs-integration`" mapping and run a fresh install to verify only
`@proofkit/docs` is affected.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/docs/src/components/DownloadLink.tsx`:
- Around line 20-22: Currently platform is set asynchronously in useEffect via
setPlatform(detectPlatform()), which can be stale on immediate clicks; remove
the detectPlatform call from useEffect and instead call detectPlatform()
synchronously inside the button click handler (e.g., the onClick/handleOpen
function that opens the dialog), assign that result to a local variable and pass
it into state setters and into trackDownloadRequest so the platform used is the
freshly-detected value; update usages that relied on the platform state
(setPlatform, trackDownloadRequest) to use this detectedPlatform variable to
ensure the correct platform is recorded at click time.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f5a86fe3-281e-4c4a-8ba4-a3adfec5f48c
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (5)
apps/docs/content/docs/ai/install-and-connect.mdxapps/docs/content/docs/ai/updating-proofkit.mdxapps/docs/package.jsonapps/docs/src/components/DownloadLink.tsxapps/docs/src/mdx-components.tsx
✅ Files skipped from review due to trivial changes (2)
- apps/docs/content/docs/ai/install-and-connect.mdx
- apps/docs/content/docs/ai/updating-proofkit.mdx
| useEffect(() => { | ||
| setPlatform(detectPlatform()); | ||
| }, []); |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n apps/docs/src/components/DownloadLink.tsxRepository: proofsh/proofkit
Length of output: 1373
🏁 Script executed:
find . -name "DownloadDialog*" -type fRepository: proofsh/proofkit
Length of output: 106
🏁 Script executed:
cat -n apps/docs/src/components/DownloadDialog.tsxRepository: proofsh/proofkit
Length of output: 4371
Move platform detection to the click handler to ensure correct platform is captured.
The platform state initializes to "mac" and is updated asynchronously in a useEffect with an empty dependency array. A user who clicks the button immediately after first paint—before the effect runs—will open the dialog with the default platform value. When they submit the form, trackDownloadRequest will receive the wrong platform.
Moving detectPlatform() to the click handler ensures the correct platform is detected synchronously at the moment of user interaction.
Proposed fix
-import { useEffect, useState } from "react";
+import { useState } from "react";
@@
- useEffect(() => {
- setPlatform(detectPlatform());
- }, []);
@@
- onClick={() => setOpen(true)}
+ onClick={() => {
+ setPlatform(detectPlatform());
+ setOpen(true);
+ }}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| useEffect(() => { | |
| setPlatform(detectPlatform()); | |
| }, []); | |
| import { useState } from "react"; |
| useEffect(() => { | |
| setPlatform(detectPlatform()); | |
| }, []); | |
| onClick={() => { | |
| setPlatform(detectPlatform()); | |
| setOpen(true); | |
| }} |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/docs/src/components/DownloadLink.tsx` around lines 20 - 22, Currently
platform is set asynchronously in useEffect via setPlatform(detectPlatform()),
which can be stale on immediate clicks; remove the detectPlatform call from
useEffect and instead call detectPlatform() synchronously inside the button
click handler (e.g., the onClick/handleOpen function that opens the dialog),
assign that result to a local variable and pass it into state setters and into
trackDownloadRequest so the platform used is the freshly-detected value; update
usages that relied on the platform state (setPlatform, trackDownloadRequest) to
use this detectedPlatform variable to ensure the correct platform is recorded at
click time.
1 participant
Summary
/docs/ai/github-workflowaimed at FileMaker devs new to Git, anchored to the shared-user model they know.ThemedImageMDX component renders light/dark SVG variants via Tailwinddark:classes (no JS toggle, no hydration flicker).public/diagrams/: shared-user-model and github-flow.Test plan
pnpm run cipasses/docs/ai/github-workflowlocally; verify both diagrams render🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation
Analytics