@songsid/agend 2.1.4-beta.7 → 2.1.4-beta.9

package/dist/fleet-manager.d.ts

@@ -106,6 +106,8 @@ export declare class FleetManager implements FleetContext, LifecycleContext, Arc
     readonly replyDeduper: ReplyDeduper;
     /** instanceName → what it is doing right now, when the backend can tell us. */
     private instanceActivity;
+    /** instanceName → this turn's tool list (multi-line), for the bubble. */
+    private instanceProgress;
     /** instanceName → tail of deliveries waiting for its IPC to come back. */
     private ipcWaitTails;
     /** instanceName → restart currently executing; concurrent callers join it. */
@@ -644,6 +646,26 @@ export declare class FleetManager implements FleetContext, LifecycleContext, Arc
      * never used to decide anything — purely what the user is shown.
      */
     private cacheInstanceActivity;
+    /**
+     * Cache the turn's tool-progress list and push it into the instance's live
+     * bubble, coalesced so a burst of tool events cannot flood the Bot API
+     * (Telegram's flood limit is per-chat across ALL forum topics, so edits are
+     * rate-limited per bubble AND ride behind the daemon-side 3s coalescer).
+     */
+    private cacheInstanceProgress;
+    /** At most one progress-driven edit per bubble per TOOL_PROGRESS_EDIT_MIN_MS. */
+    private scheduleProgressEdit;
+    /**
+     * The ONE composer for the bubble text. Both writers — the elapsed-time
+     * ticker and the tool-progress push — go through here; two independent
+     * renderers editing the same message is how the progress list used to get
+     * wiped by the next elapsed tick (#528 trap 2).
+     */
+    private composeBubbleText;
+    /** Pure composition of header + tool list, exposed for tests. */
+    static bubbleText(elapsedMs: number, activity: string | undefined, minElapsedMs: number, progress: string | undefined): string;
+    /** Recompose and edit the bubble in place; skips when nothing changed. */
+    private refreshBubble;
     /**
      * Refresh the button's text in place while the instance keeps working.
      *
@@ -728,8 +750,45 @@ export declare class FleetManager implements FleetContext, LifecycleContext, Arc
     private static GENERAL_INSTRUCTIONS;
     /** Ensure the general instance has its project instructions file + knowledge */
     private ensureGeneralInstructions;
-    /** Copy general-knowledge steering + skills to the general instance's workspace */
+    /** Resolve the workspace path a backend actually uses before publishing knowledge. */
+    private resolveKnowledgeWorkDir;
+    /**
+     * Where each backend natively loads on-demand skills from, relative to the
+     * workspace. Backends without a native skill mechanism (opencode, grok,
+     * antigravity, gemini-cli) are deliberately absent: dropping files a CLI
+     * never reads is clutter, not capability. Unknown directories are ignored
+     * by older CLI versions, so publishing is fail-open across upgrades.
+     */
+    private static SKILLS_DIR_SEGMENTS;
+    /** Copy general-knowledge steering + all role-eligible skills to General. */
     private syncGeneralKnowledge;
+    /** Publish only the bundled skills eligible for an instance role. */
+    private syncRoleSkills;
+    /**
+     * Steering (always-on rules like core-rules.md). Kiro loads a native
+     * steering directory; every other backend gets the content embedded into
+     * its instructions file (CLAUDE.md / AGENTS.md / …) inside a managed marker
+     * block — the previous behavior dropped bare .md files in the workspace
+     * root, which no CLI ever read. The block is replaced in place on every
+     * sync, so rule updates reach EXISTING workspaces; everything the user
+     * wrote outside the markers is preserved byte-for-byte.
+     */
+    private syncGeneralSteering;
+    private static STEERING_BLOCK_BEGIN;
+    private static STEERING_BLOCK_END;
+    /**
+     * Publish AgEnD's bundled skills into a CLI's native skills directory,
+     * owning ONLY what we published. A manifest records which skill names AgEnD
+     * wrote; a bundled rename/removal deletes the stale managed copy, while a
+     * skill the user created by hand is never listed and therefore never
+     * touched — even if a future bundle happens to reuse its name (the sync
+     * then skips it and logs, rather than overwrite the user's work). The sole
+     * migration exception is the pre-manifest Kiro General layout explicitly
+     * selected by adoptLegacyUnmanaged.
+     */
+    private syncManagedSkills;
+    /** Read AgEnD's roles extension from SKILL.md YAML frontmatter. */
+    private readManagedSkillRoles;
     /** Fetch forum topic icon stickers and pick emoji IDs for each state */
     private resolveTopicIcons;
     /** Set topic icon based on instance state */