Suggestion: HADS format for context files — reduces token waste for loaded docs

Plandex loads context files into the agent's working memory. When those files are human-written docs, the agent burns tokens on narrative to extract a handful of facts.

HADS (Human-AI Document Standard) is an open Markdown convention that structures docs for AI-first consumption: https://github.com/catcam/hads

## API Auth

**[SPEC]**
- Method: Bearer token
- Header: `Authorization: Bearer <token>`
- Expiry: 3600s

**[NOTE]**
Switched from cookie auth in v2. Legacy docs mentioning cookies are outdated.

**[BUG] Token silently rejected after password change**
Symptom: 401 identical to expired token
Fix: Re-authenticate after any account operation

An AI manifest at the top tells Plandex what to read and skip — same principle as your context management, but baked into the doc format itself.

Two possible integrations:

1. Recommend HADS in docs as a best practice for context files
2. Auto-detect HADS manifests and use them to prioritize which sections to load

No tooling overhead — pure Markdown, works in any editor.