Release v6.0.4 · agentdecksdk/agentdeck

Docs navigation on a phone collapses down from the bar instead of sliding in from the side.
It fills the screen under the header, the tree scrolls inside it, and the bar's control is a menu
closed and an X open. The page behind no longer moves while it is open.
Ask Jack on a phone is a full-screen page and no longer opens the keyboard by itself. The
composer takes focus only on the docked panel, where typing is the next action; on a phone the
keyboard used to cover the transcript and the suggestions before anything had been asked.

Troubleshooting lists the binding errors where they actually raise (#750). Two of the four
ConfigError causes under "At build time" raise from deck.expose(...) or deck.serve(...), not
from Deck(...): a deck is valid on its own, and a set of bindings is checked when they are put
together. They now have their own section, with the three causes the page never listed.
The agent-with-a-skill example links to the documentation site (#726). Both "next" links
pointed at a personal github.io mirror that is being unpublished.
Sharing a docs page renders the social preview card instead of a blank one (#733). The site
declared twitter:card=summary_large_image and an Open Graph block with no image in either, so
every crawler that honoured the declaration reserved a large card and had nothing to put in it.
The site now serves a rendered PNG at /brand/social-card.png, because no crawler renders SVG
for a preview, and the card artwork is the light landing-page treatment in both docs/brand/
and docs-site/public/brand/.

Docs no longer deploy to GitHub Pages (#724). The real site is served from its own domain;
the Pages mirror hadn't worked since the Fumadocs migration. docs-pages.yml is deleted, and
next.config.mjs no longer branches on GITHUB_ACTIONS to add a /agentdeck prefix, so CI's
Build documentation now builds the same output prod serves.

scripts/check_docs_impact.py accepts an indented docs-impact acknowledgement (#719). The
checklist line was anchored at column 0, so a Markdown list-continuation indent (identical when
rendered) failed silently, listing every affected page as unacknowledged. Leading whitespace is
now accepted, and the failure output now also names the gh run rerun / stale PR_BODY gotcha.
scripts/release_bump.py issues finds a squash-merged release's milestone issues again
(#699). It looked for Merge pull request #N commits, a shape this repo's squash-merge
workflow never produces, so it silently milestoned nothing; it now resolves each commit's
merged PR and reads GitHub's own closingIssuesReferences.
A run that fails between its claim and its play now folds to failed, not cancelled
(#688). An infrastructure fault there (a store write, a control-signal read) used to close the
run with run.cancelled, the same terminal kind a real cancellation gets, with the true cause
readable only in the reason prose. It now writes run.failed with error_code="engine_error",
the same code the identical fault gets inside a run's own engine loop, so an operator's failure
listing or an incident metric keyed on run.failed sees it. A cancellation between the claim
and the play still folds to cancelled, unchanged. Any consumer that filtered on a run's folded
status will now see these runs move from its cancelled set to its failed set.

The docs site nav states which version it documents (#686), sourced from
generated-version.ts so it follows the release bump automatically.

The documentation site runs on Fumadocs instead of Nextra 4 (#683). Same 44 URLs, same
Pagefind search, same pages. Nextra's loader routed every fenced block through twoslash,
whose peer range pinned TypeScript below 7 (#664); nothing does now.
brand.css targets Fumadocs' own DOM and tokens instead of Nextra's leftovers (#691). The
sidebar and table-of-contents active states now recolor through Fumadocs' own
--color-fd-primary token; the announcement bar reads 4.88:1 white-on-blue (AA, disclosed on
#691); the docs-site build has zero remaining .nextra-* selectors.

Navigation Menu