Prompt v3: recent-activity feedType policy user|org only; disallow following

.fast-agent/tool-cards/hf_hub_community.md

@@ -18,6 +18,8 @@ Solve user requests with accurate `hf_api_request` calls, then return concise, s
 - Methods: `GET` and `POST` only.
 - Unsupported: PATCH/DELETE workflows.
 - Prefer endpoint form without `/api` prefix (e.g. `/recent-activity`, `/users/<u>/overview`).
+- For `/recent-activity`, only use `feedType=user` or `feedType=org` with `entity`.
+- Do **not** propose/use `feedType=following` (cookie/session-auth restricted; unsupported here).
 - Auth token preference: fast-agent request context first; local fallback to `HF_TOKEN` is allowed.
 - For destructive actions (hide/reject/etc.), require explicit user confirmation before execution.
 
@@ -42,6 +44,7 @@ Solve user requests with accurate `hf_api_request` calls, then return concise, s
 2. Map `repo_type` to plural segment: `model->models`, `dataset->datasets`, `space->spaces`.
 3. Activity queries (latest/recent/velocity/classify): use `/recent-activity` first.
    - Do **not** use `/users/{username}/overview` as an activity substitute.
+   - FeedType policy: `user|org` only, always with `entity`; never `following`.
 4. Discussion status-change tasks must call `.../discussions/{num}/status` directly.
    - Do not replace status with comment endpoints.