Miro Redacted Debug Bundle

Overview

Create evidence useful to maintainers or Miro support while excluding credentials, authorization codes, board content, personal data, and unrestricted configuration; use the evidence produced here to make the next decision explicit and reviewable.

Prerequisites

• Incident identifier and narrow UTC window
• Approved evidence destination and retention period
• Known redaction rules for identifiers, URLs, headers, and payloads

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, configuration names, adapters, tests, and evidence. Use WebFetch only for current official Miro documentation. Use Write or Edit after confirming the requested mode, target environment, tenant, board, and approval boundary. These declared tools do not call authenticated Miro APIs or deployment CLIs; implement client, configuration, and test changes, then return exact operator commands or an approval-gated handoff for live execution.

Current Contract

• Safe evidence includes versions, operation names, status/code, latency, rate headers, counts, hashes, and timestamps.
• Authorization headers, cookies, tokens, client secrets, callback query strings, and raw board payloads are never safe evidence.
• Access-token context is useful only after user/team identifiers are pseudonymized.
• Official status evidence should include observation time because incidents change.

Authentication

For REST work, use OAuth 2.0 Authorization Code with the narrowest Miro scopes. Bind each encrypted token record to its user, application, authorized team, and granted scopes. Never print access tokens, refresh tokens, client secrets, authorization codes, or board content.

Instructions

1. Define the incident window, failing operations, recipient, purpose, and retention.
2. Collect repository version, deployment version, app mode, safe configuration names, and dependency lock facts.
3. Extract bounded request metadata and rate headers; replace identifiers with stable incident-local hashes.
4. Record token-context match as a boolean and include no credential or raw context response.
5. Scan the bundle for bearer patterns, secrets, emails, callback codes, board text, and private URLs.
6. Review the manifest and redaction report before writing the approved artifact.

Approval Boundaries

Do not collect raw payloads, full environment/configuration dumps, database exports, or user content without data-owner and security approval. Pause when the responsible owner or exact target is uncertain.

Output

Return bundle path, manifest, time window, redaction counts, evidence gaps, sensitivity label, recipient, and deletion date. State what was not inspected or changed so the receipt cannot overclaim coverage.

Error Handling

Examples

The example is a redacted operator receipt; identifiers are hashes or bounded labels, not board content or credentials.

incident=INC-204; window=18m; requests=14; ids-hashed=9; secrets-found=0; content-fields=0; retention=7d

Resources

• Skill-specific official documentation
• Security guidelines
• Rate limiting