@integrity-labs/agt-cli 0.28.805 → 0.28.807

package/dist/{chunk-2FL6V4E5.js → chunk-VK35F6O7.js}

@@ -5661,6 +5661,38 @@ var FLAG_REGISTRY = [
     // envVar — this is a net-new control with no pre-flags env gate to migrate.
     defaultValue: false
   },
+  {
+    key: "skill-dreaming-support-intake",
+    description: "Route skill dreaming's GLOBAL-scope proposals into Integrity Labs' own support-intake Linear workspace (ENG-9926). 42% of dreaming output targets a global skill no product surface can change, so those drafts can only ever become an agent-scoped fork that never reaches the thing it improves \u2014 the improvement is therefore ALSO filed as a support-intake issue, deduped per target skill with one Linear customer need per requesting org. Boolean gate; ships dark \u2014 when off nothing is filed and the fork behaviour is exactly today's.",
+    flagType: "boolean",
+    // Arming this starts exporting customer-derived text to a third-party tracker, so it
+    // takes the ADR-0022 §4 explicit-confirmation step rather than a single unguarded
+    // write — matching every comparable export gate in this file
+    // (`org-email-domain-derivation`, `kanban-push-status`,
+    // `augmented-support-auto-provision`, `email-guard-enforce-enabled`).
+    // (CodeRabbit, PR #5519: the first cut documented the risk in the comment below and
+    // then omitted the marker that acts on it.)
+    sensitive: true,
+    // THIS GATES A DATA CROSSING, NOT A COST. Read that before arming it.
+    //
+    // Everything skill dreaming does today stays inside the control plane: it reads
+    // `agent_memories` and writes a `skill_definitions` row in the same Postgres, same
+    // org, same RLS. This flag is what sends LLM-written rationale, confidence, and the
+    // verbatim NAMES of the memories that motivated a proposal OUT to Linear — and
+    // `feature-request-intake.ts` already calls Linear "the third-party tracker" where it
+    // refuses to export a requester's contact details there. Via
+    // linkFeatureRequestCustomerNeed it also sends the org's verified email domains.
+    //
+    // That is strictly more than ADR-0052 §6 gated for PostHog, and ENG-8247 is the
+    // precedent for why a credential must not BE the gate: holding a support-intake key
+    // is not the same as being cleared to send customer-derived text to a vendor's
+    // tracker. Hence a separate flag rather than leaning on isFeatureIntakeConfigured.
+    //
+    // Declared safe value is `false` (nothing filed). Fail-safe direction: a flag-DB read
+    // error must never start exporting on its own. No envVar — net-new control with no
+    // pre-flags env gate to migrate (ADR-0022).
+    defaultValue: false
+  },
   {
     key: "skill-draft-review-notify",
     description: "Pending skill-draft review nudge (ENG-6505): when a skill lands as a status=draft awaiting operator review, send a low-severity informational notification to the right reviewer(s) by scope \u2014 agent-scoped \u2192 the agent's manager (reports_to_person), falling back to team owners/admins; team-scoped \u2192 team owners/admins; org-scoped \u2192 org owners/admins \u2014 with a deep link to the Pending Skills card. Distinct from (and never doubles up on) the HIGH+ SkillSpector security alert. Covers both the agent-authored (ENG-4589) and skill-dreaming (ENG-6500) draft paths. Boolean gate; ships dark \u2014 when off no nudge is sent, so the steady state until an org is armed is silence.",
@@ -6009,6 +6041,26 @@ var FLAG_REGISTRY = [
     // env var is retired.
     envVar: "AUGMENTED_CONNECTIVITY_ESCALATION_ENABLED"
   },
+  {
+    key: "slack-manifest-remediate",
+    description: "Let the Slack manifest drift monitor PUSH, not just alert (ENG-9963). updateSlackManifest had exactly one caller \u2014 a console button \u2014 so nothing but a human click ever pushed a manifest; ENG-7762 changed the generator with no rollout mechanism and 26 agents went 53 days with no working per-agent slash commands. When on, the daily drift cron pushes the generated manifest for a drifted agent. When off it alerts exactly as before. NOTE what arming this authorises: a push REPLACES a customer-owned Slack app's entire manifest, so the cron only ever pushes drift whose diffs are purely additive (isSafelyRemediable) \u2014 an app with live-only entries a push would destroy is declined and left for a human. Boolean gate; ships dark.",
+    flagType: "boolean",
+    // Declared safe value is `false` (alert-only), matching the cron's compiled
+    // default. The fail-safe direction is the opposite of a paging gate's and
+    // matters more: a flag-DB read error must never authorise a WRITE to a
+    // customer's Slack app.
+    defaultValue: false,
+    // Operator override, same precedence and vocabulary as the connectivity
+    // escalation gate above, so an operator who knows one knows both.
+    envVar: "AUGMENTED_SLACK_MANIFEST_REMEDIATE_ENABLED",
+    // ADR-0022 §4. NOTE this is where it diverges from the connectivity gate it
+    // otherwise mirrors, and the divergence is the point: arming THAT one only
+    // causes alerts to open, while arming THIS one authorises a cron to REPLACE
+    // manifests on customer-owned Slack apps. That is precisely the class the
+    // sensitive marker exists for — a control whose relaxation should not be one
+    // unguarded write away.
+    sensitive: true
+  },
   {
     key: "integration-reauth-reminders",
     description: "Re-notify an integration that stays in needs_reauth (ENG-8370). Failure notification is at-most-once PER TRANSITION, so an integration nobody repairs is announced once and then silent forever - prod carried a row failing every 30-minute tick for ~21 days on a single day-one notification. When on, the IntegrationReauthReminder cron re-fires the existing reconnect notification on a backoff measured from failure ONSET (+1d, +3d, +7d, then weekly), skipping rows an operator has muted. When off the cron still scans and logs what it WOULD have sent, so the volume can be sized before anyone is messaged. Boolean gate; ships dark.",
@@ -13655,4 +13707,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-2FL6V4E5.js.map
+//# sourceMappingURL=chunk-VK35F6O7.js.map