Cardano Updates

Added complete context to all aiken code examples, using following template:

**Template:**
```aiken
// [Title]
// Purpose: [What this solves]
// Use Case: [When to use]

fn example(
  param1: Type1,  // [Explain]
  param2: Type2,  // [Explain]
) -> ReturnType {  // [Explain]

  // Step 1: [What this does]
  let result = operation()

  // Step 2: [What this does]
  result
}

// Explanation:
// [Detailed how it works]

// Usage:
// [How to call/use]

// Common Mistakes:
// ❌ [What not to do]
// ✓ [What to do instead]

There are a few approaches for making content on the Aiken docs site machine-readable but not human-visible in the normal browsing experience:
The llms.txt Standard
The most established convention is adding llms.txt and/or llms-full.txt files to the site root. This is a growing standard where sites provide structured content specifically for LLM consumption. Humans wouldn't normally navigate to these files. You'd add something like:
/llms.txt — a concise overview with links to key docs
/llms-full.txt — the full concatenated content of all relevant MDX files
This is what many projects are adopting (Anthropic, Vercel, etc.).

All 14 files concatenated into a single llms-full.txt — about 396K characters across ~9,100 lines. Here's what the script did:
Stripped YAML frontmatter, import statements, and JSX tags (like <Callout>)
Ordered sections logically: language tour (primitive types → variables → functions → custom types → control flow → modules → validators → tests → benchmarks → design patterns → troubleshooting), then tutorials (Hello World, Gift Card, MeshJS)
Added clear ==== section separators so an LLM can orient itself within the file
Added a header identifying the source and purpose
You'd drop this file into the public/ directory of the Aiken site repo so it's served at https://aiken-lang.org/llms-full.txt. You could also create a shorter llms.txt manifest that just lists section titles with links if you want the two-tier approach.