@kivimedia/kmhub 2.9.1 → 2.11.0

package/tools/strategy.mjs

@@ -1,146 +1,146 @@
-/**
- * Tool family: strategy - the officers, what they proposed, and what was done.
- *
- * Workstream B6. Strategy was 2 of 8: the pillar that makes "a COO and beyond"
- * true rather than aspirational had almost no terminal reach. A connector that
- * reads the pipeline but cannot see the decisions waiting on the owner, or what was
- * already done in their name, is a reporting tool rather than an operator.
- *
- *   km_list_decisions        -> GET /strategy/decisions
- *   km_list_ai_officers      -> GET /strategy/officers
- *   km_list_recommendations  -> GET /strategy/advice
- *   km_list_ai_activity      -> GET /strategy/activity
- *   km_list_weekly_interviews-> GET /strategy/interviews
- *
- * 🚨 READ ONLY, and approval especially so. Approving a COO proposal executes real
- * work against real records: it is the most consequential button in the product and
- * it deserves its own decision when B8 settles write scope, not to inherit a general
- * one. Never imply you can approve something.
- *
- * The family contract this file follows is documented in ./README.md.
- */
-import { z } from 'zod';
-
-export const FAMILY = 'strategy';
-
-export const TOOLS = [
-  'km_list_decisions',
-  'km_list_ai_officers',
-  'km_list_recommendations',
-  'km_list_ai_activity',
-  'km_list_weekly_interviews',
-];
-
-export const PROFILES = ['*'];
-
-function routeMissing(r) {
-  return r.status === 404 || r.status === 405 || r.status === 501;
-}
-
-const NOT_SUPPORTED =
-  'Your KM Hub does not expose the AI Team surface to the terminal yet. That is not a fault: the workspace is fine ' +
-  'and every other tool works as normal. The officers, decisions and activity log are all there in the web app at ' +
-  'https://hub.kivimedia.co, and this connector will start reading them once your KM Hub is on a build that publishes them.';
-
-export function register(server, call, { out, text, qs }) {
-  server.tool(
-    'km_list_decisions',
-    'The proposals the COO has put up for a human decision, what each one would actually DO, and how long it has been ' +
-      'waiting. ' +
-      'Call this whenever the user asks what needs them, what is outstanding, or what the AI has suggested, and any time ' +
-      'you are summarising the state of the business. A decision sitting unmade is different from a task not done: ' +
-      'nothing moves until somebody says yes, and the workspace will not chase them for it. ' +
-      '🚨 Lead with `waiting_on_you` and `oldest_waiting_days`. A proposal that has been pending for weeks is usually one ' +
-      'the owner never saw rather than one they decided against, and saying the number out loud is the whole value here. ' +
-      'Read `risk` and `what_it_would_do` before describing anything: they are not all equivalent, and a high-risk ' +
-      'proposal deserves to be presented as one. ' +
-      'Nothing here can approve or reject. That happens in KM Hub, deliberately, because approval executes real work. ' +
-      'Read only.',
-    {
-      status: z
-        .enum(['pending', 'approved', 'rejected', 'executed', 'failed', 'expired'])
-        .optional()
-        .describe('Narrow to one state. "pending" is what is waiting on a person, which is usually the real question.'),
-      limit: z.number().int().min(1).max(100).optional().describe('How many, newest first. Default 30.'),
-    },
-    async ({ status, limit }) => {
-      const r = await call('GET', `/strategy/decisions${qs({ status, limit })}`);
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_ai_officers',
-    'Which AI officers this workspace has customised: their key, the name the owner gave them and the personality they ' +
-      'were given. Use it when the user refers to an officer by name and you do not recognise it, or asks who is on ' +
-      'their AI team. An empty list is normal and means they are running the defaults, not that something is missing. ' +
-      'Useful mainly so you address an officer the way the workspace does rather than inventing your own label. Read only.',
-    {},
-    async () => {
-      const r = await call('GET', '/strategy/officers');
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_recommendations',
-    'Standing recommendations and insights the workspace has generated for itself, each with its category, impact and ' +
-      'effort where they were recorded. ' +
-      'Use it when the user asks what they should be doing, or before you offer advice of your own: the workspace may ' +
-      'already have said the same thing, and repeating it as though it were new is worse than agreeing with it. ' +
-      '🚨 These are suggestions, not instructions, and some will be stale. Weigh them against what the owner has actually ' +
-      'said they want, and check the date before presenting one as current. Read only.',
-    {
-      limit: z.number().int().min(1).max(100).optional().describe('How many of each, newest or highest priority first. Default 25.'),
-    },
-    async ({ limit }) => {
-      const r = await call('GET', `/strategy/advice${qs({ limit })}`);
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_ai_activity',
-    'What has actually been done in this workspace and by which surface: the app, a worker, a cron, the API or this ' +
-      'terminal. Each entry names the action, the record it touched, and whether it was later UNDONE. ' +
-      'Use it when the user asks what changed, who did something, or whether the AI has been acting on its own. It is ' +
-      'also the right call before you claim nothing has happened: a quiet inbox does not mean a quiet workspace. ' +
-      '🚨 `undone_count` is the honest number and it must not be skipped to look competent. A pattern of undos says ' +
-      'something real about how far a particular automation should be trusted, and the owner is better served knowing it. ' +
-      'Undo itself lives in KM Hub. Read only.',
-    {
-      source: z
-        .string()
-        .optional()
-        .describe('Narrow to one surface, for example app, worker, cron, api or desk. Leave it out for everything.'),
-      limit: z.number().int().min(1).max(200).optional().describe('How many entries, newest first. Default 40.'),
-    },
-    async ({ source, limit }) => {
-      const r = await call('GET', `/strategy/activity${qs({ source, limit })}`);
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_weekly_interviews',
-    'The weekly interview sessions: which week, who, what topics were covered, the digest of what the session concluded ' +
-      'and what it wants to ask about next. ' +
-      'Use it when the user mentions their weekly check-in or sit-down, or when you want to know what has recently been ' +
-      'learned about how this business is running. The digests are one of the richest sources of context in the ' +
-      'workspace and almost nothing else reads them. ' +
-      'Full transcripts are deliberately not returned: they are long, and the digest is the part that carries the ' +
-      'conclusion. Read only.',
-    {
-      limit: z.number().int().min(1).max(60).optional().describe('How many sessions, most recent week first. Default 15.'),
-    },
-    async ({ limit }) => {
-      const r = await call('GET', `/strategy/interviews${qs({ limit })}`);
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-}
+/**
+ * Tool family: strategy - the officers, what they proposed, and what was done.
+ *
+ * Workstream B6. Strategy was 2 of 8: the pillar that makes "a COO and beyond"
+ * true rather than aspirational had almost no terminal reach. A connector that
+ * reads the pipeline but cannot see the decisions waiting on the owner, or what was
+ * already done in their name, is a reporting tool rather than an operator.
+ *
+ *   km_list_decisions        -> GET /strategy/decisions
+ *   km_list_ai_officers      -> GET /strategy/officers
+ *   km_list_recommendations  -> GET /strategy/advice
+ *   km_list_ai_activity      -> GET /strategy/activity
+ *   km_list_weekly_interviews-> GET /strategy/interviews
+ *
+ * 🚨 READ ONLY, and approval especially so. Approving a COO proposal executes real
+ * work against real records: it is the most consequential button in the product and
+ * it deserves its own decision when B8 settles write scope, not to inherit a general
+ * one. Never imply you can approve something.
+ *
+ * The family contract this file follows is documented in ./README.md.
+ */
+import { z } from 'zod';
+
+export const FAMILY = 'strategy';
+
+export const TOOLS = [
+  'km_list_decisions',
+  'km_list_ai_officers',
+  'km_list_recommendations',
+  'km_list_ai_activity',
+  'km_list_weekly_interviews',
+];
+
+export const PROFILES = ['*'];
+
+function routeMissing(r) {
+  return r.status === 404 || r.status === 405 || r.status === 501;
+}
+
+const NOT_SUPPORTED =
+  'Your KM Hub does not expose the AI Team surface to the terminal yet. That is not a fault: the workspace is fine ' +
+  'and every other tool works as normal. The officers, decisions and activity log are all there in the web app at ' +
+  'https://hub.kivimedia.co, and this connector will start reading them once your KM Hub is on a build that publishes them.';
+
+export function register(server, call, { out, text, qs }) {
+  server.tool(
+    'km_list_decisions',
+    'The proposals the COO has put up for a human decision, what each one would actually DO, and how long it has been ' +
+      'waiting. ' +
+      'Call this whenever the user asks what needs them, what is outstanding, or what the AI has suggested, and any time ' +
+      'you are summarising the state of the business. A decision sitting unmade is different from a task not done: ' +
+      'nothing moves until somebody says yes, and the workspace will not chase them for it. ' +
+      '🚨 Lead with `waiting_on_you` and `oldest_waiting_days`. A proposal that has been pending for weeks is usually one ' +
+      'the owner never saw rather than one they decided against, and saying the number out loud is the whole value here. ' +
+      'Read `risk` and `what_it_would_do` before describing anything: they are not all equivalent, and a high-risk ' +
+      'proposal deserves to be presented as one. ' +
+      'Nothing here can approve or reject. That happens in KM Hub, deliberately, because approval executes real work. ' +
+      'Read only.',
+    {
+      status: z
+        .enum(['pending', 'approved', 'rejected', 'executed', 'failed', 'expired'])
+        .optional()
+        .describe('Narrow to one state. "pending" is what is waiting on a person, which is usually the real question.'),
+      limit: z.number().int().min(1).max(100).optional().describe('How many, newest first. Default 30.'),
+    },
+    async ({ status, limit }) => {
+      const r = await call('GET', `/strategy/decisions${qs({ status, limit })}`);
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_ai_officers',
+    'Which AI officers this workspace has customised: their key, the name the owner gave them and the personality they ' +
+      'were given. Use it when the user refers to an officer by name and you do not recognise it, or asks who is on ' +
+      'their AI team. An empty list is normal and means they are running the defaults, not that something is missing. ' +
+      'Useful mainly so you address an officer the way the workspace does rather than inventing your own label. Read only.',
+    {},
+    async () => {
+      const r = await call('GET', '/strategy/officers');
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_recommendations',
+    'Standing recommendations and insights the workspace has generated for itself, each with its category, impact and ' +
+      'effort where they were recorded. ' +
+      'Use it when the user asks what they should be doing, or before you offer advice of your own: the workspace may ' +
+      'already have said the same thing, and repeating it as though it were new is worse than agreeing with it. ' +
+      '🚨 These are suggestions, not instructions, and some will be stale. Weigh them against what the owner has actually ' +
+      'said they want, and check the date before presenting one as current. Read only.',
+    {
+      limit: z.number().int().min(1).max(100).optional().describe('How many of each, newest or highest priority first. Default 25.'),
+    },
+    async ({ limit }) => {
+      const r = await call('GET', `/strategy/advice${qs({ limit })}`);
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_ai_activity',
+    'What has actually been done in this workspace and by which surface: the app, a worker, a cron, the API or this ' +
+      'terminal. Each entry names the action, the record it touched, and whether it was later UNDONE. ' +
+      'Use it when the user asks what changed, who did something, or whether the AI has been acting on its own. It is ' +
+      'also the right call before you claim nothing has happened: a quiet inbox does not mean a quiet workspace. ' +
+      '🚨 `undone_count` is the honest number and it must not be skipped to look competent. A pattern of undos says ' +
+      'something real about how far a particular automation should be trusted, and the owner is better served knowing it. ' +
+      'Undo itself lives in KM Hub. Read only.',
+    {
+      source: z
+        .string()
+        .optional()
+        .describe('Narrow to one surface, for example app, worker, cron, api or desk. Leave it out for everything.'),
+      limit: z.number().int().min(1).max(200).optional().describe('How many entries, newest first. Default 40.'),
+    },
+    async ({ source, limit }) => {
+      const r = await call('GET', `/strategy/activity${qs({ source, limit })}`);
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_weekly_interviews',
+    'The weekly interview sessions: which week, who, what topics were covered, the digest of what the session concluded ' +
+      'and what it wants to ask about next. ' +
+      'Use it when the user mentions their weekly check-in or sit-down, or when you want to know what has recently been ' +
+      'learned about how this business is running. The digests are one of the richest sources of context in the ' +
+      'workspace and almost nothing else reads them. ' +
+      'Full transcripts are deliberately not returned: they are long, and the digest is the part that carries the ' +
+      'conclusion. Read only.',
+    {
+      limit: z.number().int().min(1).max(60).optional().describe('How many sessions, most recent week first. Default 15.'),
+    },
+    async ({ limit }) => {
+      const r = await call('GET', `/strategy/interviews${qs({ limit })}`);
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+}

package/tools/studio.mjs

@@ -1,132 +1,132 @@
-/**
- * Tool family: studio - what the creation surfaces have actually produced.
- *
- * The last seven pages. I argued these could not be closed by reading, on the
- * grounds that a studio is a place you make things rather than a place with state.
- * That was wrong. A studio has OUTPUT, and the output is exactly what an owner
- * wants to know about: what has been made, what is waiting on them, what is
- * scheduled to go out.
- *
- *   km_list_design_assets    -> GET /studio/assets
- *   km_list_galleries        -> GET /studio/galleries
- *   km_list_linkedin_content -> GET /studio/linkedin
- *   km_list_balloon_work     -> GET /studio/balloon
- *   km_review_queue          -> GET /studio/review
- *
- * 🚨 READ ONLY. Generating an image or a post spends money with a provider, and
- * approving one publishes in the client's name.
- *
- * The family contract this file follows is documented in ./README.md.
- */
-import { z } from 'zod';
-
-export const FAMILY = 'studio';
-
-export const TOOLS = [
-  'km_list_design_assets',
-  'km_list_galleries',
-  'km_list_linkedin_content',
-  'km_list_balloon_work',
-  'km_review_queue',
-];
-
-export const PROFILES = ['content', 'outreach'];
-
-function routeMissing(r) {
-  return r.status === 404 || r.status === 405 || r.status === 501;
-}
-
-const NOT_SUPPORTED =
-  'Your KM Hub does not expose the studios to the terminal yet. That is not a fault: the workspace is fine and every ' +
-  'other tool works as normal. They are there in the web app at https://hub.kivimedia.co.';
-
-export function register(server, call, { out, text, qs }) {
-  server.tool(
-    'km_review_queue',
-    'EVERYTHING across the whole product that is waiting on a human: outreach drafts, SEO posts, LinkedIn posts, COO ' +
-      'proposals and proposed business facts, each with a count and how old the oldest one is. ' +
-      'Call this in any catch-up, any status question, and before telling somebody they are on top of things. ' +
-      '🚨 No single page in KM Hub shows all of this, because every surface owns its own queue. Approval queues are ' +
-      'where work goes to die quietly: nothing sends until a person releases it, nothing chases them, and the owner ' +
-      'usually finds out when a client asks why they never heard back. ' +
-      '🚨 LEAD WITH THE OLDEST, NOT THE LARGEST. Forty drafts written this morning are fine. One draft that has been ' +
-      'waiting six weeks is a client who was ignored. Read only.',
-    {},
-    async () => {
-      const r = await call('GET', '/studio/review');
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_design_assets',
-    'Images and design assets the studios have generated, with the template and provider behind each and a link to the ' +
-      'file. ' +
-      'Use it when the user asks what has been made, wants something to reuse, or before generating anything new: ' +
-      'regenerating something that already exists spends money twice for the same picture. ' +
-      'The prompt and inputs are not returned, because they are long and what a person wants is what exists and where. ' +
-      'Read only.',
-    {
-      limit: z.number().int().min(1).max(200).optional().describe('How many assets, newest first. Default 40.'),
-    },
-    async ({ limit }) => {
-      const r = await call('GET', `/studio/assets${qs({ limit })}`);
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_galleries',
-    'The galleries this business publishes, whether each is active, and how many items are in them. ' +
-      '🚨 An ACTIVE gallery with no active items is a public page showing nothing, which is worse than not having one ' +
-      'at all, and nobody notices because the page still loads. That combination is worth raising unprompted. ' +
-      'Use it before advising anything about what buyers see before they enquire. Building a gallery happens in KM Hub. ' +
-      '🚨 These are the PUBLIC gallery pages on the website, and they have nothing to do with the photos that ride inside ' +
-      'an outreach email. If the question is about pictures in an email, this is the wrong tool and an empty answer here ' +
-      'means nothing: use km_list_work_photos and km_attach_draft_photos. ' +
-      'Read only.',
-    {},
-    async () => {
-      const r = await call('GET', '/studio/galleries');
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_linkedin_content',
-    'LinkedIn posts the workspace has produced: the hook archetype each uses, its status, when it is scheduled, and a ' +
-      'preview of the body. ' +
-      'Use it when the user asks about their LinkedIn presence, what is going out, or what is waiting on them. ' +
-      '🚨 Read `by_hook`. A workspace using one hook archetype for everything becomes predictable, and predictable is ' +
-      'invisible on LinkedIn. That is a more useful observation than the post count. `awaiting_approval` is the other ' +
-      'number worth naming: those are written and going nowhere. Publishing happens in KM Hub. Read only.',
-    {
-      limit: z.number().int().min(1).max(200).optional().describe('How many posts, newest first. Default 40.'),
-    },
-    async ({ limit }) => {
-      const r = await call('GET', `/studio/linkedin${qs({ limit })}`);
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-
-  server.tool(
-    'km_list_balloon_work',
-    'Balloon designs and the render runs behind them: the event, the guest count, the status, and whether each design ' +
-      'ever reached a proposal. ' +
-      '🚨 `designs_on_a_proposal` against the design count is the number that matters. A design that never reached a ' +
-      'proposal is work that was done and never sold, and that gap is invisible on any single screen. ' +
-      'Rendering costs money with an image provider and happens in KM Hub. Read only.',
-    {
-      limit: z.number().int().min(1).max(100).optional().describe('How many designs and runs, newest first. Default 30.'),
-    },
-    async ({ limit }) => {
-      const r = await call('GET', `/studio/balloon${qs({ limit })}`);
-      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
-      return out(r);
-    },
-  );
-}
+/**
+ * Tool family: studio - what the creation surfaces have actually produced.
+ *
+ * The last seven pages. I argued these could not be closed by reading, on the
+ * grounds that a studio is a place you make things rather than a place with state.
+ * That was wrong. A studio has OUTPUT, and the output is exactly what an owner
+ * wants to know about: what has been made, what is waiting on them, what is
+ * scheduled to go out.
+ *
+ *   km_list_design_assets    -> GET /studio/assets
+ *   km_list_galleries        -> GET /studio/galleries
+ *   km_list_linkedin_content -> GET /studio/linkedin
+ *   km_list_balloon_work     -> GET /studio/balloon
+ *   km_review_queue          -> GET /studio/review
+ *
+ * 🚨 READ ONLY. Generating an image or a post spends money with a provider, and
+ * approving one publishes in the client's name.
+ *
+ * The family contract this file follows is documented in ./README.md.
+ */
+import { z } from 'zod';
+
+export const FAMILY = 'studio';
+
+export const TOOLS = [
+  'km_list_design_assets',
+  'km_list_galleries',
+  'km_list_linkedin_content',
+  'km_list_balloon_work',
+  'km_review_queue',
+];
+
+export const PROFILES = ['content', 'outreach'];
+
+function routeMissing(r) {
+  return r.status === 404 || r.status === 405 || r.status === 501;
+}
+
+const NOT_SUPPORTED =
+  'Your KM Hub does not expose the studios to the terminal yet. That is not a fault: the workspace is fine and every ' +
+  'other tool works as normal. They are there in the web app at https://hub.kivimedia.co.';
+
+export function register(server, call, { out, text, qs }) {
+  server.tool(
+    'km_review_queue',
+    'EVERYTHING across the whole product that is waiting on a human: outreach drafts, SEO posts, LinkedIn posts, COO ' +
+      'proposals and proposed business facts, each with a count and how old the oldest one is. ' +
+      'Call this in any catch-up, any status question, and before telling somebody they are on top of things. ' +
+      '🚨 No single page in KM Hub shows all of this, because every surface owns its own queue. Approval queues are ' +
+      'where work goes to die quietly: nothing sends until a person releases it, nothing chases them, and the owner ' +
+      'usually finds out when a client asks why they never heard back. ' +
+      '🚨 LEAD WITH THE OLDEST, NOT THE LARGEST. Forty drafts written this morning are fine. One draft that has been ' +
+      'waiting six weeks is a client who was ignored. Read only.',
+    {},
+    async () => {
+      const r = await call('GET', '/studio/review');
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_design_assets',
+    'Images and design assets the studios have generated, with the template and provider behind each and a link to the ' +
+      'file. ' +
+      'Use it when the user asks what has been made, wants something to reuse, or before generating anything new: ' +
+      'regenerating something that already exists spends money twice for the same picture. ' +
+      'The prompt and inputs are not returned, because they are long and what a person wants is what exists and where. ' +
+      'Read only.',
+    {
+      limit: z.number().int().min(1).max(200).optional().describe('How many assets, newest first. Default 40.'),
+    },
+    async ({ limit }) => {
+      const r = await call('GET', `/studio/assets${qs({ limit })}`);
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_galleries',
+    'The galleries this business publishes, whether each is active, and how many items are in them. ' +
+      '🚨 An ACTIVE gallery with no active items is a public page showing nothing, which is worse than not having one ' +
+      'at all, and nobody notices because the page still loads. That combination is worth raising unprompted. ' +
+      'Use it before advising anything about what buyers see before they enquire. Building a gallery happens in KM Hub. ' +
+      '🚨 These are the PUBLIC gallery pages on the website, and they have nothing to do with the photos that ride inside ' +
+      'an outreach email. If the question is about pictures in an email, this is the wrong tool and an empty answer here ' +
+      'means nothing: use km_list_work_photos and km_attach_draft_photos. ' +
+      'Read only.',
+    {},
+    async () => {
+      const r = await call('GET', '/studio/galleries');
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_linkedin_content',
+    'LinkedIn posts the workspace has produced: the hook archetype each uses, its status, when it is scheduled, and a ' +
+      'preview of the body. ' +
+      'Use it when the user asks about their LinkedIn presence, what is going out, or what is waiting on them. ' +
+      '🚨 Read `by_hook`. A workspace using one hook archetype for everything becomes predictable, and predictable is ' +
+      'invisible on LinkedIn. That is a more useful observation than the post count. `awaiting_approval` is the other ' +
+      'number worth naming: those are written and going nowhere. Publishing happens in KM Hub. Read only.',
+    {
+      limit: z.number().int().min(1).max(200).optional().describe('How many posts, newest first. Default 40.'),
+    },
+    async ({ limit }) => {
+      const r = await call('GET', `/studio/linkedin${qs({ limit })}`);
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+
+  server.tool(
+    'km_list_balloon_work',
+    'Balloon designs and the render runs behind them: the event, the guest count, the status, and whether each design ' +
+      'ever reached a proposal. ' +
+      '🚨 `designs_on_a_proposal` against the design count is the number that matters. A design that never reached a ' +
+      'proposal is work that was done and never sold, and that gap is invisible on any single screen. ' +
+      'Rendering costs money with an image provider and happens in KM Hub. Read only.',
+    {
+      limit: z.number().int().min(1).max(100).optional().describe('How many designs and runs, newest first. Default 30.'),
+    },
+    async ({ limit }) => {
+      const r = await call('GET', `/studio/balloon${qs({ limit })}`);
+      if (routeMissing(r)) return text(NOT_SUPPORTED, true);
+      return out(r);
+    },
+  );
+}