tokens-for-good 0.4.7 → 0.4.8

package/README.md

@@ -13,7 +13,7 @@ Works with Claude Code, OpenCode, Cursor, Windsurf, Devin, and Qwen Code as an M
    npx tokens-for-good init
    ```
 
-   init is interactive: it asks for your API key, the cadence you want (daily / weekly / hourly / one-off), and then writes everything — MCP config, SessionStart hook, `/tfg` and `/tfg-schedule` skills, and your preference — in one shot.
+   init is interactive: it asks for your API key, the cadence you want (daily, with a chosen number of runs per day / weekly / one-off), and then writes everything — MCP config, SessionStart hook, `/tfg` and `/tfg-schedule` skills, and your preference — in one shot.
 
 3. **Open your AI coding tool.** Your first session acts on the cadence you picked automatically:
    - Scheduled → it sets up `/schedule` via the `/tfg-schedule` skill.
@@ -23,7 +23,7 @@ To change cadence later, run `npx tokens-for-good init` again.
 
 ## What happens during research
 
-Each org takes ~5 minutes and ~$0.20 in tokens:
+Each org takes about 5 minutes:
 
 1. **Research** — web search + 6-prompt methodology, scored checklist (100 pts)
 2. **Verify** — every citation URL checked, hallucinations flagged and corrected

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tokens-for-good",
-  "version": "0.4.7",
+  "version": "0.4.8",
   "type": "module",
   "description": "Donate your spare AI tokens to research nonprofits for Fierce Philanthropy",
   "homepage": "https://tokensforgood.ai",

package/skills/tfg-schedule.md

@@ -1,36 +1,45 @@
----
-name: tfg-schedule
-description: Set up automated Tokens for Good research on a schedule (hourly, daily, or weekly). Use this when the user wants their AI to donate spare tokens to nonprofit research without manual prompting — it wires up a recurring /schedule agent in one shot instead of making them run /schedule, pick a frequency, and paste a prompt by hand.
----
-
-The user wants to automate Tokens for Good research on a recurring schedule.
-
-## What to do
-
-1. **Read the user's chosen frequency.** If the user invoked you without specifying one, default to `daily`. Otherwise use what they said (`hourly`, `daily`, `weekly`).
-
-2. **Call the TFG MCP `setup_automation` tool** with that frequency. It returns the full `/schedule` setup text, including a research prompt scoped to that user's API key.
-
-3. **Extract the research prompt.** The returned text contains a block delimited by `---` lines — that block is the exact task description `/schedule` needs. Don't paraphrase it; pass it through verbatim.
-
-4. **Invoke the `/schedule` skill** to create the recurring trigger:
-   - Frequency: the value from step 1
-   - Task description: the verbatim block from step 3
-
-5. **Wait for `/schedule` to confirm success.** If it fails or the user cancels, stop here and tell the user — do NOT call `mark_setup_complete`.
-
-6. **On success, call the TFG MCP `mark_setup_complete` tool.** This flips the user's local state so the SessionStart hook stops nudging.
-
-7. **Confirm to the user** in one sentence: *"Scheduled ✓ — your spare tokens will research a nonprofit every `<frequency>` from here on. You can change this anytime with /schedule."*
-
-## If something goes wrong
-
-- **`setup_automation` returned an error about a missing API key** → tell the user to run `npx tokens-for-good init` in their terminal and re-open Claude Code.
-- **`/schedule` skill not available** → the user's Claude Code version may be too old; direct them to update.
-- **User declines the /schedule confirmation** → don't call `mark_setup_complete`. The hook will offer again next session.
-
-## What not to do
-
-- Don't ask the user to confirm the frequency again if they already picked one at install — they're done making that decision.
-- Don't print the raw research prompt to the user; it's verbose and already flows through /schedule.
-- Don't assume the user knows what /schedule is. If they ask, briefly explain: "It's Anthropic's scheduled-task feature — runs your prompt on their cloud on a cron schedule, no need to keep your laptop on."
+---
+name: tfg-schedule
+description: Set up automated Tokens for Good research on a schedule (daily — with a chosen number of runs per day — or weekly). Use this when the user wants their AI to donate spare tokens to nonprofit research without manual prompting — it wires up a recurring /schedule agent in one shot instead of making them run /schedule, pick a schedule, and paste a prompt by hand.
+---
+
+The user wants to automate Tokens for Good research on a recurring schedule.
+
+## 1. Settle the cadence
+
+Work out the cadence before doing anything else:
+
+- If you were invoked with an explicit cadence (e.g. `frequency=daily`, `runs_per_day=3`) or the user already stated one, use it.
+- Otherwise ask the user, offering: **Daily** (recommended), **Weekly** (light touch), or **Skip for now**.
+- For a daily cadence with no per-day count set, ask **"How many times per day? (1–15)"**. Claude Code caps how many scheduled runs you get per day, so keep it at 15 or below. Default to 1 if the user has no preference.
+
+Describe cadence by frequency only — keep token costs and dollar amounts out of every question and confirmation.
+
+## 2. Wire it up
+
+1. **Call the TFG MCP `setup_automation` tool** with `frequency` (`daily` or `weekly`) and, for daily, `runs_per_day`. It returns the full `/schedule` setup text: a Step 2 schedule line containing a cron expression, and a research prompt scoped to the user's API key.
+
+2. **Extract the research prompt** — the block delimited by `---` lines. Pass it through verbatim; don't paraphrase.
+
+3. **Invoke the `/schedule` skill** to create the recurring trigger:
+   - Schedule: the cron expression from `setup_automation`'s Step 2 line.
+   - Task description: the verbatim block from step 2.
+
+4. **Wait for `/schedule` to confirm success.** If it fails or the user cancels, stop here and tell the user — do NOT call `mark_setup_complete`.
+
+5. **On success, call the TFG MCP `mark_setup_complete` tool.** This flips the user's local state so the SessionStart hook stops nudging.
+
+6. **Confirm to the user** in one sentence, e.g. *"Scheduled ✓ — your spare tokens will research a nonprofit on that cadence from here on. You can change it anytime with /schedule."*
+
+## If something goes wrong
+
+- **`setup_automation` returned an error about a missing API key** → tell the user to run `npx tokens-for-good init` in their terminal and re-open Claude Code.
+- **`/schedule` skill not available** → the user's Claude Code version may be too old; direct them to update.
+- **User declines the /schedule confirmation** → don't call `mark_setup_complete`. The hook will offer again next session.
+
+## What not to do
+
+- Keep token costs and dollar figures out of every question and confirmation.
+- If the user already picked a cadence at install, don't re-ask it — only ask for the per-day count when it's missing for a daily cadence.
+- Don't print the raw research prompt to the user; it's verbose and already flows through /schedule.
+- Don't assume the user knows what /schedule is. If they ask, briefly explain: "It's Anthropic's scheduled-task feature — runs your prompt on their cloud on a cron schedule, no need to keep your laptop on."

package/skills/tfg.md

@@ -1,6 +1,6 @@
 ---
 name: tfg
-description: Do one Tokens for Good research task end-to-end — claim an org, research it using the provided methodology, and submit the report. Use when the user wants to contribute once (not set up automation). Takes ~5 minutes and ~$0.20 in tokens per org.
+description: Do one Tokens for Good research task end-to-end — claim an org, research it using the provided methodology, and submit the report. Use when the user wants to contribute once (not set up automation). Takes about 5 minutes per org.
 ---
 
 The user wants to complete one Tokens for Good research cycle.

package/src/init.js

@@ -8,7 +8,7 @@ import { join, dirname } from 'path';
 import { homedir } from 'os';
 import { fileURLToPath } from 'url';
 import { spawnSync } from 'child_process';
-import { detectPlatform } from './platform.js';
+import { detectPlatform, cronForSchedule, MAX_RUNS_PER_DAY } from './platform.js';
 import { loadState, saveState } from './state.js';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
@@ -16,9 +16,8 @@ const PKG_ROOT = join(__dirname, '..');
 const IS_WINDOWS = process.platform === 'win32';
 
 const FREQUENCY_CHOICES = [
-  { title: 'Daily  — recommended, sustainable cadence',                    value: 'daily'   },
+  { title: 'Daily  — recommended; pick how many runs per day next',        value: 'daily'   },
   { title: 'Weekly — light touch',                                         value: 'weekly'  },
-  { title: 'Hourly — aggressive (many orgs per day)',                      value: 'hourly'  },
   { title: "One-off — I'll run research manually when I feel like it",     value: 'one_off' },
 ];
 
@@ -45,7 +44,7 @@ export async function runInit() {
     const { redo } = await prompts({
       type: 'confirm',
       name: 'redo',
-      message: `Already set up (${existing.intended_flow}${existing.intended_frequency ? `, ${existing.intended_frequency}` : ''}). Reconfigure?`,
+      message: `Already set up (${existing.intended_flow}${existing.intended_frequency ? `, ${existing.intended_frequency}${existing.intended_frequency === 'daily' && existing.runs_per_day > 1 ? ` ${existing.runs_per_day}×/day` : ''}` : ''}). Reconfigure?`,
       initial: false,
     }, { onCancel });
     if (!redo) {
@@ -82,6 +81,21 @@ export async function runInit() {
     initial: 0,
   }, { onCancel });
 
+  // Step 3b: Daily cadence — how many runs per day. Claude Code caps the
+  // number of scheduled runs per day, so we ask for a count (1-15).
+  let runs_per_day = null;
+  if (choice === 'daily') {
+    const { count } = await prompts({
+      type: 'number',
+      name: 'count',
+      message: `How many times per day? (1-${MAX_RUNS_PER_DAY})`,
+      initial: 1,
+      min: 1,
+      max: MAX_RUNS_PER_DAY,
+    }, { onCancel });
+    runs_per_day = count || 1;
+  }
+
   const intended_flow = choice === 'one_off' ? 'one_off' : 'scheduled';
   const intended_frequency = choice === 'one_off' ? null : choice;
 
@@ -120,6 +134,7 @@ export async function runInit() {
     ...loadState(),
     intended_flow,
     intended_frequency,
+    runs_per_day,
     first_setup_complete: false,
     platform,
     installed_at: new Date().toISOString(),
@@ -130,7 +145,7 @@ export async function runInit() {
 
   // Closing message
   console.log('\n✓ Setup complete.\n');
-  printClosingGuidance(platform, intended_flow, intended_frequency);
+  printClosingGuidance(platform, intended_flow, intended_frequency, runs_per_day);
 }
 
 // --- Planning (for preview + execute) ---
@@ -300,10 +315,11 @@ function writeQwenCommand(name) {
 
 // --- Closing guidance ---
 
-function printClosingGuidance(platform, flow, freq) {
+function printClosingGuidance(platform, flow, freq, runsPerDay = 1) {
+  const cadence = freq === 'daily' && runsPerDay > 1 ? `daily (${runsPerDay}× per day)` : freq;
   if (platform === 'claude-code') {
     if (flow === 'scheduled') {
-      console.log(`Open Claude Code — your first session will set up /schedule at ${freq} cadence automatically.`);
+      console.log(`Open Claude Code — your first session will set up /schedule at ${cadence} cadence automatically.`);
     } else {
       console.log('Open Claude Code — your first session will kick off a one-off research task.');
     }
@@ -314,7 +330,7 @@ function printClosingGuidance(platform, flow, freq) {
     if (flow === 'scheduled') {
       console.log(`MCP config written to ${mcpConfigPath('opencode')}.\n`);
       console.log('To run on a schedule, add this to your crontab (crontab -e):');
-      console.log(`  ${cronExpression(freq)} cd /path/to/workspace && opencode run "Research a nonprofit org for Fierce Philanthropy using the tokens-for-good MCP tools."\n`);
+      console.log(`  ${cronForSchedule(freq, runsPerDay)} cd /path/to/workspace && opencode run "Research a nonprofit org for Fierce Philanthropy using the tokens-for-good MCP tools."\n`);
     } else {
       console.log('MCP config written. In OpenCode run: "Research a nonprofit org for Fierce Philanthropy."\n');
     }
@@ -328,7 +344,7 @@ function printClosingGuidance(platform, flow, freq) {
       console.log('\nFor recurring runs, either:');
       console.log('  • Enable Qwen Code\'s experimental cron (set QWEN_CODE_ENABLE_CRON=1 and use the Cron tool / /loop), or');
       console.log('  • Add a system cron line (crontab -e):');
-      console.log(`      ${cronExpression(freq)} cd /path/to/workspace && qwen --prompt "Run /tfg"`);
+      console.log(`      ${cronForSchedule(freq, runsPerDay)} cd /path/to/workspace && qwen --prompt "Run /tfg"`);
     }
     console.log('');
     return;
@@ -341,9 +357,3 @@ function printClosingGuidance(platform, flow, freq) {
   }
   console.log('');
 }
-
-function cronExpression(freq) {
-  if (freq === 'hourly') return '0 * * * *';
-  if (freq === 'weekly') return '0 2 * * 1';
-  return '0 2 * * *';
-}

package/src/mcp-server.js

@@ -21,7 +21,7 @@ Tell the user to run this in their terminal (not here in the chat), then restart
 
   npx tokens-for-good init
 
-The init command asks them to choose a contribution cadence (hourly / daily / weekly / one-off) and wires up everything else automatically. It takes about 30 seconds.`;
+The init command asks them to choose a contribution cadence (daily / weekly / one-off) and wires up everything else automatically. It takes about 30 seconds.`;
 
 // Gate: only fires for genuinely cold installs where state.json is missing
 // entirely. Existing users — including those on the pre-0.4.0 schema — pass
@@ -57,12 +57,12 @@ const NO_KEY_INSTRUCTIONS = `The user wants to set up Tokens for Good. Tell them
 The command walks them through everything in under a minute:
 1. Create an account at https://tokensforgood.ai/contribute (GitHub OAuth, free)
 2. Copy their API key (starts with \`tfg_live_\`) and paste it into the init prompt
-3. Pick a cadence: **daily** (recommended), weekly, hourly, or one-off
+3. Pick a cadence: **daily** (recommended; choose how many runs per day), weekly, or one-off
 4. Confirm
 
 init writes everything — MCP config, SessionStart hook, /tfg and /tfg-schedule skills, and their recorded preference — in one shot. The first session after init runs their chosen flow automatically.
 
-**What is Tokens for Good?** A way for developers to donate their spare AI subscription tokens to research nonprofit organizations for Fierce Philanthropy's social impact directory. Each org takes ~5 minutes and ~$0.20 in tokens. Contributors get credit on a public leaderboard.`;
+**What is Tokens for Good?** A way for developers to donate their spare AI subscription tokens to research nonprofit organizations for Fierce Philanthropy's social impact directory. Each org takes about 5 minutes. Contributors get credit on a public leaderboard.`;
 
 // --- Resources ---
 
@@ -95,7 +95,7 @@ Contributor tiers:
 
 Automation: On Claude Code, use /schedule to auto-contribute daily. On Opencode, set up a system cron. On Cursor/Windsurf, contribute manually when prompted.
 
-Cost: ~$0.15-0.25 per org in tokens. Scale: 750K+ US nonprofits to research.`,
+Scale: 750K+ US nonprofits to research.`,
   }],
 }));
 
@@ -245,10 +245,9 @@ server.tool('my_impact', 'See your personal contribution stats, tier, and histor
   try {
     const result = await client.getImpact();
     const c = result.contributor;
-    const estimatedCost = (c.total_tokens / 1_000_000 * 3).toFixed(2);
 
     return {
-      content: [{ type: 'text', text: `Your Impact (@${c.github_handle}):\n\nTier: ${c.tier}\nOrgs researched: ${c.total_orgs}\nEstimated donation: ~$${estimatedCost}\nAcceptance rate: ${c.acceptance_rate}%\nAutomation: ${c.has_schedule ? 'Active' : 'Not set up'}\n\nRecent:\n${result.claims?.slice(0, 5).map(cl => `  ${cl.organization?.name || 'Unknown'} - ${cl.status}`).join('\n') || 'None'}` }],
+      content: [{ type: 'text', text: `Your Impact (@${c.github_handle}):\n\nTier: ${c.tier}\nOrgs researched: ${c.total_orgs}\nAcceptance rate: ${c.acceptance_rate}%\nAutomation: ${c.has_schedule ? 'Active' : 'Not set up'}\n\nRecent:\n${result.claims?.slice(0, 5).map(cl => `  ${cl.organization?.name || 'Unknown'} - ${cl.status}`).join('\n') || 'None'}` }],
     };
   } catch (err) {
     return { content: [{ type: 'text', text: `Error: ${err.message}` }] };
@@ -260,10 +259,11 @@ server.tool('setup_guide', 'Get setup instructions for Tokens for Good. Use this
 });
 
 server.tool('setup_automation', 'Get the scheduled-research prompt + setup instructions for the user\'s platform. Usually called by the /tfg-schedule skill (which extracts the prompt and invokes /schedule). Safe to call directly too — returns human-readable instructions.', {
-  frequency: z.enum(['hourly', 'daily', 'weekly']).optional().describe('How often to contribute'),
-}, async ({ frequency }) => {
+  frequency: z.enum(['daily', 'weekly']).optional().describe('How often to contribute'),
+  runs_per_day: z.number().int().min(1).max(15).optional().describe('For daily cadence: how many research runs per day (1-15). Defaults to 1.'),
+}, async ({ frequency, runs_per_day }) => {
   if (notInitialized()) return { content: [{ type: 'text', text: INIT_GUARD_MESSAGE }] };
-  const instructions = getAutomationInstructions(platform, frequency || 'daily', apiKey);
+  const instructions = getAutomationInstructions(platform, frequency || 'daily', apiKey, runs_per_day || 1);
   return { content: [{ type: 'text', text: instructions }] };
 });
 
@@ -342,7 +342,7 @@ server.prompt('session_start', 'Check if you should research an org or complete
     return {
       messages: [{
         role: 'user',
-        content: { type: 'text', text: `Tokens for Good: Would you like to research a nonprofit org today? It takes about 5 minutes and costs ~$0.20 in tokens.\n\n1. Research an org now\n2. Ask me tomorrow\n3. Ask me in a week\n\nUse claim_org for option 1.` },
+        content: { type: 'text', text: `Tokens for Good: Would you like to research a nonprofit org today? It takes about 5 minutes.\n\n1. Research an org now\n2. Ask me tomorrow\n3. Ask me in a week\n\nUse claim_org for option 1.` },
       }],
     };
   }

package/src/platform.js

@@ -40,19 +40,25 @@ Auth header for all requests: X-TFG-Api-Key: ${apiKey}
 All endpoints, scoring criteria, and submission format are in the fetched instructions.`;
 }
 
-export function getAutomationInstructions(platform, frequency = 'daily', apiKey = null) {
+// Claude Code caps how many scheduled runs a routine gets per day, so daily
+// research fires a chosen number of times (1-15).
+export const MAX_RUNS_PER_DAY = 15;
+
+export function getAutomationInstructions(platform, frequency = 'daily', apiKey = null, runsPerDay = 1) {
+  const cron = cronForSchedule(frequency, runsPerDay);
+  const label = scheduleLabel(frequency, runsPerDay);
   switch (platform) {
     case 'claude-code':
       return `Set up automated contributions with Claude Code's /schedule command.
 
-(The /tfg-schedule skill does these 3 steps automatically. If you're reading this because Claude is orchestrating /tfg-schedule, extract the prompt between the --- markers and invoke /schedule with frequency="${frequency}" and that prompt.)
+(The /tfg-schedule skill does these 3 steps automatically. If you're reading this because Claude is orchestrating /tfg-schedule, extract the prompt between the --- markers and invoke /schedule on the schedule below with that prompt.)
 
 **Step 1:** Run this in Claude Code:
 \`\`\`
 /schedule
 \`\`\`
 
-**Step 2:** Set frequency to "${frequency}"
+**Step 2:** Set the schedule to ${label} (cron: \`${cron}\`)
 
 **Step 3:** When prompted for the task description, paste the prompt between the --- markers below:
 
@@ -66,13 +72,13 @@ This runs on Anthropic's cloud infrastructure. Your machine doesn't need to be o
       return `Set up automated contributions with a system cron job:
 
 Add this to your crontab (crontab -e):
-${getCronExpression(frequency)} cd /path/to/workspace && opencode run "Research a nonprofit org for Fierce Philanthropy using the tokens-for-good MCP tools. Claim an org, research it, then submit the report."
+${cron} cd /path/to/workspace && opencode run "Research a nonprofit org for Fierce Philanthropy using the tokens-for-good MCP tools. Claim an org, research it, then submit the report."
 
 Your machine must be on for cron jobs to run.`;
 
     case 'devin':
       return `Set up a recurring Devin session to contribute automatically.
-Configure a ${frequency} recurring session with the prompt:
+Configure a ${label} recurring session with the prompt:
 "Research a nonprofit org for Fierce Philanthropy using the tokens-for-good MCP tools."
 
 Devin runs in the cloud, fully autonomous.`;
@@ -83,20 +89,31 @@ Devin runs in the cloud, fully autonomous.`;
 Qwen Code v0.14+ has experimental built-in cron — enable it with QWEN_CODE_ENABLE_CRON=1 (or "experimental.cron": true in ~/.qwen/settings.json) and then use the Cron tool / /loop skill.
 
 For a portable option, use a system cron job (add via crontab -e):
-${getCronExpression(frequency)} cd /path/to/workspace && qwen --prompt "Research a nonprofit org for Fierce Philanthropy using the tokens-for-good MCP tools. Claim an org, research it, then submit the report."
+${cron} cd /path/to/workspace && qwen --prompt "Research a nonprofit org for Fierce Philanthropy using the tokens-for-good MCP tools. Claim an org, research it, then submit the report."
 
 Your machine must stay on for system cron to run.`;
 
     default:
-      return getAutomationInstructions('claude-code', frequency, apiKey);
+      return getAutomationInstructions('claude-code', frequency, apiKey, runsPerDay);
   }
 }
 
-function getCronExpression(frequency) {
-  switch (frequency) {
-    case 'hourly': return '0 * * * *';
-    case 'daily': return '0 2 * * *';
-    case 'weekly': return '0 2 * * 1';
-    default: return '0 2 * * *';
-  }
+// Build a cron expression. Weekly fires Monday 02:00. Daily fires `runsPerDay`
+// times (1-15), evenly spaced across the day; once-daily fires at 02:00.
+export function cronForSchedule(frequency, runsPerDay = 1) {
+  if (frequency === 'weekly') return '0 2 * * 1';
+  const n = clampRunsPerDay(runsPerDay);
+  if (n === 1) return '0 2 * * *';
+  const hours = Array.from({ length: n }, (_, i) => Math.round((i * 24) / n));
+  return `0 ${hours.join(',')} * * *`;
+}
+
+function scheduleLabel(frequency, runsPerDay = 1) {
+  if (frequency === 'weekly') return 'weekly (Mondays)';
+  const n = clampRunsPerDay(runsPerDay);
+  return n === 1 ? 'daily' : `${n}× per day`;
+}
+
+function clampRunsPerDay(runsPerDay) {
+  return Math.min(MAX_RUNS_PER_DAY, Math.max(1, Math.floor(Number(runsPerDay)) || 1));
 }

package/src/session-start-hook.js

@@ -55,12 +55,16 @@ function firstSessionMessage(state) {
     : 'recently';
 
   if (state.intended_flow === 'scheduled') {
-    const freq = state.intended_frequency || 'daily';
+    // Normalize to the supported cadences (older installs may hold other values).
+    const freq = state.intended_frequency === 'weekly' ? 'weekly' : 'daily';
+    const runs = freq === 'daily' ? (state.runs_per_day || 1) : null;
+    const runsClause = runs ? ` and runs_per_day=${runs}` : '';
+    const cadence = runs && runs > 1 ? `${freq}, ${runs}× per day` : freq;
     return (
       `Tokens for Good: The user ran \`npx tokens-for-good init\` on ${installedOn} ` +
-      `and chose scheduled research at ${freq} cadence. This is their first Claude Code ` +
+      `and chose scheduled research (${cadence}). This is their first Claude Code ` +
       `session since. Before any other task, invoke the /tfg-schedule skill with ` +
-      `frequency=${freq}. After /schedule confirms, the skill will call ` +
+      `frequency=${freq}${runsClause}. After /schedule confirms, the skill will call ` +
       `mark_setup_complete on the TFG MCP to dismiss this prompt.`
     );
   }

package/src/state.js

@@ -13,7 +13,8 @@ const DEFAULT_STATE = {
   platform: null,
   total_session_contributions: 0,
   intended_flow: null,          // 'scheduled' | 'one_off' | null (pre-init)
-  intended_frequency: null,     // 'hourly' | 'daily' | 'weekly' | null
+  intended_frequency: null,     // 'daily' | 'weekly' | null
+  runs_per_day: null,           // 1-15 when intended_frequency === 'daily', else null
   first_setup_complete: false,  // flipped by mark_setup_complete tool after first scheduled run or first one-off submit
   installed_at: null,           // ISO timestamp when init finished
 };