The SDK documentation should be written after the SDK contract is frozen and reconciled with the runtime implementation.Documentation Index
Fetch the complete documentation index at: https://docs.airglow.cc/llms.txt
Use this file to discover all available pages before exploring further.
Planned page set
| Page | Scope | Size |
|---|---|---|
| App model | What an app is and where code lives | Medium |
| Runtime contexts | Userscript, UI, startup, and server boundaries | Medium |
| Manifest | Manifest schema and validation rules | Large |
| SDK API | Method-level browser SDK reference | Large |
| Server RPC | Server functions, payloads, errors, and secrets | Medium |
| Security and permissions | Permission model, secrets, review checklist | Large |
| Local debugging | First-run diagnosis and developer inspection flow | Medium |
Before writing
- Freeze the SDK contract.
- Compare the contract with the runtime implementation.
- Compare the contract with generated TypeScript declarations.
- Decide which examples are stable enough to publish.
- Keep non-final behavior out of the public docs.
Estimated volume
The first useful SDK docs pass is roughly 7 pages. The large pages areManifest, SDK API, and Security and permissions; those should wait until the spec is stable.