Cardano Updates

Module 6 had a Governance page (SDK how-tos) and a separate "Governance via
cardano-cli" category covering the same operations plus deep ceremonies. Add
cardano-cli as a third tab alongside Evolution and Mesh for each operation
(register DRep, delegate, vote, propose, committee, query), and continue the
deeper cli-only ceremonies inline: script and Plutus DReps, authoring each
action type, committee cold/hot key management, and the governance queries.

Delete the six cardano-cli pages and the sidebar category, point the operator
governance page at the consolidated sections, and retarget the old cli
governance redirects to the page.

The section split the same detection loop (poll an address, compare the
received amount) across three method pages plus an overview. Consolidate
into a single page with the methods as tabs: Blockfrost (recommended,
hosted), cardano-cli (own node), and cardano-wallet (REST service). Each
tab keeps the essential query-and-compare code and links out for the deeper
walkthrough (the Blockfrost point-of-sale app links to its starter repo).

Delete the three method pages, collapse the sidebar category to a single
entry, repoint the inbound link, and redirect the old prod URLs to the page.

Wallet Authentication was split across a concept page, a separate Mesh guide,
and an autogenerated UTXOS subtree. Roll it into one page: the concept, an
"implement it yourself" section with Mesh and Evolution in tabs, a hosted
sign-in section pointing to UTXOS as a service, and a zero-knowledge login
earmark for zklogin-aiken. Delete the Mesh and UTXOS pages, repoint inbound
links, and redirect their prod URLs to the page.

Broaden the Integrations "AI Agents" category to "AI" and add a highlighted
AI-assisted development page for Cardano Dev Skills, the plugin that gives AI
coding assistants current Cardano context. The overview now frames the two
scopes: AI as a development aid versus autonomous on-chain agents.

Fix the Token Registry sidebar so the category opens its overview directly
(the category-link pattern used everywhere else) instead of listing overview
as a separate item.

builderVersion = 2 runs a test's installed binary directly (not via
`cabal v2-test`) in an empty dir with only runtime libs on PATH, so tests
that rely on the environment cabal normally provides failed.  Bring the v2
`check` (lib/check.nix) in line with v1 / cabal v2-test:

- Set each installed package's `<pkg>_datadir` (the env var Cabal's
  `Paths_<pkg>` consults) to the `share` dir the slice stages under
  `$out/store/ghc-*/<unit>/share`, so `getDataFileName` finds `data-files`
  (the compiled-in datadir is an ephemeral build-time cabal dir).

- Put the component's `build-tool-depends` (`executableToolDepends`,
  including same-package exes a test spawns) on PATH, so e.g. a test that
  spawns its package's exe no longer fails with `spawnProcess: ... does not
  exist`.

- Run the test from a writable copy of the package source subdir
  (`passthru.srcSubDirPath`), so tests reading source-relative files
  (golden files / fixtures) find them — mirroring v1's unpack + cd.

All three happen before `preCheck` so a project's own `preCheck` can still
override them.  Exes are unaffected (they install to the store with a
correct, persistent datadir).

Adds the `check-datadir` test: a library package shipping a data-file, a
source-relative file, and a build-tool exe, with a test-suite that reads /
spawns all three — run under both builderVersion 1 and 2.

The languages/ subsection was mostly thin: only Aiken had real content, the
Plutarch subtree duplicated the Design Patterns data structures, and the rest
were install steps plus external links that Choose a Language already
aggregates.

Choose a Language becomes the single hub: its comparison table links out to
each language's official docs, and a compact "Getting started with Aiken"
section carries the install and learning resources. The language-agnostic DeFi
patterns the Plutarch dApps demonstrated (vesting, P2P/atomic swaps, reward
accrual, routing, bridges) fold into a new section on the DeFi page, each
composing the existing Design Patterns primitives and pointing to open-source
reference implementations.

Delete the languages/ tree, drop the Languages sidebar category, repoint
inbound links to the hub or upstream docs, and redirect the established prod
URLs (data structures to Design Patterns, the dApp patterns to the DeFi page).

Dev Blog appeared in both the Developers and Ecosystem menus; keep it in
Ecosystem only. Add a data-column-count="1" width rule so the simplified
Operators menu renders as a single narrow column instead of reserving three
columns of empty width.

Group Module 7's infrastructure pages under an Infrastructure category that
lands on the infrastructure overview. Reorder Community to Developer
Community, Talent Pool, Funding.

Reshape Module 5 (Build a dApp): Scaffolding, Connect a wallet, Wallet
Authentication, DeFi on Cardano, DeFi Kernel, Oracles. Add a Scaffolding page
(starter templates today plus the cardano-init tool in development), a DeFi
Kernel page (the open order-book standard), and a Cardano DeFi map link.

Stop naming specific third-party apps in conceptual prose. Generalize DeFi
protocols, wallets, and example tokens to categories, pointing to
cardano.org/apps for the live list. Developer tooling (SDKs, infra providers,
oracles) and hands-on tutorials keep their specifics.

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.52.0 to 0.53.0.
- [Commits](https://github.com/golang/crypto/compare/v0.52.0...v0.53.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-version: 0.53.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Wrap the operator sidebar's eight setup steps under a Handbook category,
mirroring the developer Curriculum grouping, with Overview on top and
Operator Tools alongside.

Rename the navbar's Validators dropdown to Operators (matching the reorg)
and collapse it from seven enumerated steps to three high-level entries:
Overview, Handbook, and Operator Tools. The sidebar carries the depth.

Community had three overlapping docs. Careers re-listed the same channels,
pointed at Catalyst again, and duplicated the Contributing section and the
curriculum. Funding led with Project Catalyst and a Builder DAO that no
longer operates, then a prescriptive "which door do I use" tab flow that
broke once Catalyst paused.

Fold the useful parts of Careers (ecosystem entities, founding-entity job
boards) into a Jobs section on the Developer Community page and drop the
rest. Rewrite Funding as a neutral map of the current avenues: Catalyst,
on-chain treasury withdrawals, Intersect grants, the Maintainer Retainer
Program, and other paths to watch, each linking out for live status rather
than baking in transient state. Talent Pool stays its own landing.

Repoint the footer Careers link and the careers redirects to the Community
page.

The folder structure never caught up with the curriculum. Readers saw a
clean module path in the sidebar while the files still sat in legacy
buckets (learn/, value/, foundations/, get-started/) next to build/ and
native-tokens/. Contributors had to hold two mental models.

Collapse everything into the structure readers actually navigate:

- docs/developers/ holds the developer sidebar: a curriculum/ tree with
  numbered module folders (01-fundamentals through 07-production) plus an
  integrations/ section. Numeric prefixes order the tree; Docusaurus
  strips them so URLs stay clean.
- docs/operators/ holds the stake pool content (was operate-a-stake-pool/)
  plus a security/ folder for the air-gap and secure-workflow guides.
- community/ and contribute/ stay top-level as cross-cutting meta.

No get-started/, infrastructure/, learn/, build/, value/, foundations/,
or first-steps/ buckets survive. Shared node pages live once under
Module 7 and the operators sidebar cross-links them.

Mechanics: ~260 file moves, every internal /docs/ link rewritten by
prefix, sidebars.js re-keyed (networkSidebar is now operatorsSidebar),
redirect targets repointed so old prod URLs resolve straight to the
final location, and the llms path-fix script and includeOrder globs
updated. Old prod URLs keep working through redirects; curriculum-spine
URLs were never published so they need none.

The developer sidebar groups the seven modules under a Curriculum
category so the navigation mirrors the developers/curriculum/ tree, with
Start Here on top and Integrations/Community/Contributing alongside.

Also drops the two orphaned cardano-wallet REST-server pages. They sat in
no sidebar, taught the legacy run-your-own-wallet-backend approach the
curriculum already covers through SDKs and API providers, and only the
payments-listening guide referenced them (now pointed at the upstream repo).

Add a docker-compose.yml to each cloud-sink example so it runs with no real
cloud account, and document the standalone workflow in each README:

- aws_s3 / aws_sqs / aws_lambda — LocalStack + an init script that provisions
  the bucket / queue / function. The AWS SDK honors AWS_ENDPOINT_URL, so no
  code change is needed; the READMEs show the env vars to target LocalStack.
- gcp_pubsub — Google's Pub/Sub emulator + a curl init container creating the
  topic and a subscription. Targeted via PUBSUB_EMULATOR_HOST.
- gcp_cloudfunction / webhook_basics — an http-echo server stands in for the
  HTTP endpoint.

Each README gains "Run standalone" and "Run against real <cloud>" sections.
All six were verified end-to-end against the bundled services.

Also fix a pre-existing bug in aws_s3/daemon.toml: the AwsS3 sink only accepts
Record::CborBlock, but the example ran a ParseCbor filter, so it errored on the
first block regardless of AWS. Removed the filter (N2N already emits CborBlock).

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>