docs: add support for llms.txt

Author: captainsafia

site/astro.config.mjs

@@ -9,6 +9,11 @@ export default defineConfig({
   vite: {
     plugins: [tailwindcss()]
   },
+  markdown: {
+    shikiConfig: {
+      theme: 'css-variables'
+    }
+  },
   redirects: {
     '/docs': '/docs/installation'
   }

site/src/content/config.ts

@@ -0,0 +1,12 @@
+import { defineCollection, z } from "astro:content";
+
+const docs = defineCollection({
+  type: "content",
+  schema: z.object({
+    title: z.string(),
+    description: z.string().optional(),
+    order: z.number().optional(),
+  }),
+});
+
+export const collections = { docs };

site/src/content/docs/assertions.md

@@ -0,0 +1,125 @@
+---
+title: Assertions
+description: Reference for all Hone assertion types
+order: 4
+---
+
+Hone provides a rich set of assertions for verifying command output, exit codes, timing, and file contents.
+
+## Output Assertions
+
+### stdout
+
+Assert on the standard output of the most recent (or named) command:
+
+```hone
+# Contains - check if output includes text
+ASSERT stdout contains "success"
+ASSERT stdout contains "Hello, World!"
+
+# Equals - exact match
+ASSERT stdout == "exact output"
+ASSERT stdout != "not this"
+
+# Regex - pattern matching
+ASSERT stdout matches /version \d+\.\d+\.\d+/
+ASSERT stdout matches /hello world/i  # case insensitive
+```
+
+### stderr
+
+Assert on the standard error output:
+
+```hone
+# Same operators work for stderr
+ASSERT stderr contains "warning"
+ASSERT stderr == ""
+ASSERT stderr matches /error: .*/
+```
+
+### Raw Output
+
+By default, ANSI escape codes are stripped from output. Use `.raw` to preserve them:
+
+```hone
+# Access raw output with ANSI codes preserved
+ASSERT stdout.raw contains "\x1b[32m"
+```
+
+## Exit Code Assertions
+
+Verify the exit status of commands:
+
+```hone
+# Check exit status
+ASSERT exit_code == 0
+ASSERT exit_code != 0
+ASSERT exit_code == 42
+```
+
+## Duration Assertions
+
+Check how long a command took to execute. Supports `ms`, `s`, `m`, and `h` units:
+
+```hone
+# Time constraints
+ASSERT duration < 500ms
+ASSERT duration <= 2s
+ASSERT duration < 1m
+```
+
+## File Assertions
+
+### Existence
+
+Check if a file exists:
+
+```hone
+# Check file existence
+ASSERT file "output.txt" exists
+ASSERT file "/tmp/cache.json" exists
+```
+
+### Content
+
+Assert on file contents using the same operators as stdout:
+
+```hone
+# Check file contents
+ASSERT file "config.yaml" contains "enabled: true"
+ASSERT file "output.json" == '{"status": "ok"}'
+ASSERT file "version.txt" matches /v\d+\.\d+/
+```
+
+## Named Run Targets
+
+When you have multiple RUN commands, use named runs to assert on specific ones:
+
+```hone
+RUN compile: gcc main.c -o main
+RUN test: ./main --test
+
+# Reference specific commands
+ASSERT compile.exit_code == 0
+ASSERT compile.stdout contains "compiled"
+ASSERT compile.duration < 30s
+
+ASSERT test.exit_code == 0
+ASSERT test.stdout contains "PASSED"
+```
+
+## Assertion Operators
+
+| Operator | Description | Example |
+|----------|-------------|---------|
+| `contains` | Substring match | `stdout contains "ok"` |
+| `==` | Exact equality | `exit_code == 0` |
+| `!=` | Not equal | `stderr != ""` |
+| `matches` | Regex pattern | `stdout matches /v\d+/` |
+| `exists` | File exists | `file "x.txt" exists` |
+| `<` | Less than | `duration < 5s` |
+| `<=` | Less than or equal | `duration <= 10s` |
+
+---
+
+**Next Steps**: Learn about configuration options in the [Configuration](/docs/configuration) guide.

site/src/content/docs/configuration.md

@@ -0,0 +1,141 @@
+---
+title: Configuration
+description: Configure Hone through pragmas, CLI, and editor integration
+order: 5
+---
+
+Hone can be configured through file pragmas, CLI options, and editor integration. This page covers all configuration options.
+
+## File Pragmas
+
+Pragmas at the top of a `.hone` file configure that file's test execution:
+
+```hone
+#! shell: /bin/zsh
+#! env: NODE_ENV=test
+#! env: DEBUG=true
+#! timeout: 30s
+
+TEST "my test"
+RUN echo $NODE_ENV
+ASSERT stdout contains "test"
+```
+
+| Pragma | Description | Default |
+|--------|-------------|---------|
+| `shell:` | Shell executable path | `/bin/sh` |
+| `env:` | Environment variable (can repeat) | — |
+| `timeout:` | Max execution time per command | — |
+
+## CLI Options
+
+The `hone` CLI accepts several options:
+
+```bash
+# Use a custom shell
+hone run --shell /bin/zsh tests/
+
+# Show verbose output (useful for debugging)
+hone run --verbose tests/
+
+# Show version
+hone --version
+
+# Show help
+hone --help
+```
+
+## Language Server (LSP)
+
+Hone includes a built-in Language Server that provides IDE features for `.hone` files.
+
+### Features
+
+- **Diagnostics** — Real-time syntax and semantic checking
+- **Completion** — Context-aware snippets for keywords and assertions
+- **Hover** — Documentation for keywords and assertions
+- **Outline** — Document structure view
+- **Formatting** — Consistent indentation and spacing
+- **Semantic Highlighting** — Rich syntax highlighting
+
+### Starting the Server
+
+```bash
+# Start the language server
+hone lsp
+```
+
+### Editor Setup
+
+Use the `setup` command to automatically configure your editor:
+
+```bash
+# Configure VS Code
+hone setup vscode
+
+# Configure Neovim
+hone setup neovim
+
+# Configure multiple editors
+hone setup vscode neovim
+
+# List supported editors
+hone setup
+```
+
+### Manual VS Code Configuration
+
+Add to your `settings.json`:
+
+```json
+{
+  "hone.languageServer": {
+    "enabled": true,
+    "command": "hone",
+    "args": ["lsp"]
+  }
+}
+```
+
+### Manual Neovim Configuration
+
+With `nvim-lspconfig`:
+
+```lua
+local lspconfig = require('lspconfig')
+local configs = require('lspconfig.configs')
+
+if not configs.hone then
+  configs.hone = {
+    default_config = {
+      cmd = { 'hone', 'lsp' },
+      filetypes = { 'hone' },
+      root_dir = lspconfig.util.root_pattern('.git'),
+      single_file_support = true,
+    },
+  }
+end
+
+lspconfig.hone.setup{}
+```
+
+## Exit Codes
+
+Hone uses the following exit codes:
+
+| Code | Meaning |
+|------|---------|
+| 0 | All tests passed |
+| 1 | One or more tests failed |
+
+## LSP Logs
+
+LSP logs are written to platform-specific locations:
+
+- **Linux** — `~/.local/state/hone/lsp.log`
+- **macOS** — `~/Library/Application Support/hone/lsp.log`
+- **Windows** — `%LOCALAPPDATA%\hone\lsp.log`
+
+---
+
+**You're all set!** Check out the [Examples](/examples) page to see Hone in action with real-world test files.