Classify the issue_activity family in the export ledger

The activity read landed with its routes classified in
ApiRouteAuthority but no entry in the data-rights export ledger, so
the ledger's coverage proof went red: every published API family must
be classified before the export question can be answered for it. The
family is a derived assembly — threads that named the issue plus the
receipts reachable from its commit references — storing nothing of its
own, and every record it shows exports through its own family, so it
is classified not_user_data.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RfZq5s3rc6zpnBR75pTQaU

Co-Authored-By

Claude Fable 5 <noreply@anthropic.com>

Claude-Session

https://claude.ai/code/session_01RfZq5s3rc6zpnBR75pTQaU

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Changed files

• modified lib/openagents/data_rights/export_inventory.ex

Diff

1 file changed, +14 -0

          "what a person did with a plugin is their thread events, which " <>

          "export whole."

    },

    %{

      family: :issue_activity,

      api?: true,

      status: :not_user_data,

      mechanism: nil,

      proof: nil,

      issue: nil,

      note:

        "A derived assembly, not a store: the activity read composes the " <>

          "threads that named the issue with the push, build, target, and " <>

          "deployment receipts reachable from its commit references, and " <>

          "stores nothing of its own. Every record it shows exports through " <>

          "its own family."

    },

    %{

      family: :capacity,

      api?: true,