@@ -0,0 +1,82 @@
+import type { ComponentPropsWithoutRef } from 'react'
+import { cn } from '@sim/emcn'
+import Link from 'next/link'
+import { SITE_URL } from '@/lib/core/utils/urls'
+import { blockTypeToIconMap, INTEGRATIONS } from '@/lib/integrations'
+import { IntegrationIcon } from '@/app/(landing)/integrations/components/integration-icon'
+import { getProviderBySlug } from '@/app/(landing)/models/utils'
+
+interface ChangelogLinkProps extends ComponentPropsWithoutRef<'a'> {}
+
+const SITE_HOST = new URL(SITE_URL).hostname
+const SITE_APEX = SITE_HOST.replace(/^www\./, '')
+const INTEGRATIONS_BY_PATH = new Map(
+  INTEGRATIONS.map((integration) => [`/integrations/${integration.slug}`, integration])
+)
+const INTEGRATIONS_BY_DOCS = new Map(
+  INTEGRATIONS.map((integration) => [integration.docsUrl, integration])
+)
+
+/** Decorates catalog links with the same brand marks used on their destination pages. */
+export function ChangelogLink({ href, children, className, ...props }: ChangelogLinkProps) {
+  let url: URL | undefined
+  try {
+    if (href) url = new URL(href, SITE_URL)
+  } catch {}
+
+  const isSite = url?.hostname === SITE_HOST || url?.hostname === SITE_APEX
+  const isExternal = url && url.hostname !== SITE_APEX && !url.hostname.endsWith(`.${SITE_APEX}`)
+  const pathname = url?.pathname.replace(/\/$/, '')
+  const integration = isSite
+    ? INTEGRATIONS_BY_PATH.get(pathname ?? '')
+    : url && INTEGRATIONS_BY_DOCS.get(`${url.origin}${pathname}`)
+  const providerSlug = isSite ? pathname?.match(/^\/models\/([^/]+)(?:\/[^/]+)?$/)?.[1] : undefined
+  const ProviderIcon = providerSlug ? getProviderBySlug(providerSlug)?.icon : undefined
+  const isHeadingAnchor = className?.split(' ').includes('anchor')
+  const icon = !isHeadingAnchor && (integration || ProviderIcon)
+
+  const content = (
+    <>
+      {icon ? (
+        <span aria-hidden='true' className='flex size-4 shrink-0 items-center justify-center'>
+          {integration ? (
+            <IntegrationIcon
+              as='span'
+              name={integration.name}
+              bgColor={integration.bgColor}
+              Icon={blockTypeToIconMap[integration.type]}
+              className='size-4 rounded-sm'
+              iconClassName='size-3'
+              fallbackClassName='text-xs'
+            />
+          ) : ProviderIcon ? (
+            <ProviderIcon className='size-4' />
+          ) : null}
+        </span>
+      ) : null}
+      {icon ? <span className='min-w-0'>{children}</span> : children}
+    </>
+  )
+  const linkClassName = cn(
+    'text-inherit no-underline',
+    icon && 'inline-flex max-w-full items-center gap-1 align-baseline',
+    !isHeadingAnchor && !icon && 'font-medium',
+    !isHeadingAnchor && 'focus-visible:outline-2 focus-visible:outline-offset-4',
+    className
+  )
+
+  return href && isSite ? (
+    <Link {...props} href={href} prefetch={false} className={linkClassName}>
+      {content}
+    </Link>
+  ) : (
+    <a
+      {...props}
+      href={href}
+      {...(isExternal ? { target: '_blank', rel: 'noopener noreferrer' } : {})}
+      className={linkClassName}
+    >
+      {content}
+    </a>
+  )
+}
@@ -0,0 +1 @@
+export { ChangelogLink } from './changelog-link'
@@ -3,5 +3,6 @@ export { ChangelogArticle } from './changelog-article'
 export { ChangelogHeader } from './changelog-header'
 export { ChangelogImage } from './changelog-image'
 export { ChangelogLayout } from './changelog-layout'
+export { ChangelogLink } from './changelog-link'
 export { ChangelogList } from './changelog-list'
 export { ChangelogVideo } from './changelog-video'
@@ -1,5 +1,5 @@
 import type { ReactNode } from 'react'
-import { Avatar, AvatarFallback, AvatarImage } from '@sim/emcn'
+import { Avatar, AvatarFallback, AvatarImage, cn } from '@sim/emcn'
 import Image from 'next/image'
 import Link from 'next/link'
 import { FAQ } from '@/lib/content/faq'
@@ -140,7 +140,16 @@ export function ContentPostPage({
       <div className='mx-auto w-full max-w-[1728px] px-10 max-md:px-7 max-lg:px-8 max-xl:px-9'>
         <div className='border-[var(--border)] border-x'>
           <div className='mx-auto max-w-[900px] px-6 py-16' itemProp='articleBody'>
-            <div className='prose prose-lg max-w-none prose-blockquote:border-[var(--border-1)] prose-hr:border-[var(--border)] prose-headings:font-season prose-a:text-[var(--text-primary)] prose-blockquote:text-[var(--text-secondary)] prose-code:text-[var(--text-primary)] prose-headings:text-[var(--text-primary)] prose-li:text-[var(--text-body)] prose-p:text-[var(--text-body)] prose-strong:text-[var(--text-primary)] prose-headings:tracking-[-0.02em]'>
+            <div
+              className={cn(
+                'prose prose-lg max-w-none prose-headings:font-season prose-headings:tracking-[-0.02em]',
+                '[--tw-prose-body:var(--text-body)] [--tw-prose-headings:var(--text-primary)] [--tw-prose-lead:var(--text-body)]',
+                '[--tw-prose-bold:var(--text-primary)] [--tw-prose-bullets:var(--text-primary)] [--tw-prose-counters:var(--text-primary)] [--tw-prose-links:var(--text-primary)]',
+                '[--tw-prose-captions:var(--text-secondary)] [--tw-prose-hr:var(--border)] [--tw-prose-quote-borders:var(--border)] [--tw-prose-quotes:var(--text-secondary)]',
+                '[--tw-prose-code:var(--text-primary)] [--tw-prose-pre-bg:var(--surface-5)] [--tw-prose-pre-code:var(--text-primary)]',
+                '[--tw-prose-td-borders:var(--border)] [--tw-prose-th-borders:var(--border)]'
+              )}
+            >
               <Article />
               {post.faq && post.faq.length > 0 ? <FAQ items={post.faq} /> : null}
             </div>
 
@@ -0,0 +1,61 @@
+# Oracle Database, Checkr, and Shopify updates
+
+Edition: `2026-10-15`. This is the existing scheduled edition, expanded during human editorial review.
+
+Article: `../oracle-checkr-and-shopify/index.mdx`
+
+Canonical: https://www.sim.ai/changelog/oracle-checkr-and-shopify
+
+Publication: pending the normal site release and hosted verification. A staging deployment is not production publication.
+
+## Selection and release evidence
+
+The initial draft considered only an older candidate batch and focused on Oracle Database. This catch-up edition adds substantial integration changes that were missing from earlier posts, followed by two concrete Chat fixes from the latest release. It does not imply that every item shipped on the article's publication date.
+
+| Source | Verified release | Coverage |
+| --- | --- | --- |
+| [Oracle Database](https://github.com/simstudioai/sim/pull/7378) | [v0.9.17](https://github.com/simstudioai/sim/releases/tag/v0.9.17) | Queries, structured writes, schema inspection, reusable connections, encrypted transport, and access requirements. |
+| [Checkr](https://github.com/simstudioai/sim/pull/8824) | v0.9.17 | Candidates, invitations, reports, and report/invitation event triggers. |
+| [Shopify](https://github.com/simstudioai/sim/pull/8833) | v0.9.17 | Bulk product variants, fulfillment orders, shipment tracking, and refresh of expiring connections. |
+| [Ramp and Vanta](https://github.com/simstudioai/sim/pull/8802) | v0.9.17 | Saved client-credentials connections selected from blocks. |
+| [Chat recovery](https://github.com/simstudioai/sim/pull/9059) | [v0.9.23](https://github.com/simstudioai/sim/releases/tag/v0.9.23) | Recovery of interrupted runs after a server restart without reopening the chat. No exactly-once execution claim. |
+| [Chat panel resizing](https://github.com/simstudioai/sim/pull/9065) | v0.9.23 | Retains the selected width when focus changes during a resize. |
+
+Release membership comes from explicit PR references in the published release notes, not merge dates. Oracle and the integration notes belong to v0.9.17; the Chat section is explicitly v0.9.23. The combined edition uses its canonical URL as its RSS identity, without a single `release.url`.
+
+## Availability and factual review
+
+- The deployed public block catalog exposes Oracle Database, Checkr, Shopify, Ramp, and Vanta without preview gating. Their public integration pages and guides resolve successfully.
+- Oracle Database requires version 12.1 or later and network access from the Sim runtime. Self-hosted installations require Node.js 24. Connection and SQL details remain in the linked guide.
+- Checkr requires the user's API key. Ramp and Vanta require their client ID and secret. Existing Vanta workflows with inline credentials must create and select a saved credential before running again; the article links the setup guide. The copy makes no claims about provider execution, connection success, or account permissions established by the image.
+- The latest release's Project-file work and workflow tests remain gated or foundational; they are excluded. OCI, Fusion, and EPM infrastructure has no corresponding public integration block to announce here.
+- Routine dependency work, internal refactors, and the original narrow workflow-lint note remain in technical release history.
+
+## Media provenance
+
+- Asset: `/changelog/oracle-operations-v1.jpg`, a 496 × 226 JPEG.
+- Captured October 15, 2026 from the actual Oracle Database block in a disposable local demo workspace, running this branch on the current staging base.
+- Opened the real Operation dropdown and widened the editor panel before capture. The complete rounded menu shows search and all six operations. The optimized crop excludes the editor's outer edge and unrelated workspace content.
+- No generated UI, fake credentials, edited labels, or fabricated query results. This capture demonstrates available operations; it is not an execution demonstration. Provider-account execution was not part of this capture.
+- The article retains the shared 12px radius, width limit, and existing image lightbox. One focused image serves the edition; supporting notes do not need separate media.
+- Full capture and review evidence are retained privately. Do not publish environment identifiers or logs.
+
+## Editorial and delivery checklist
+
+- [x] Concise lead plus five useful one-sentence notes within the body word budget.
+- [x] Each supporting change traced to its actual release; no repeated coverage from earlier articles.
+- [x] Public integration catalogs and contextual Oracle setup guide verified.
+- [x] Authentic media captured with complete menu edges; access restrictions retained.
+- [x] Desktop and 390px mobile review, including dark-theme icons and image-viewer zoom, dismissal, and focus return.
+- [x] Generated artifacts, lint, type-check, 60 audits, block-registry checks, and HTTP discovery checks pass locally. Repository test suites run in CI.
+- [ ] Both current-head PR reviews and final CI checks complete.
+- [ ] Staging article, media, discovery feeds, and links verified after deployment.
+- [ ] Production article and media verified before publication records or distribution advance.
+
+## Announcement drafts
+
+**Social:** Oracle Database and Checkr join Sim's integrations. Shopify adds bulk variant and fulfillment actions, while Ramp and Vanta connections can be reused across workflows. This changelog also covers the latest Chat recovery and resizing fixes.
+
+**Email:** Query and update Oracle Database from your agents, run Checkr background-check workflows, and manage more Shopify operations. Saved Ramp and Vanta connections reduce repeated setup. Read the changelog for requirements and the latest Chat fixes.
+
+These are drafts for the final canonical article. Distribution follows production verification.
@@ -15,10 +15,10 @@ Keep existing article URLs, original dates, and RSS identities when refining his
 - Headline: name the capability or action, at most 65 characters. Avoid generic headlines such as “A better experience.”
 - Summary: 15–40 words for search, sharing, and RSS, naming Sim and explaining the capability in plain language. It must make sense without the image.
 - Body: say what changed and explain the behavior a reader needs to understand it. There is no target length or minimum; keep the body under 250 words. Do not expand a short announcement with generic use cases, repeated benefits, or a setup tutorial. Name specific capabilities or controls only when they add information.
-- Release coverage: inspect the technical release for other meaningful user-facing changes. Include up to three concise notes under “Also in vX.Y.Z” when source evidence establishes that they belong to the same release. Group them sensibly, avoid repeating notes across articles from that release, and link to the relevant guide or product page. A focused feature announcement can remain short. Do not infer release membership from merge timing or add unrelated changes just to make an entry longer.
+- Release coverage: inspect the technical release for other meaningful user-facing changes. Include up to three concise notes under “Also in vX.Y.Z” when source evidence establishes that they belong to the same release. Group them sensibly, avoid repeating notes across articles from that release, and link to the relevant guide or product page. A manually curated catch-up edition can cover multiple releases when each section names its verified version; allow up to five notes total within the same word budget. A focused feature announcement can remain short. Do not infer release membership from merge timing or add unrelated changes just to make an entry longer.
 - Detail: every sentence must contribute a product change, useful behavioral detail, or necessary access information. Examples are optional and earn their place only when they make an unfamiliar change easier to understand. Leave full setup instructions and model inventories to the linked docs and catalogs. Never invent customer results or benchmarks.
 - Media: place the reviewed image or video immediately after the article header. Both use the shared lightbox; videos show a plain poster with playback, seeking, and zoom controls inside the viewer. Use concise alt text or an accessible action label without a visible video description. Do not add captions or prose about how the capture was made, whether a query ran, sample credentials, or what a screenshot does not prove. Keep capture provenance and review evidence in production.md.
-- Supporting notes: one sentence per change, up to three per article. Omit empty sections and technical maintenance with no meaningful user impact. Keep each note’s source and release evidence in production.md. The lead image need not illustrate every supporting note.
+- Supporting notes: one sentence per change, up to three for a focused announcement or five for a manually reviewed catch-up edition. Omit empty sections and technical maintenance with no meaningful user impact. Keep each note’s source and release evidence in production.md. The lead image need not illustrate every supporting note.
 - Links: one descriptive setup/documentation link, plus an integration, model, or product link when directly relevant. Use the actual catalog slug and guide. Put links in context; avoid a wall of generic “Learn more” links.
 - Availability: keep restrictions that affect whether someone can use the feature, such as a required plan or administrator role, in one concise sentence. Link to documentation for setup details. Keep unverified rollout questions, source analysis, capture instructions, and approval checkboxes in production.md. Never substitute a capture disclaimer for verifying a claim.
 
@@ -38,7 +38,7 @@ Every production brief records:
 
 Use the same clean demo workspace and product theme. Frame the relevant panel with enough context to locate it, and make the result legible at a 390px viewport. Hide unrelated private sidebar content before recording. Keep UI text and controls intact; never generate a different product state to improve a screenshot. Prefer recording at the intended framing over aggressive crops later.
 
-Complete sign-in and credential setup before capturing. Never save a placeholder key and present it as a working connection, or treat a saved key as evidence that the provider accepted it. A model-picker image can show model selection without a connected account; a demonstration of execution must use a working credential and a real result. Keep these production checks out of public copy.
+Complete sign-in and credential setup before capturing. Never save a placeholder key and present it as a working connection, or treat a saved key as evidence that the provider accepted it. A model picker or operation menu can show available choices without a connected account; a demonstration of execution must use a working credential and a real result. Keep these production checks out of public copy.
 
 Begin with the task ready to perform, show the action, and hold on its result. Avoid decorative intros, music, title cards, and excessive cursor movement. Keep the headline and important explanation in HTML. Record videos assembled from still screenshots as edited walkthroughs in the production brief; do not describe them as continuous recordings in public copy.
 
 
@@ -52,7 +52,7 @@ The GitHub tool supports pagination parameters, but the current visual List pull
 
 Use the API block for the final `POST /repos/{owner}/{repo}/pulls` with fixed repository, head/base branches, and boolean `draft: true`. The visual Create as Draft dropdown stores string values, while the GitHub endpoint expects a boolean; the explicit JSON request avoids depending on implicit coercion. Verify the returned head, base, and draft fields during acceptance.
 
-Set finite page, payload, and model-input budgets. For example, stop a scan after 20 GitHub pages and stop a model batch after 20 candidate summaries. Fetch relevant file excerpts only for shortlisted candidates, rather than sending every patch to a model. Treat reaching a cap as an incomplete scan: preserve saved candidates, keep the last completed boundary, and surface a catch-up action. Split an oversized interval or deliberately raise the reviewed budget; do not repeat an impossible capped scan forever or silently advance past it.
+Set finite page, payload, and model-input budgets. For example, stop a scan after 20 GitHub pages and stop a model batch after 20 candidate summaries. For editorial review, combine the ten newest eligible candidates with the ten oldest eligible backlog candidates and deduplicate by row identity before requesting evidence. This keeps recent releases visible while older unreviewed features continue moving through review. The resulting batch stays at or below twenty. Fetch relevant file excerpts only for shortlisted candidates, rather than sending every patch to a model. Treat reaching a cap as an incomplete scan: preserve saved candidates, keep the last completed boundary, and surface a catch-up action. Split an oversized interval or deliberately raise the reviewed budget; do not repeat an impossible capped scan forever or silently advance past it.
 
 ## Drafting contract
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+export { ChangelogLink } from './changelog-link'`