DL-267
Forge subscriptions gain CONTAINER-SCOPE granularity via an explicit ForgeSubscriptionScope enum on SubscribeForgeRequest — Matt’s W2 ruling, option (b); the number = 0 sentinel is REJECTED (proto3 absent-vs-0 blindness would convert a forgotten number from an LLM tool caller into a silent whole-repo subscription). Containers are PROVIDER-NATIVE: GitHub’s container is the REPO (the existing repo slot); Linear’s is a PROJECT, carried in a slot of its own and never overloaded onto the team key in repo — Linear project scope is thereby IN scope (promoted from deferral). The project identifier lives in a dedicated column (OQ-1, ruled (i): additive scope + project columns, UNIQUE widened). A container subscription delivers exactly FORGE_NOTIFICATION_KIND_OPENED with the new artifact’s number/url — never a fan-in of every event on every artifact. Two additive ForgeNotificationKind values land with it: REVIEW = 5 (submitted PR review; free on webhooks where the poll design priced no review endpoint) and OPENED = 6.
Status: Active (Matt, 2026-08-26)