docs: flag dependencies follow how clients read the parent

[adamXbot]

What

Documents the feature-flag dependency rule on develop/feature-flags.mdx, to match privacykey/privacytracker#364 (stacked on #363):

• New Dependencies section: the parent is resolved through the whole chain first, its own override included; a tri-state parent (hard default 'collapsed') turns its dependents off only at 'off'; a two-state parent still does at anything but 'on'. Names the two tri-state edges (accessibility preference highlights under the accessibility panel, the run log's full trace under the run-log strip) and why a two-state parent at 'collapsed' still hides its dependents.
• The resolution-order sketch splits the old "runtime checks (Tauri, dependencies)" line into the desktop-only step and the dependency step, in the order the resolver runs them.
• Replaces "roughly 8–12 flags use it" with the actual seven tri-state flags, which are exactly the ones whose hard default is 'collapsed'.

llms-full.txt is regenerated (npm run llms); npm run check passes. The added lines contain no {, }, < or >.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	docs-privacytracker	3e128b3	Commit Preview URL Branch Preview URL	Oct 02 2026, 02:04 PM