You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Decision record: one writer per config-manager object (the skip table of the dedicated kinds) #1346
Part of the tracking issue #1254 (line X5). Maintainer decision (2026-11-16): the one-writer rule becomes a short decision record. WRITE IT AFTER #1259 and #1249 have merged, so that it describes what exists: the shared table skippedForDedicatedKind and its contract test.
The rule
An object of config-manager has ONE writer. When a dedicated kind exists for an agent type (trusted JWT issuers, CIMD profiles, later software publishers and others), the generic file-driven kind oauth2-agents skips entries of that type with one warning per realm and type that names the dedicated command; it never reads, writes or imports an object of that type; exit codes and --allow-failures are unchanged; no user file is modified. Every new kind adds its entry to the table, and a contract test fails when a key of the table has no pull and no push command of that name. The OAuth2 client an application owns is the older instance of the rule (record 0042).
What to do
A short CLI decision record in docs/decisions/ (skill record-a-decision: number after the highest, status proposed, the maintainer accepts it), with the table and the contract test named in applies-to, plus the accepted decisions of #1254 that bind future kinds: a kind per type (model A), all agent types dynamic (not in pull all-static), delete per kind only, wrapped file shape, the password convention of the OAuth2 client issue. Keep it within the repository's limit of 60 lines.
Activity