feat(framework): report per person, team and epic #656

As a tech lead
I want a week of work broken down by person, tool, model and step
So that I can see where the effort and the money actually go, across a team rather than a folder

Acceptance

• A report covers several repositories and several people, over a chosen period.
• The attached and unattached shares are both shown; a report that silently measures two thirds is a failed report.
• Reported and computed cost stay distinguishable all the way through aggregation.
• Nothing is uploaded that the redaction issue does not allow.
• A person can see their own figures, and what is shared about them, before anyone else does.
• Upload failure never blocks or slows a session, and the local figures remain readable without it.

What it looks like

Marie — week 33
  3 features, 2 bugs, 1 spike
  active time        11h40
  tokens             2.1M      34% cache
  cost               $47       reported $41 · computed $6
  attached           61%       out of task 39%, of which /debug 22%
  by step            implement 61% · review 19% · plan 12% · rest 8%
  by model           opus 78% of cost for 31% of calls

The decision that gates this milestone — made

Settled on 2026-08-31 by @blafourcade, in writing: aidd_docs/memory/internal/decisions/measurement-may-reach-a-hosted-destination.md, posted on #297.

#297's privacy clause is reaffirmed unchanged. Its standard clause — "Sink is an OTel collector. No SaaS." — is superseded: a hosted destination is allowed, and it is never ours to fix. The person names the destination, what travels is the already-published record contract, anyone can run their own and lose no capability, and nothing about measuring or reading requires an account.

The argument this section used to carry is also factually out of date, and its correction is what makes the decision liveable:

• The journal names nobody. No line it writes carries any identity field. It records the repository, the task folders written into, the skills run and their timings.
• It does not enter git history. aidd telemetry on git-ignores it; committing it takes deliberately deleting that line.
• A person can refuse, and their refusal wins. AIDD_TELEMETRY=0 is honoured by the hooks and the CLI alike and overrides whatever a repository's committed switch says — which answers "the safeguard protects the wrong people" directly.
• A person can remove what was measured. aidd telemetry forget shows what would go, and what git history keeps whatever it does, then removes it on confirmation.

One boundary from that decision binds this milestone directly: the framework exposes, the destination analyses. Aggregating across people and repositories belongs to a hosted destination, not to what runs on a machine.

Out of scope

• Any judgement rendered on an individual. The report shows distribution, not performance.

Relations