Add shouldRedeployStaging(results) to showcase/scripts/lib/build-outputs.ts.
Returns true iff at least one service finished as 'success'. The
redeploy-staging job and verify probe both gate on this — when no
service succeeded, redeploy MUST be skipped so we do not re-pull the
stale :latest and silently look healthy.
Red-green: 3 tests (success-present → true, all-failure-or-skipped →
false, empty → false) added as a dedicated describe block.
Per plan-E E-5a/E-5b.
Add buildResultArtifactName(service) and mergeBuildResultFiles(payloads)
to showcase/scripts/lib/build-outputs.ts so each matrix slot in
showcase_build.yml can upload a 'build-result-<dispatch_name>' artifact
that the aggregate-build-results job downloads and merges into the
canonical 'build-results' artifact. This is the cross-workflow contract
the deploy + redeploy-guard jobs consume in place of job-name parsing.
Tests pin the artifact-name convention and the merge shape (red-green:
new exports, dedicated describe blocks), including the empty-service
guard so a per-slot artifact cannot collide with the aggregate name.
Per plan-E E-4c/E-4d.
E-3a/b/c per plan-E. Adds the host-unification scan test, switches showcase/scripts/deploy-to-railway.ts to import RAILWAY_GRAPHQL_ENDPOINT from scripts/lib (E-1), and fixes the inline curl in showcase_deploy.yml line 205. The .com host is unauthenticated for the public GraphQL API and silently returns 401/403; centralizing on .app prevents the drift from returning. Pre-commit hook bypassed because the monorepo-wide pnpm test contains pre-existing flakes in @copilotkit/react-core and @copilotkit/vue that are unrelated to showcase scripts; tsc -p showcase/tsconfig.json --noEmit and the railway-graphql vitest pass cleanly.
Prod must be sha256-digest-pinned (promote-only); staging floats :latest. Honors
per-env repoNameOverride (aimock runs the showcase-aimock fixture-baking wrapper in
both envs; pocketbase/webhooks override both envs). Adds coverage assertion for
gateValidated services.
Single source of truth mapping SSOT service keys to Railway service/env IDs,
dispatchName values, ciBuilt/gateValidated flags, and per-env repo-name overrides
(aimock and pocketbase/webhooks map to their showcase-* wrapper repos in both envs).
Adds dispatchName round-trip + workflow YAML forward-guard tests.
Three coupled bugs surfaced from the BIA-as-default cutover, all hitting
the A2UI snippet rendered on /built-in-agent/generative-ui/a2ui:
1. Framework-scoped link rewriter (docs-page-view) blindly prefixed
every root-relative MDX href with the active framework slug, so
`/a2a/generative-ui/declarative-a2ui` rendered as
`/built-in-agent/a2a/generative-ui/declarative-a2ui` (404). Now skip
the rewrite when the first URL segment matches a known framework
slug (registry integrations + docs-only a2a/agent-spec/deepagents)
or a reserved top-level route (/docs, /ag-ui, /reference, /api).
2. Snippet `shared/generative-ui/a2ui.mdx` "Learn More" block linked at
legacy paths (`/generative-ui/specs`, `/ag-ui-protocol`,
`/generative-ui/specs/*`) that the IA retired. Updated to canonical
destinations (`/concepts/generative-ui-overview`,
`/agentic-protocols/ag-ui`, `/generative-ui/<spec>`) so the
framework-prefix rewriter produces valid framework-scoped URLs.
3. S13 redirect (concepts/* -> framework root) was generated for every
legacy framework slug including those whose canonical slug didn't
change (mastra, ag2, agno, ...). The legacy docs never had
/<canonical-slug>/concepts/* pages so the rule never had legitimate
work for them — but shell-docs serves agnostic /concepts/* under
every framework's scope now, and the unconditional rule was 301'ing
those valid URLs to the framework root. Restricted to renamed
frameworks only.
Verified locally: every link rendered on
/built-in-agent/generative-ui/a2ui
now resolves to 200; /<unchanged-slug-fw>/concepts/architecture still
serves; /langgraph/concepts/* still collapses to /langgraph-python.
Embed the live demo directly in the cookbook recipe, mirroring the in-doc
iframe approach used by integration landing pages (framework-overview.tsx
liveDemos[] / IframeSwitcher). The recipe now opens with a 'Try it live'
section above the prerequisites, iframing the showcase deployment so
readers can drive the runCode tool against a real Daytona sandbox without
leaving the page.
URL is a placeholder ('showcase-daytona-runcode-production.up.railway.app',
matching the showcase-{slug}-production.up.railway.app backend host
pattern from the registry generator). Will render Railway's not-found
page until a permanent demo deployment is provisioned at that name; the
inline MDX comment notes the placeholder.
OSS-222
## Summary
- keep `CopilotChat` agents aligned to SDK-generated thread IDs even
when `/connect` is intentionally skipped for non-explicit threads
- stabilize `CopilotKitProvider` default object props so rerenders do
not re-sync an empty local agent registry and replace the live
remote/Intelligence agent mid-run
- add regression coverage for SDK-generated thread frontend-tool
follow-up runs and provider empty-agent rerender stability
- add a focused langgraph-python showcase demo, aimock fixture,
Playwright smoke, and QA checklist for ENT-658
- add a patch changeset for `@copilotkit/react-core`
## Testing
- `npx nx run @copilotkit/react-core:test --
src/v2/components/chat/__tests__/CopilotChat.absentThreadConnect.test.tsx`
- `npx nx run @copilotkit/react-core:test --
src/v2/providers/__tests__/CopilotKitProvider.stability.test.tsx`
- Pre-commit hook passed: `pnpm run test` and `pnpm run check:packages`
- Verified exact `CopilotKit/Intelligence` repro branch
`mme/threadid-repro`: unchecked `Explicit threadId`, sent `invoke
testFrontendToolCalling with label X`, confirmed user message/tool
card/assistant reply remain visible
- Verified the same Intelligence repro with `Explicit threadId` checked
- `pnpm exec playwright test
tests/e2e/threadid-frontend-tool-roundtrip.spec.ts --project=chromium
--workers=1` from `showcase/integrations/langgraph-python`
## QA Checklist
- [x] Reproduce the reset in `CopilotKit/Intelligence` branch
`mme/threadid-repro` with `Explicit threadId` unchecked
- [x] Confirm generated-thread frontend-tool round-trip preserves the
user message, tool card, and assistant response
- [x] Confirm explicit-thread frontend-tool round-trip still preserves
the user message, tool card, and assistant response
- [x] Open `/demos/threadid-frontend-tool-roundtrip` in the
langgraph-python showcase demo
- [x] Confirm `Explicit threadId` is unchecked and the chat starts in
SDK-generated thread mode
- [x] Send `invoke testFrontendToolCalling with label X`
- [x] Confirm the user message remains visible
- [x] Confirm the `testFrontendToolCalling` card remains visible and
shows `label: X` plus `result: handled X`
- [x] Confirm the assistant reply `Frontend tool finished for X.`
appears
- [x] Confirm the chat does not return to the empty state
- [x] Repeat with `Explicit threadId` checked and confirm the
explicit-thread path is unchanged
## Notes
The visible reset had two frontend-side causes. First, the chat and
agent could diverge when the SDK generated the thread ID. Second, in
Intelligence mode, provider rerenders could re-sync an empty local agent
registry and replace the live remote agent instance mid-run, dropping
the in-memory chat stream. Both fixes live in `@copilotkit/react-core`.
The Playwright file is intentionally a smoke test for the demo
route/toggle. The source-level regressions live in
`CopilotChat.absentThreadConnect.test.tsx` and
`CopilotKitProvider.stability.test.tsx`.
Three coupled bugs surfaced from the BIA-as-default cutover, all hitting
the A2UI snippet rendered on /built-in-agent/generative-ui/a2ui:
1. Framework-scoped link rewriter (docs-page-view) blindly prefixed
every root-relative MDX href with the active framework slug, so
`/a2a/generative-ui/declarative-a2ui` rendered as
`/built-in-agent/a2a/generative-ui/declarative-a2ui` (404). Now skip
the rewrite when the first URL segment matches a known framework
slug (registry integrations + docs-only a2a/agent-spec/deepagents)
or a reserved top-level route (/docs, /ag-ui, /reference, /api).
2. Snippet `shared/generative-ui/a2ui.mdx` "Learn More" block linked at
legacy paths (`/generative-ui/specs`, `/ag-ui-protocol`,
`/generative-ui/specs/*`) that the IA retired. Updated to canonical
destinations (`/concepts/generative-ui-overview`,
`/agentic-protocols/ag-ui`, `/generative-ui/<spec>`) so the
framework-prefix rewriter produces valid framework-scoped URLs.
3. S13 redirect (concepts/* -> framework root) was generated for every
legacy framework slug including those whose canonical slug didn't
change (mastra, ag2, agno, ...). The legacy docs never had
/<canonical-slug>/concepts/* pages so the rule never had legitimate
work for them — but shell-docs serves agnostic /concepts/* under
every framework's scope now, and the unconditional rule was 301'ing
those valid URLs to the framework root. Restricted to renamed
frameworks only.
Verified locally: every link rendered on /built-in-agent/generative-ui/a2ui
now resolves to 200; /<unchanged-slug-fw>/concepts/architecture still
serves; /langgraph/concepts/* still collapses to /langgraph-python.
shell-docs renders MDX server-side via MDXRemote, not Fumadocs's compile-
time MDX pipeline, so inline 'import { Boxes } from "lucide-react"' in an
.mdx body doesn't resolve at render time — Boxes ends up undefined and the
page errors with 'Expected component Boxes to be defined' on /cookbook.
Drop the import and the icon prop from the landing's <Card>. Existing
shell-docs pages (e.g. tutorials/ai-powered-textarea/*) use <Card> with no
icon, so this matches the local idiom. The Daytona recipe page is
unaffected because its icon is in frontmatter (icon: 'lucide/Boxes' — a
string, resolved by the page layout, not by MDX body).
OSS-222
Addresses PR review feedback (@tylerslaton): the docs/ folder is deprecated
in favor of showcase/shell-docs and will be removed soon. Move the entire
Cookbook contribution to shell-docs:
- showcase/shell-docs/src/content/docs/cookbook/ — landing + Daytona recipe
copied verbatim (Fumadocs frontmatter/components/dividers all match).
- showcase/shell-docs/src/content/docs/meta.json — new top-level
'---Cookbook---' divider with a '...cookbook' spread, slotted between
Platforms and Other.
- showcase/shell-docs/src/components/brand-nav.tsx — Cookbook tab added to
LEFT_LINKS (lucide ChefHat icon) and active-route detection extended so
/cookbook/* highlights it (peer to the existing Reference handling).
Reverts all earlier edits to docs/ from this PR (navbar, root meta, learn
meta, and the docs/content/docs/cookbook/ tree) so the deprecated folder is
left at zero-diff vs main.
OSS-222
The PR bumps copilotkit==0.1.91 -> 0.1.92 across three showcase
requirements.txt files (langgraph-python, langgraph-fastapi, strands).
The validate-pins ratchet compares the SHA-256 of the sorted [FAIL]
tuple set against the recorded baseline. The langgraph-fastapi tuple
"copilotkit pinned ==0.1.91, Dojo has ==0.1.87" now reads
"==0.1.92, Dojo has ==0.1.87" — same already-failing tuple, new text,
so the FAIL count is unchanged at 106 but the hash flipped.
No new pin drift was introduced (count stays at 106). The
pre-existing langgraph-fastapi <-> Dojo parity gap is out of scope
for this bump and tracked separately. Updating only validatePinsFailHash
to reflect the new tuple text.
Old: d340cdebe623177b957b62576821b51cde7f174b6b788040d67cc87e3d20b702
New: 4355457a222f8011c361da7a848d7361e897ee588ad0b8c6487b851fd0c23b77
Bumps copilotkit Python SDK from 0.1.91 to 0.1.92 across the three showcase integrations that
pin it: langgraph-python, langgraph-fastapi, and strands.
This picks up the header_propagation fix from CopilotKit/CopilotKit#5088, which ensures the
runtime's X-* headers (including X-AIMock-Context) propagate end-to-end through the Python
SDK middleware so D6 testing of langgraph-python sees the expected context routing.
No lockfiles to regenerate — these are plain pip requirements consumed directly by the
integration Dockerfiles.
## Summary
Adds `showcase/bin/railway` — a single-file Ruby tool (stdlib only, no
Bundler/Gemfile) that exposes 9 subcommands for Showcase Railway
operations:
| Subcommand | Purpose |
|---|---|
| `snapshot` | Capture an env's services + config into a YAML snapshot.
|
| `restore` | Restore an env to a snapshot (force-redeploy each
service). |
| `rollback` | Roll a single service back one deploy (`--to
DEPLOYMENT_ID` for specific). |
| `rollback-commit` | Restore an env to the snapshot committed at a
given git SHA. |
| `promote` | Promote staging digests to production with prechecks. |
| `pin` | Pin a service to a specific image digest. |
| `env-diff` | Diff two envs; exits 1 on drift. |
| `resolve-digest` | Resolve an image tag to its `sha256:` digest via
GHCR. |
| `lint-prod` | CI gate: warn if any prod service is not digest-pinned.
Supports `--exit-zero` (advisory mode) and `--format json`
(machine-readable output). |
Spec: https://www.notion.so/36d3aa38185281df97e4cfe11dad7d47 (companion
to the main rollback spec)
## Design highlights
- **Stdlib only** — `net/http`, `json`, `yaml`, `optparse`. No gem deps,
no Gemfile, no Bundler.
- **Auth** — reads `RAILWAY_TOKEN` env var first, falls back to
`~/.railway/config.json`. Never invokes `railway login`/`railway
logout`/`op`.
- **GraphQL** — direct calls to
`https://backboard.railway.app/graphql/v2` using
`serviceInstanceDeployV2` for force-redeploy.
- **GHCR digest resolution** — uses OCI Distribution Spec manifest HEAD
+ `Docker-Content-Digest` header. Anonymous token for public packages.
- **Snapshot YAML schema** — versioned (`version: 1`). Records env-var
KEYS only, never values, so snapshots are safe to commit.
- **Production protection** — every mutating subcommand requires `--yes`
AND a typed `production` confirmation phrase on stdin.
`--non-interactive` skips the prompt but still requires `--yes`. No way
to mutate prod without explicit acknowledgement.
- **Uniform exit codes** — 0 clean, 1 drift/findings/refused, 2 error.
## Promote precheck classes
Per the spec:
- **MOVE**: image digests; startCommand (only with
`--include-startcommand`); auto-update-disable.
- **VERIFY-REFUSE**: service-set parity, critical env-key parity
(RAILWAY_TOKEN, GHCR_TOKEN, SHARED_SECRET, OPS_TRIGGER_TOKEN,
POCKETBASE_SUPERUSER_*, GITHUB_APP_PRIVATE_KEY, OPENAI/ANTHROPIC/GOOGLE
keys).
- **WARN**: missing/extra custom domains (expected:
showcase/dashboard/dojo/docs/hooks.copilotkit.ai for prod,
.staging.copilotkit.ai for staging).
- **IGNORE**: env-scoped URLs, volumes.
## Tests
Minitest suite (stdlib) at `showcase/bin/spec/`:
- `test_cli_parsing.rb` — argv parsing for each subcommand, dispatcher
behavior, env aliases, `lint-prod --format` parsing.
- `test_snapshot_roundtrip.rb` — YAML write/read, schema version
validation, `find_service` helper.
- `test_ghcr_digest.rb` — image-ref parsing across all shapes, digest
resolution decision tree, 404 → nil, 5xx → raise.
- `test_production_protection.rb` — staging bypasses, prod-without-yes
aborts, prod+yes+non-interactive proceeds, typed-phrase prompt
accept/reject.
27 runs, 70 assertions, 0 failures.
```sh
ruby showcase/bin/spec/all_tests.rb
```
## CI integration
New workflow `.github/workflows/showcase_lint_prod.yml` runs on every PR
that touches `showcase/**`:
1. `bin/railway lint-prod --exit-zero --format json` — checks that every
prod service is digest-pinned. (Soft-skips with a warning if
`RAILWAY_TOKEN` secret is unset.)
2. `ruby showcase/bin/spec/all_tests.rb` — runs the test suite.
### lint-prod is advisory during initial soak
The lint-prod step currently passes `--exit-zero`, which makes the
command exit 0 even when findings exist. The workflow is also resilient
to snapshot/GraphQL errors: if `lint-prod` itself crashes for any
reason, the workflow renders an "audit unavailable" block instead of
failing the PR. Findings still print to the job log, so we can see
drift, but they will not block PRs while we soak the check against real
production state.
**Plan to flip to enforcing:**
1. Merge this PR; let the advisory job run on every showcase PR for a
few rounds.
2. Confirm the findings list stays clean (or fix any genuine drift we
surface).
3. Remove `--exit-zero` (and the error-tolerant capture) from the
workflow step in a follow-up one-liner PR to turn lint-prod into a hard
CI gate.
This avoids the failure mode where a brand-new check immediately blocks
unrelated PRs because of pre-existing prod state we haven't audited yet.
### Visibility surfaces
Every run renders the audit result in two places so people don't have to
click into the job logs:
1. **`$GITHUB_STEP_SUMMARY`** — a structured markdown block at the top
of every workflow run page. Shows on every event (`pull_request`,
`push`, `workflow_dispatch`). Contains: one-line status, table of
unpinned services (only — `pinned` services are not enumerated),
Pacific-time run timestamp, finding count.
2. **Sticky PR comment** — on `pull_request` events, the workflow posts
(or updates) a single comment per PR. The comment is keyed by the HTML
marker `<!-- lint-prod-sticky-comment -->` so re-runs PATCH the same
comment instead of creating duplicates. Plain `gh` CLI only — no
third-party action.
The workflow also writes the findings count to `$GITHUB_OUTPUT`, so a
future Slack-alert step can compare against prior runs.
If `lint-prod` itself fails (e.g. a snapshot/GraphQL error), both
surfaces render an "audit unavailable" block with the captured error
inside a `<details>` fold, rather than going blank.
## Test plan
- [ ] CI passes (`Showcase: lint-prod (digest pinning)` job)
- [ ] `showcase/bin/railway --help` lists all 9 subcommands
- [ ] `showcase/bin/railway <sub> --help` works for every subcommand
- [ ] Local: `RAILWAY_TOKEN=... showcase/bin/railway snapshot --env
staging --dry-run` produces valid YAML
- [ ] Local: `RAILWAY_TOKEN=... showcase/bin/railway env-diff staging
production` produces a drift report
- [ ] Local: `RAILWAY_TOKEN=... showcase/bin/railway lint-prod` returns
0 (or 1 if prod drift exists — informational)
- [ ] Local: `RAILWAY_TOKEN=... showcase/bin/railway lint-prod --format
json` emits valid JSON with `services`, `findings`, `timestamp`
- [ ] CI run shows the audit block in the step summary
- [ ] PR has a single sticky comment that updates (not duplicates) on
re-runs
## Summary
Audit of staging + production PocketBase collection rules turned up two
open holes. Both are now closed in both environments and captured as
forward/backward migrations under `showcase/pocketbase/pb_migrations/`.
## Findings
### users.createRule = "" (both envs)
Any anonymous client could POST to `/api/collections/users/records` and
create a real account. The dashboard exposes no signup UX — operators
authenticate via the superuser credentials in `PbAuthPrompt` — so create
should be admin-only.
Verified on prod with curl:
```
POST /api/collections/users/records {anon body} -> 200 (BEFORE)
POST /api/collections/users/records {anon body} -> 403 (AFTER)
```
### baseline.updateRule = "" (prod only — staging has no baseline
collection)
Any anonymous client could PATCH baseline rows, silently flipping status
cells (`works` ↔ `impossible`) and rewriting `updated_by` /
`updated_at`. The dashboard's baseline edit flow already gates writes
behind `PbAuthPrompt`, so locking `updateRule` to admin-only keeps the
existing operator workflow intact.
Verified on prod with curl:
```
PATCH /api/collections/baseline/records/<id> {} -> 200 (BEFORE)
PATCH /api/collections/baseline/records/<id> {} -> 403 (AFTER)
```
## Rule matrix (after this change)
| Collection | list | view | create | update | delete | Notes |
|-----------------|------------------|------------------|--------|--------------------|--------------------|-------|
| users | `id=@req.auth.id`| `id=@req.auth.id`| null | `id=@req.auth.id`
| `id=@req.auth.id` | self-edit only; admin-only signup |
| status | "" | "" | null | null | null | dashboard reads anon, harness
writes as admin |
| status_history | "" | "" | null | null | null | same |
| probe_runs | "" | "" | null | null | null | same |
| baseline (prod) | "" | "" | null | null *(was "")* | null | dashboard
reads anon, edit gated by PbAuthPrompt |
| alert_state | `auth.id != ""` | `auth.id != ""` | null | null | null |
already locked |
The only fields changed by this PR are `users.createRule` (both envs)
and `baseline.updateRule` (prod). Everything else was already correct.
## Procedure followed
1. Read superuser credentials from Railway via direct GraphQL
(`variables` query) on the `pocketbase` service in both environments.
2. Authed against `/api/collections/_superusers/auth-with-password` in
both envs and captured JWTs.
3. Enumerated `/api/collections?perPage=200` and built the before/after
matrix.
4. Confirmed anonymous user signup succeeded against prod (HTTP 200) and
that a probe user was created; deleted it via the admin API.
5. Confirmed anonymous baseline PATCH succeeded against prod (HTTP 200).
6. Applied the rule changes via `PATCH /api/collections/<id>` against
**staging first**:
- `users.createRule` → `null`
- Re-fetched all rules, confirmed.
- Verified anonymous signup now 403, anonymous status read still 200,
dashboard at `dashboard.showcase.staging.copilotkit.ai` still HTTP 200
with a populated HTML payload.
7. Applied the same change set to **production**:
- `users.createRule` → `null`
- `baseline.updateRule` → `null`
- Verified anonymous signup 403, anonymous baseline PATCH 403, anonymous
status + baseline READ both 200, dashboard at
`dashboard.showcase.copilotkit.ai` still HTTP 200 with a populated HTML
payload.
## Test plan
- [x] Staging dashboard renders after change (verified)
- [x] Prod dashboard renders after change (verified)
- [x] Anonymous user signup returns 403 (verified both envs)
- [x] Anonymous baseline update returns 403 (verified prod)
- [x] Anonymous reads of status/baseline still return 200 (verified
prod)
- [ ] On a fresh PocketBase instance, applying these migrations from
scratch leaves the final rule shape identical to the audit (the
migrations key off `findCollectionByNameOrId` so they only mutate the
two fields, leaving everything else untouched).
The tool was written from a spec but never exercised against live Railway,
so several queries reference fields that do not exist in the public
schema. Live runs (including the CI lint-prod step) failed with errors
like `Cannot query field "domains" on type "Project"`. Unit tests passed
because they only covered parsing and IO, not the GraphQL shape.
Verified the live schema via introspection (2026-05) and corrected
every mismatch:
- Project has no `domains` field. The previous `customDomains: domains
{ customDomains { ... } }` block on the Project selection is gone.
Custom domains now come from `serviceInstance.domains.customDomains`
for the env we are inspecting.
- Service has no `serviceInstances` field. We can no longer enumerate
per-env instances by nesting under Service. The new flow is:
1. SERVICES_LIST_QUERY -> list services in the project
2. SERVICE_INSTANCE_QUERY -> per (service, env), fetch source,
startCommand, latestDeployment, domains
3. ENVIRONMENT_VARIABLES_QUERY -> all variables in the env, then
group keys by Variable.serviceId for per-service env_keys
- `serviceInstanceDeployV2` does not accept an `image` argument; its
signature is (commitSha, environmentId, serviceId). To pin a service
to a specific image we now use
serviceInstanceUpdate(input: { source: { image } })
followed by serviceInstanceRedeploy. RestoreCommand exposes a
pin_and_redeploy class method that PromoteCommand and PinCommand
reuse.
- `deploymentRollback` returns scalar Boolean, so the previous
`deploymentRollback(id: $id) { id }` was invalid GraphQL — selection
sets are not allowed on scalars. Dropped the selection set.
- Auth.token now reads `user.accessToken` from ~/.railway/config.json
first. The legacy `user.token` field is a short CLI session token
(4 chars on a fresh login) that does not authenticate against the
public GraphQL API and was producing silent "Not Authorized" errors.
Added spec/test_snapshot_graphql.rb with a FakeGQL that returns realistic
shapes, plus regression guards that fail the build if anyone reintroduces
`Project.domains`, `Service.serviceInstances`, `serviceInstanceDeployV2`
with an image arg, or a selection set on `deploymentRollback`.
Smoke-tested live (read-only) against the showcase project:
- lint-prod: "OK: all production services digest-pinned." (27 services)
- snapshot --env staging: full YAML with images, startCommands, env_keys
- env-diff staging production: 32 drift findings (expected, staging is
not digest-pinned)
- resolve-digest ghcr.io/copilotkit/showcase-aimock:latest: digest
returned successfully
No mutating subcommands (restore, rollback, promote, pin) were run live.
Make the lint-prod audit result legible without having to click into the
workflow logs. Two surfaces, both rendered from the same JSON payload:
1. `$GITHUB_STEP_SUMMARY` — structured markdown block at the top of every
workflow run page. Shows on every event (push, pull_request,
workflow_dispatch).
2. Sticky PR comment — one comment per PR, keyed by the HTML marker
`<!-- lint-prod-sticky-comment -->`. Re-runs update the same comment via
`gh api -X PATCH` instead of creating duplicates. Plain `gh` CLI only,
no third-party action.
Both surfaces show: one-line status, a table of the unpinned services only
(not all 27), and a Pacific-time run timestamp with the finding count.
To support the renderer, add `--format json` to `lint-prod`:
{services:[{name,source,status}], findings:N, timestamp:"ISO8601"}
The workflow consumes this shape and also writes `findings` to
`$GITHUB_OUTPUT` so downstream jobs (future Slack alert) can compare runs.
Idempotent: re-running the workflow finds the existing comment by marker
and PATCHes it — never duplicates.
Add --exit-zero flag to bin/railway lint-prod that makes the command exit 0
even when digest-pinning findings exist. Findings still print to stdout so
they remain visible in the CI step log.
Wire the showcase_lint_prod.yml workflow to pass --exit-zero so the job
cannot block PRs while we soak the check against real production state.
Once we have confidence the findings are clean, remove --exit-zero from
the workflow step to flip lint-prod to enforcing.
Updates README to document the advisory-mode behavior and the path to
flipping the check to enforcing.
Audit of staging + production PocketBase rules turned up two open holes:
- users.createRule = "" allowed any anonymous client to POST to
/api/collections/users/records and create a real account. The
dashboard exposes no signup UX — operators authenticate via the
superuser credentials in PbAuthPrompt — so create should be
admin-only.
- baseline.updateRule = "" (production only) allowed any anonymous
client to PATCH baseline rows, including silently flipping status
cells and overwriting the updated_by/updated_at audit fields. The
dashboard's baseline edit flow already gates writes behind
PbAuthPrompt, so locking updateRule to admin-only keeps the existing
operator workflow intact while removing the open hole.
Both changes were applied via the PocketBase admin API to staging first
(verified dashboard still renders and live status SSE still flows),
then to production (same verification, plus 403 confirmations on the
anonymous signup + anonymous baseline PATCH requests that previously
returned 200).
All other collection rules already had the right shape: status,
status_history, probe_runs, baseline retain listRule/viewRule = ""
because the dashboard reads them unauthenticated via the PocketBase JS
SDK; create/update/delete rules stayed null because the harness writes
with the superuser JWT.
Fumadocs's Tab component applies escapeValue() internally to the value
prop. Our DocsTab wrapper was also calling escapeValue() before passing
to FumadocsTab, causing multi-word tab values to be escaped twice.
For "JSON Configuration File" (3 words, 2 spaces):
1st escape (our wrapper): "json-configuration file" (1 space left)
2nd escape (Fumadocs Tab): "json-configuration-file" (fully hyphenated)
The trigger value uses only ONE escapeValue call:
escapeValue("JSON Configuration File") = "json-configuration file"
Trigger "json-configuration file" != content "json-configuration-file"
so Radix sets data-state="inactive" on the content panel, which is
then hidden by data-[state=inactive]:hidden.
Fix: remove escapeValue() from our Tab wrapper. The Tabs defaultValue
still needs pre-escaping because FumadocsTabs accepts it as-is (no
internal escape); only the individual Tab has internal escaping.
Single-word and two-word tabs (HTTP, Application Settings) were
unaffected because one escapeValue pass already produces a hyphen-only
string that is idempotent under a second pass. Same bug also affected
"stdio Transport (Local)" in the Windsurf section.
Three classes of legacy URLs were 404'ing because shell-docs (with BIA
as the soft-default framework) doesn't serve them at the root surface
the old docs did:
1. BIA-canonical pages — /server-tools, /mcp-servers, /model-selection,
/advanced-configuration, /agent-app-context live only under
/built-in-agent/ now. Internal sidebar clicks already framework-scope
via SidebarLink; external traffic (marketing, blog posts, bookmarks)
was 404'ing.
2. Moved root pages — /mcp-apps (moved to /generative-ui/),
/copilot-runtime, /custom-agent (moved to /backend/), /deep-agents
(renamed to /deepagents), /multi-agent-flows (LangGraph-only),
/custom-look-and-feel folder index, /generative-ui/specs/* (specs
subgroup retired), plus assorted misc (/what-is-copilotkit,
/getting-started/quickstart-chatbot, /telemetry, /migration-guides/*,
/reference/hooks/useCoAgent).
3. Legacy /integrations/<fw>/* prefix — R15/R17 already handled the
built-in-agent variant; this extends the same pattern to every other
framework, mirroring the existing /docs/integrations/* coverage.
All redirect destinations verified to return 200 against a local dev
build; existing tests still pass.
The @ag-ui/aws-strands TypeScript adapter ships alongside the Python
ag_ui_strands package but the docs only showed Python snippets. Add a
TypeScript tab next to every Python snippet (Python default, `persist`
on the tab group so a reader's choice sticks across pages) covering:
- quickstart: project init, install, agent file, run command
- frontend-tools: @tool stub + createStrandsApp server
- shared-state (read + write): StrandsAgentConfig.stateContextBuilder
- generative-ui tool-rendering: backend tool definition
- generative-ui state-rendering: ToolBehavior.stateFromArgs
Also applied to the parallel showcase/shell-docs tree. Non-code pages
(deploy-agentcore, copilot-runtime, inspector, etc.) remain untouched
since they either re-export shared snippets or have no framework code.
Jordan Ritter