Skip to content

docs: tighten welcome wording and casing#4

Merged
sebfried merged 1 commit into
mainfrom
style/welcome-casing
May 21, 2026
Merged

docs: tighten welcome wording and casing#4
sebfried merged 1 commit into
mainfrom
style/welcome-casing

Conversation

@sebfried

Copy link
Copy Markdown
Contributor

Summary

Two small wording adjustments to `start-here/welcome`:

  • Note callout reworded — names plan.ai/ui explicitly as the proof of concept this project evolves from, and splits the thought into two sentences.
  • Drop proper-noun casing on "Workbench" and "Plan.ai" in the lead "two surfaces" sentence and the V1 row, matching the lowercase plan.ai brand style.

Not propagated to other docs that still capitalize those terms — call it out as a follow-up sweep if wanted.

Version bump: starlight `0.0.20 → 0.0.21`.

Test plan

  • `pnpm check` clean
  • `pnpm build` clean
  • After CF deploy: welcome page note reads "next evolutionary step of the plan.ai/ui proof of concept. it is the same project…"
  • Lead sentence uses lowercase "workbench" and "plan.ai"

🤖 Generated with Claude Code

- Note callout reworded: explicitly names plan.ai/ui as the "proof
  of concept" this project evolves from, and splits the two thoughts
  into separate sentences.
- Lead "two surfaces" sentence and V1 row drop the proper-noun
  capitalization on "Workbench" and "Plan.ai" — treating workbench
  as a common noun and matching the lowercase plan.ai brand styling.

Same wording style not yet propagated to other docs that mention
"Workbench"/"Plan.ai" capitalized — flagged separately if a
docs-wide sweep is wanted.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@sebfried sebfried merged commit 80616c3 into main May 21, 2026
1 check passed
@sebfried sebfried deleted the style/welcome-casing branch May 21, 2026 01:16
sebfried added a commit that referenced this pull request May 28, 2026
… enum, RLS

Council + Codex round 2: finish remaining v1 findings (#4-#7, #9, #12).
Backend is deno-check + pnpm build green. The migration is NOT applied —
run `supabase start && supabase db reset` to verify, then `supabase db push`.

- #5 metadata validation: new _shared/frame-metadata.ts validates both ingress
  endpoints against ui.plan.ai/frame-metadata.v1 before insert. Removes the
  silent date coercion and the flat agent_slug/channel_slug reads (schema is
  nested agent.slug/channel.slug). Adds the missing idempotency_conflict code.
- #4 scopes: media:image gates frame-submissions, media:video gates
  media-uploads (hasApiScope). Migration grandfathers existing keys.
- #6 idempotency: scoped per endpoint (idempotency_scope column + unique
  (api_key_id, idempotency_scope, idempotency_key)); PNG fingerprint now
  includes the image bytes (sha256BytesHex).
- #7 media status: frame_media.status is the frame_media_status enum; functions
  write media_processing (not processing); spec/docs aligned.
- #9 RLS: revoke client UPDATE on frame_submissions/frames (no client write
  path; transitions go through service-role Edge Functions).
- #12 OpenAPI + schema + narrative docs: media-uploads creates the submission;
  frame-submissions is image-only; removed media_upload_id.
- Fix a latent images.ts type error caught by deno check.
- skills: supabase-setup (ingress invariants), workbench-app (no client UPDATE).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant