One-install Honeycomb configuration front door over two bounded domain packs and seventeen non-chat operating workflows. The complete five-pack suite admits all 85 operations across the exact hash-pinned official contract: 71 configuration operations, 11 separately credentialed Management API operations, two separately credentialed JSON ingest operations, and one separately credentialed Kinesis Firehose operation. This front door depends only on the configuration-key leaves, so installing it never asks for bearer management, ingest-only, or Firehose authority. The connection owns X-Honeycomb-Team and defaults to https://api.honeycomb.io; per-organization enrollment may select the documented https://api.eu1.honeycomb.io origin. Reads are uncached and never approval-gated; mutations are grant-off and approval-gated. JSON responses preserve unsafe integers as strings. Batch ingestion intentionally selects documented JSON rather than binary or compressed transport. The official contract does not prove a stable mandatory identity and version for an honest task, note, or project projection, so the suite declares no work-entity Source.