fix(framework): the FAQ promises no telemetry while we ship it

[blafourcade]

Context

docs/FAQ.md:44 states, as a public commitment:

No hosted service. AIDD is prompt content you install into your own tool; there is no AIDD server, account, or telemetry.

Expected

The published documentation describes what the framework actually does, and a reader deciding whether to install it is not misled about what it collects.

Actual

The sentence becomes false in three steps, and no issue updates it.

• At milestone 14 the framework writes a session journal into the repository and configures a provider export. "No telemetry" stops being true.
• At milestone 15 a skill reads it back.
• At milestone 16 data leaves the machine towards a hosted dashboard. "No AIDD server" stops being true too.

The claim is load-bearing in a way a stale doc line usually is not: it is the answer people quote when asking whether the framework watches them. Leaving it while shipping the opposite is worse than never having written it.

Reproduction

Read docs/FAQ.md:44, then read #620, #646 and #656.

Scope

• The FAQ entry, rewritten to describe what is collected, where it goes, what is off by default, and how to turn it off.
• A search for the same claim elsewhere: README.md and docs/ were checked and carry no duplicate today, but that must be re-checked at the time of the change.
• The privacy commitments that survive, stated positively rather than as an absence: no prompt content, no code, no diff, off by default on public repositories, and a local-only default.

Done When

• No published document claims the framework collects nothing while it does.
• The entry states what is collected, where it is written, and the command that disables it.
• The entry distinguishes what stays on the machine from what may leave it, and names which milestone introduces the second.
• The change lands with the milestone that first makes the old wording false, not after it.

Relations

Field	Value
parent	#631
related	#620, #646, #656

[blafourcade]

Closed. Measurement has its own FAQ section rather than a bullet doing four jobs: off unless you turn it on, what is recorded and where, what is never recorded, that nothing leaves the machine today, and that turning it off keeps what was already measured.

The remaining claim — "there is no AIDD server and no account" — was checked and is still true. It becomes false the day #662 lands, and that ticket owns it.

The plugin's own README stopped describing a plugin that ships hooks only and does nothing yet; it now carries a coverage table naming what each tool cannot do and the ticket that would close it. docs/telemetry-limits.md holds every limit with the measurement behind it.