file-issuelisted

# File Issue Capture an idea or bug as a GitHub issue for later triage. ## HIGH PRIORITY: Sanitize before filing GitHub issues are world-readable on public repos and broadly accessible on private ones. Before calling `issue-create`, scrub the title and body of: - **PII**: names, email addresses, phone numbers, usernames tied to real identities, home addresses - **Secrets**: API keys, tokens, passwords, private URLs with credentials, `.env` snippets, signing keys, session cookies - **Company / employer names**: do not name the user's employer, clients, vendors, or internal team names. Use generic terms ("$company", "the service", "an upstream provider") - **Infrastructure details**: internal hostnames, IP addresses, cluster names, datacenter identifiers, internal tool names, internal URLs, ticket IDs from non-public trackers, Slack channel names If a reproduction genuinely requires one of these, redact it (`<redacted>`, `$COMPANY`, `<internal-host>`) and note that the real value lives outside the issue. When in doubt, leave it out --- a future-triage agent can ask. ## Steps 1. **Create the issue** using `get-hubbed issue-create` with the provided title 2. **Body** --- include enough context for a future agent to act on it: - For bugs: steps to reproduce and/or a code snippet that could be used to write a failing test proving the incorrect behavior. Include an **Environment** line pinning the affected tool's version/commit (e.g. `piggy