Skip to content

fix(site): enforce Sierra editorial formatting - #3

Merged
sierracatalina merged 1 commit into
mainfrom
codex/sitewide-editorial-formatting
Aug 25, 2026
Merged

sierracatalina merged 1 commit into
mainfrom
codex/sitewide-editorial-formatting

Conversation

@sierracatalina

Copy link
Copy Markdown
Owner

summary

  • apply Sierra's lowercase editorial system across all seven public Context Layer routes
  • preserve proper names, acronyms, technical tokens and code casing
  • centralize runtime/editorial formatting and add durable verification
  • remove agent-facing presentation notes from public copy

verification

  • formatter check: 7 pages
  • editorial verifier: pass
  • test suite: 83/83
  • lint: pass
  • Vercel preview: all seven routes render with Cormorant display, Lora body and DM Mono interface text; no horizontal overflow at 1280x720; no console errors

release order

Merge after sierracatalina/ship-goblin adopts canonical before-files routing, so HTML and assets switch together.

@vercel

vercel Bot commented Aug 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
context-layer-public Ready Ready Preview Aug 25, 2026 8:30pm

@sierracatalina
sierracatalina marked this pull request as ready for review August 25, 2026 20:50
@sierracatalina
sierracatalina merged commit 08cc9e4 into main Aug 25, 2026
5 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 57bba0ab0b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

<a href="/context-layer/implementation/valid-memory-update-proposal.json" download><strong>valid proposal fixture</strong><span>valid-memory-update-proposal.json ↓</span></a>
<a href="/context-layer/implementation/invalid-memory-update-proposal.json" download><strong>invalid proposal fixture</strong><span>invalid-memory-update-proposal.json ↓</span></a>
<a href="/context-layer/implementation/invalid-secret-receipt.json" download><strong>invalid receipt fixture</strong><span>invalid-secret-receipt.json ↓</span></a>
<a href="/context-layer/implementation/context-request.schema.json" download><strong>context request schema</strong><span>context-request.schema.JSON ↓</span></a>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the lowercase download filename extensions

Keep the displayed filename byte-for-byte consistent with the linked artifact. The formatter has changed .json to .JSON here and for every subsequent JSON download, while each href and actual repository filename still uses lowercase .json; on case-sensitive systems, users who copy the displayed filename into commands or paths will reference a nonexistent file. The formatter should protect filename-like technical identifiers rather than canonicalizing their extensions.

Useful? React with 👍 / 👎.

This branch was successfully deployed

1 active deployment
Preview — 57bba0ab Deployed Aug 25, 2026 by vercel[bot]
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