zilmate 1.7.2 → 1.7.5

package/scripts/postinstall.mjs

@@ -1,42 +1,42 @@
-// postinstall.mjs
-import { mkdir, writeFile } from 'node:fs/promises';
-import { existsSync } from 'node:fs';
-import path from 'node:path';
-import { homedir } from 'node:os';
-
-const root = process.env.ZILMATE_WORKSPACE?.trim()
-  ? path.resolve(process.env.ZILMATE_WORKSPACE.trim())
-  : process.platform === 'win32' || process.platform === 'darwin'
-    ? path.join(homedir(), 'Downloads', 'ZilMate')
-    : path.join(homedir(), 'ZilMate');
-
-const dirs = [
-  root,
-  path.join(root, 'skills'),
-  path.join(root, 'outputs', 'osint'),
-  path.join(root, 'outputs', 'pentest'),
-  path.join(root, 'outputs', 'images'),
-  path.join(root, 'logs'),
-  path.join(root, 'projects'),
-  path.join(root, 'attachments'),
-  path.join(root, 'backups'),
-  path.join(root, 'config'),
-  path.join(root, 'scratch'),
-  path.join(root, 'data'),
-];
-
-for (const dir of dirs) {
-  await mkdir(dir, { recursive: true });
-}
-
-const notebook = path.join(root, 'notebook.md');
-if (!existsSync(notebook)) {
-  await writeFile(notebook, '# ZilMate Notebook\n\n', 'utf8');
-}
-
-const memory = path.join(root, 'memory.json');
-if (!existsSync(memory)) {
-  await writeFile(memory, '[]\n', 'utf8');
-}
-
-console.log(`ZilMate workspace ready at ${root}`);
+// postinstall.mjs
+import { mkdir, writeFile } from 'node:fs/promises';
+import { existsSync } from 'node:fs';
+import path from 'node:path';
+import { homedir } from 'node:os';
+
+const root = process.env.ZILMATE_WORKSPACE?.trim()
+  ? path.resolve(process.env.ZILMATE_WORKSPACE.trim())
+  : process.platform === 'win32' || process.platform === 'darwin'
+    ? path.join(homedir(), 'Downloads', 'ZilMate')
+    : path.join(homedir(), 'ZilMate');
+
+const dirs = [
+  root,
+  path.join(root, 'skills'),
+  path.join(root, 'outputs', 'osint'),
+  path.join(root, 'outputs', 'pentest'),
+  path.join(root, 'outputs', 'images'),
+  path.join(root, 'logs'),
+  path.join(root, 'projects'),
+  path.join(root, 'attachments'),
+  path.join(root, 'backups'),
+  path.join(root, 'config'),
+  path.join(root, 'scratch'),
+  path.join(root, 'data'),
+];
+
+for (const dir of dirs) {
+  await mkdir(dir, { recursive: true });
+}
+
+const notebook = path.join(root, 'notebook.md');
+if (!existsSync(notebook)) {
+  await writeFile(notebook, '# ZilMate Notebook\n\n', 'utf8');
+}
+
+const memory = path.join(root, 'memory.json');
+if (!existsSync(memory)) {
+  await writeFile(memory, '[]\n', 'utf8');
+}
+
+console.log(`ZilMate workspace ready at ${root}`);

package/scripts/release-github.mjs

@@ -1,91 +1,91 @@
-import { execFileSync } from 'node:child_process';
-import { readFileSync, writeFileSync } from 'node:fs';
-import { join } from 'node:path';
-import { tmpdir } from 'node:os';
-
-const args = new Set(process.argv.slice(2));
-const dryRun = args.has('--dry-run');
-const pkg = JSON.parse(readFileSync(new URL('../package.json', import.meta.url), 'utf8'));
-const version = pkg.version;
-const tag = `v${version}`;
-const title = `ZilMate ${tag}`;
-
-const notes = `# ${title}
-
-ZilMate ${tag} — Claude-inspired CLI, situational awareness, session handoffs, model picker, and SDK docs.
-
-## Install
-
-\`\`\`powershell
-npm install -g zilmate@${version}
-zilmate setup
-zilmate doctor --live
-zilmate talk
-\`\`\`
-
-## Highlights
-
-- **Beautiful CLI** — welcome card, tips, boxed composer input, Claude-style tool progress (\`● tool\` / \`└ Done\`).
-- **/model pick** — interactively choose manager, coding, image, and vision models; persisted to workspace \`config/models.json\`.
-- **Situational awareness** — \`getSituationBrief\` snapshots cwd, git, workspace, jobs, memory, models, and capabilities.
-- **Session continuity** — handoff save/load/generate so ZilMate resumes where you left off.
-- **Coding intelligence** — five tools: grep, working-tree review, symbol explain, scaffold, project checks; appBuilder + qaIntegration sub-coders.
-- **Image director** — \`enhanceImagePrompt\` + generation with art-direction presets.
-- **Cloudflare setup** — dedicated tunnel section in \`zilmate setup\`; \`zilmate jobs listen --tunnel\`.
-- **SDK.md** — Next.js App Router streaming route, subagents, jobs, voice, model selection.
-
-## Quick Checks
-
-\`\`\`powershell
-zilmate talk
-/model pick
-zilmate jobs listen --tunnel
-\`\`\`
-
-## npm
-
-Published package: \`zilmate@${version}\`
-`;
-
-const run = (command, commandArgs, options = {}) => {
-  return execFileSync(command, commandArgs, {
-    encoding: 'utf8',
-    stdio: options.stdio ?? 'pipe',
-    ...options,
-  });
-};
-
-if (dryRun) {
-  console.log(`Tag: ${tag}`);
-  console.log(`Title: ${title}`);
-  console.log('');
-  console.log(notes);
-  process.exit(0);
-}
-
-try {
-  run('gh', ['auth', 'status'], { stdio: 'pipe' });
-} catch {
-  console.error('GitHub CLI is not authenticated. Run: gh auth login -h github.com');
-  process.exit(1);
-}
-
-const notesPath = join(tmpdir(), `zilmate-${version}-github-release.md`);
-writeFileSync(notesPath, notes);
-
-run(
-  'gh',
-  [
-    'release',
-    'create',
-    tag,
-    '--repo',
-    'zester4/zilo-manager',
-    '--title',
-    title,
-    '--notes-file',
-    notesPath,
-    '--latest',
-  ],
-  { stdio: 'inherit' },
-);
+import { execFileSync } from 'node:child_process';
+import { readFileSync, writeFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { tmpdir } from 'node:os';
+
+const args = new Set(process.argv.slice(2));
+const dryRun = args.has('--dry-run');
+const pkg = JSON.parse(readFileSync(new URL('../package.json', import.meta.url), 'utf8'));
+const version = pkg.version;
+const tag = `v${version}`;
+const title = `ZilMate ${tag}`;
+
+const notes = `# ${title}
+
+ZilMate ${tag} — Claude-inspired CLI, situational awareness, session handoffs, model picker, and SDK docs.
+
+## Install
+
+\`\`\`powershell
+npm install -g zilmate@${version}
+zilmate setup
+zilmate doctor --live
+zilmate talk
+\`\`\`
+
+## Highlights
+
+- **Beautiful CLI** — welcome card, tips, boxed composer input, Claude-style tool progress (\`● tool\` / \`└ Done\`).
+- **/model pick** — interactively choose manager, coding, image, and vision models; persisted to workspace \`config/models.json\`.
+- **Situational awareness** — \`getSituationBrief\` snapshots cwd, git, workspace, jobs, memory, models, and capabilities.
+- **Session continuity** — handoff save/load/generate so ZilMate resumes where you left off.
+- **Coding intelligence** — five tools: grep, working-tree review, symbol explain, scaffold, project checks; appBuilder + qaIntegration sub-coders.
+- **Image director** — \`enhanceImagePrompt\` + generation with art-direction presets.
+- **Cloudflare setup** — dedicated tunnel section in \`zilmate setup\`; \`zilmate jobs listen --tunnel\`.
+- **SDK.md** — Next.js App Router streaming route, subagents, jobs, voice, model selection.
+
+## Quick Checks
+
+\`\`\`powershell
+zilmate talk
+/model pick
+zilmate jobs listen --tunnel
+\`\`\`
+
+## npm
+
+Published package: \`zilmate@${version}\`
+`;
+
+const run = (command, commandArgs, options = {}) => {
+  return execFileSync(command, commandArgs, {
+    encoding: 'utf8',
+    stdio: options.stdio ?? 'pipe',
+    ...options,
+  });
+};
+
+if (dryRun) {
+  console.log(`Tag: ${tag}`);
+  console.log(`Title: ${title}`);
+  console.log('');
+  console.log(notes);
+  process.exit(0);
+}
+
+try {
+  run('gh', ['auth', 'status'], { stdio: 'pipe' });
+} catch {
+  console.error('GitHub CLI is not authenticated. Run: gh auth login -h github.com');
+  process.exit(1);
+}
+
+const notesPath = join(tmpdir(), `zilmate-${version}-github-release.md`);
+writeFileSync(notesPath, notes);
+
+run(
+  'gh',
+  [
+    'release',
+    'create',
+    tag,
+    '--repo',
+    'zester4/zilo-manager',
+    '--title',
+    title,
+    '--notes-file',
+    notesPath,
+    '--latest',
+  ],
+  { stdio: 'inherit' },
+);

package/src/doc/README.md

@@ -1,49 +1,49 @@
-# ZiloShift Support Training Docs
-
-These docs train support staff to help workers and venues use ZiloShift confidently, safely, and consistently.
-
-## Who These Docs Are For
-
-- Customer support agents helping workers and venues.
-- Operations staff reviewing verification, payments, disputes, and shift issues.
-- Admin users handling SMS campaigns, account questions, and escalation.
-
-## Core Support Principles
-
-1. Protect user safety and money first.
-2. Verify the account, role, country, and shift before giving specific advice.
-3. Do not ask users to share passwords, full card details, full ID numbers, or private API keys.
-4. Explain next steps clearly and avoid blaming the user.
-5. Escalate when money, identity, fraud, safety, legal, or platform bugs are involved.
-
-## Platform Overview
-
-ZiloShift connects workers with venues that need shift cover. Workers create profiles, verify identity, add roles/certifications, browse shifts in their city, apply, get accepted, clock in/out, message venues, and receive payouts. Venues verify their business, connect payment/billing, post shifts, review applicants, accept workers, coordinate through messages, and confirm completion.
-
-## Support Areas
-
-- [Worker Support Playbook](./worker-support-playbook.md)
-- [Venue Support Playbook](./venue-support-playbook.md)
-- [Verification And Trust](./verification-and-trust.md)
-- [Payments And Payouts](./payments-and-payouts.md)
-- [Shift Lifecycle And Disputes](./shift-lifecycle-and-disputes.md)
-- [Admin Tools And SMS Campaigns](./admin-tools-and-sms-campaigns.md)
-- [Support Macros](./support-macros.md)
-- [Escalation Checklist](./escalation-checklist.md)
-
-## Quick Triage Questions
-
-Ask these before troubleshooting:
-
-1. Are you a worker or venue?
-2. What country are you in?
-3. What email or phone number is on the account?
-4. What page were you on when the issue happened?
-5. If it is about a shift, what is the role, date, venue/company, and city?
-6. If it is about payment, what provider was shown: Hubtel, Paystack, Razorpay, Stripe, or bank/card?
-7. What exact error message did you see?
-
-## Risk Warning
-
-Do not manually override identity verification, payment status, payout destination, worker reliability, cancellation penalties, or dispute outcomes unless an authorized admin or engineering escalation confirms it.
-
+# ZiloShift Support Training Docs
+
+These docs train support staff to help workers and venues use ZiloShift confidently, safely, and consistently.
+
+## Who These Docs Are For
+
+- Customer support agents helping workers and venues.
+- Operations staff reviewing verification, payments, disputes, and shift issues.
+- Admin users handling SMS campaigns, account questions, and escalation.
+
+## Core Support Principles
+
+1. Protect user safety and money first.
+2. Verify the account, role, country, and shift before giving specific advice.
+3. Do not ask users to share passwords, full card details, full ID numbers, or private API keys.
+4. Explain next steps clearly and avoid blaming the user.
+5. Escalate when money, identity, fraud, safety, legal, or platform bugs are involved.
+
+## Platform Overview
+
+ZiloShift connects workers with venues that need shift cover. Workers create profiles, verify identity, add roles/certifications, browse shifts in their city, apply, get accepted, clock in/out, message venues, and receive payouts. Venues verify their business, connect payment/billing, post shifts, review applicants, accept workers, coordinate through messages, and confirm completion.
+
+## Support Areas
+
+- [Worker Support Playbook](./worker-support-playbook.md)
+- [Venue Support Playbook](./venue-support-playbook.md)
+- [Verification And Trust](./verification-and-trust.md)
+- [Payments And Payouts](./payments-and-payouts.md)
+- [Shift Lifecycle And Disputes](./shift-lifecycle-and-disputes.md)
+- [Admin Tools And SMS Campaigns](./admin-tools-and-sms-campaigns.md)
+- [Support Macros](./support-macros.md)
+- [Escalation Checklist](./escalation-checklist.md)
+
+## Quick Triage Questions
+
+Ask these before troubleshooting:
+
+1. Are you a worker or venue?
+2. What country are you in?
+3. What email or phone number is on the account?
+4. What page were you on when the issue happened?
+5. If it is about a shift, what is the role, date, venue/company, and city?
+6. If it is about payment, what provider was shown: Hubtel, Paystack, Razorpay, Stripe, or bank/card?
+7. What exact error message did you see?
+
+## Risk Warning
+
+Do not manually override identity verification, payment status, payout destination, worker reliability, cancellation penalties, or dispute outcomes unless an authorized admin or engineering escalation confirms it.
+

package/src/doc/admin-tools-and-sms-campaigns.md

@@ -1,99 +1,99 @@
-# Admin Tools And SMS Campaigns
-
-This guide trains admins to use campaign tools, verification queues, user management, shifts, payments, and disputes.
-
-## Admin SMS Campaigns
-
-SMS campaigns are for Ghana users through Hubtel SMS.
-
-Supported audiences:
-
-- Workers.
-- Venues.
-- Both workers and venues.
-
-The campaign tool should:
-
-1. Let admin choose audience.
-2. Preview real recipients.
-3. Show skipped users missing phone numbers.
-4. Send a test SMS before bulk sending.
-5. Send personalized batch SMS through Hubtel.
-6. Save campaign logs in `sms_campaigns`.
-
-## Hubtel SMS Contract
-
-The gateway follows Hubtel SMS docs:
-
-- Single test SMS: `POST /v1/messages/send`.
-- Personalized batch SMS: `POST /v1/messages/batch/personalized/send`.
-- Basic Auth is built from SMS credentials.
-- Sender ID max length is 11 characters.
-
-Supported variables:
-
-- `{{first_name}}`
-- `{{last_name}}`
-- `{{name}}`
-- `{{company_name}}`
-- `{{account_type}}`
-- `{{city}}`
-- `{{town}}`
-
-## SMS Troubleshooting
-
-If test SMS returns 400:
-
-- Check Hubtel error details.
-- Check phone format normalizes to `233...`.
-- Check sender ID is 11 characters or less.
-- Check message length is not too long.
-- Check SMS account credit.
-- Check if recipient is blacklisted.
-- Check SMS credentials.
-
-If no workers appear:
-
-- Check Ghana workers have profile phone numbers.
-- Workers without phone numbers are skipped.
-
-If venues appear but workers do not:
-
-- Venue phone may exist on `venues.phone`.
-- Worker phone must exist on `profiles.phone`.
-
-## Admin Verification Page
-
-Admins can review identity and business verification.
-
-Do not approve:
-
-- Mismatched names.
-- Blurry IDs.
-- Missing liveness.
-- Suspicious duplicate accounts.
-
-## Admin Payments Page
-
-Admins should use this for:
-
-- Captured payments.
-- Payout status.
-- Failed provider responses.
-- Refund checks.
-
-Never expose secret keys in admin notes or user replies.
-
-## Admin Disputes Page
-
-Admins should review:
-
-- Worker/venue claims.
-- Shift status.
-- Clock-in/out.
-- Messages.
-- Payment status.
-- Reliability/no-show history.
-
-Keep notes factual and timestamped.
-
+# Admin Tools And SMS Campaigns
+
+This guide trains admins to use campaign tools, verification queues, user management, shifts, payments, and disputes.
+
+## Admin SMS Campaigns
+
+SMS campaigns are for Ghana users through Hubtel SMS.
+
+Supported audiences:
+
+- Workers.
+- Venues.
+- Both workers and venues.
+
+The campaign tool should:
+
+1. Let admin choose audience.
+2. Preview real recipients.
+3. Show skipped users missing phone numbers.
+4. Send a test SMS before bulk sending.
+5. Send personalized batch SMS through Hubtel.
+6. Save campaign logs in `sms_campaigns`.
+
+## Hubtel SMS Contract
+
+The gateway follows Hubtel SMS docs:
+
+- Single test SMS: `POST /v1/messages/send`.
+- Personalized batch SMS: `POST /v1/messages/batch/personalized/send`.
+- Basic Auth is built from SMS credentials.
+- Sender ID max length is 11 characters.
+
+Supported variables:
+
+- `{{first_name}}`
+- `{{last_name}}`
+- `{{name}}`
+- `{{company_name}}`
+- `{{account_type}}`
+- `{{city}}`
+- `{{town}}`
+
+## SMS Troubleshooting
+
+If test SMS returns 400:
+
+- Check Hubtel error details.
+- Check phone format normalizes to `233...`.
+- Check sender ID is 11 characters or less.
+- Check message length is not too long.
+- Check SMS account credit.
+- Check if recipient is blacklisted.
+- Check SMS credentials.
+
+If no workers appear:
+
+- Check Ghana workers have profile phone numbers.
+- Workers without phone numbers are skipped.
+
+If venues appear but workers do not:
+
+- Venue phone may exist on `venues.phone`.
+- Worker phone must exist on `profiles.phone`.
+
+## Admin Verification Page
+
+Admins can review identity and business verification.
+
+Do not approve:
+
+- Mismatched names.
+- Blurry IDs.
+- Missing liveness.
+- Suspicious duplicate accounts.
+
+## Admin Payments Page
+
+Admins should use this for:
+
+- Captured payments.
+- Payout status.
+- Failed provider responses.
+- Refund checks.
+
+Never expose secret keys in admin notes or user replies.
+
+## Admin Disputes Page
+
+Admins should review:
+
+- Worker/venue claims.
+- Shift status.
+- Clock-in/out.
+- Messages.
+- Payment status.
+- Reliability/no-show history.
+
+Keep notes factual and timestamped.
+