@rubytech/taskmaster 1.10.0 → 1.11.0

package/skills/strategic-proactivity/references/daily-review.md

@@ -0,0 +1,64 @@
+# Daily Review Protocol
+
+Run this protocol on schedule or when triggered by an admin. Be thorough in analysis but concise in output.
+
+## Step 1: Conversation Scan
+
+Search all sessions from the review period (typically last 24 hours):
+- Public agent conversations (customer enquiries, feedback, objections)
+- Admin conversations (decisions, strategy discussions, new directions)
+- Group chats (partner feedback, team discussions)
+
+**What to look for:**
+- Questions the public agent couldn't answer or answered poorly — content gap
+- Pain points or frustrations mentioned repeatedly — messaging opportunity
+- New use cases, verticals, or audiences mentioned — market intel
+- Objections raised that aren't addressed in existing materials — sales gap
+- Positive feedback or testimonials — social proof opportunity
+- Contact or relationship signals — relationship development
+
+## Step 2: Materials Audit
+
+Search memory for the business's existing materials — documents, FAQs, guides, outreach trackers, website copy, pitch materials, training content, or anything the business maintains.
+
+Compare findings from Step 1 against those materials:
+- Are common questions covered in published content?
+- Does the public-facing copy still reflect current positioning and offerings?
+- Are contact lists and outreach records current?
+- Are any working hypotheses or strategies validated or invalidated by recent conversations?
+
+Don't assume which materials exist — discover them by searching memory.
+
+## Step 3: Opportunity Tracking
+
+Check for signals:
+- Inbound enquiries from unexpected verticals or audiences
+- Partners or contacts mentioning specific needs the business could serve
+- Competitors mentioned in conversations
+- Pricing feedback or willingness-to-pay signals
+- Feature or service requests that indicate market direction
+
+## Step 4: Draft Improvements
+
+For each gap or opportunity found:
+1. Write the actual content (FAQ entry, pitch angle, email draft, updated copy)
+2. Save to memory for admin review
+3. Include in the summary with a one-line description
+
+**Don't just flag — fix.** Admin reviews and approves; you do the drafting.
+
+## Step 5: Relationship Check
+
+Review active relationships:
+- Any contacts who haven't responded in 7+ days? Flag for follow-up
+- Any new contacts who need onboarding or introductory materials?
+- Any partners or collaborators who gave feedback that needs acting on?
+
+## Step 6: Housekeeping
+
+Scan scheduled jobs (cron) and clean up any that are in the past and not set to recur.
+
+## Step 7: Summary Output
+
+Compose the summary following the format defined in SKILL.md.
+The cron job or admin session takes care of delivery.

package/taskmaster-docs/USER-GUIDE.md

@@ -25,10 +25,12 @@ If you received a Taskmaster device:
 
 > **WiFi:** Your device needs an internet connection. You can plug a network cable directly into it to get started, then connect to WiFi from the Control Panel (see "WiFi" below). Need help? Message us on WhatsApp at **+44 7591 215452** or visit [taskmaster.bot](https://www.taskmaster.bot/).
 
-Then open your web browser on any device connected to the same WiFi and go to:
+Then open your web browser on any device connected to the same WiFi network and go to:
 
 **http://taskmaster.local:18789**
 
+> **Same network required:** The `.local` address only works when your phone/laptop and the Taskmaster device are on the **same network subnet**. If the Pi is plugged into Ethernet and your phone is on WiFi, some routers put them on separate subnets — in that case, connect the Pi to WiFi instead (see "WiFi" below), or connect both devices to the same wired or wireless network.
+
 ### Option B: Install on a Raspberry Pi (or any Linux OS) yourself
 
 You'll need a Raspberry Pi running Raspberry Pi OS with an internet connection (ethernet or WiFi).
@@ -46,6 +48,8 @@ curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 4. Open a browser on any device on the same Wi-Fi network and go to: **http://taskmaster.local:18789/setup**
 
 > After installation, Taskmaster runs in the background and starts automatically when the Pi restarts. It can take up to 2 minutes to come back online after a power cycle. You can disconnect the monitor and keyboard.
+>
+> **Same network required:** The `.local` address only works when your phone/laptop and the Taskmaster device are on the **same network subnet**. If the Pi is on Ethernet and your phone is on WiFi, some routers put them on separate subnets — in that case, connect the Pi to WiFi instead (see "WiFi" below), or ensure your router bridges Ethernet and WiFi onto the same subnet.
 
 ### Option C: Install on a Mac
 
@@ -502,6 +506,19 @@ Your assistant learns your customers, their service history, and your pricing th
 
 All outreach messages are sent as your assistant — customers reply normally and the conversation continues.
 
+### Daily Strategic Review
+
+Taskmaster ships with a pre-configured Daily Strategic Review that analyses your recent conversations, audits your business materials, and suggests improvements. It runs as a scheduled event but is **paused by default** — you choose when to enable it.
+
+**To enable:**
+1. Open the Control Panel
+2. Go to **Advanced** → **Events**
+3. Find **🔭 Daily Strategic Review** and enable it
+
+Once enabled, the review runs daily at 7:00 AM (your device's timezone). Results appear in the web chat, and are also sent via WhatsApp if you have an admin phone number connected.
+
+You can edit the schedule, change the time, or disable it at any time from the Events tab.
+
 ### Conversations & Sessions
 
 Your assistant has full access to conversation history across all channels — WhatsApp, webchat, iMessage, and group chats. It can find specific messages, review entire conversations, and give you an overview of all activity.
@@ -948,6 +965,12 @@ sudo sed -i "s/127\.0\.1\.1.*/127.0.1.1\tdave/" /etc/hosts
 sudo systemctl restart avahi-daemon
 ```
 
+> **Chromium lock after hostname change:** If Chromium is installed on the Pi and won't launch after changing the hostname (error: "profile appears to be in use by another Chromium process on another computer"), the old hostname left a stale lock file. Fix:
+> ```bash
+> rm -rf ~/.config/chromium/Singleton*
+> chromium
+> ```
+
 **Changing the hostname (macOS):**
 
 ```bash
@@ -975,7 +998,7 @@ After flushing, open your browser and navigate to the new URL (e.g. `http://dave
 If the Pi checks pass but the control panel still doesn't load from another device:
 
 1. **Use the IP address directly** — on the Pi, run `hostname -I` to get its IP address, then open `http://192.168.1.XXX:18789` (use your IP and port) from the other device. If this works, the problem is mDNS resolution, not the gateway.
-2. **Check you're on the same network** — mDNS only works between devices on the same WiFi/LAN. It won't work across VLANs or guest networks.
+2. **Check you're on the same subnet** — mDNS only works between devices on the same network subnet. It won't work across separate subnets, VLANs, or guest networks. A common cause: the Pi is on Ethernet while your device is on WiFi, and your router assigns them to different subnets. Check by comparing the first three groups of your IP addresses (e.g. if the Pi is `192.168.88.4` and your laptop is `192.168.10.172`, they're on different subnets).
 3. **Contact support** with: what you changed (port/hostname), the output of `hostname`, `grep 127.0.1.1 /etc/hosts`, and `taskmaster daemon status`.
 
 ### Static IP Address
@@ -999,11 +1022,11 @@ This is entirely optional and is a network preference, not a Taskmaster requirem
 
 If you can't load the Control Panel in your browser:
 
-1. **Same network?** — Make sure your device is on the same WiFi or LAN as Taskmaster
+1. **Same subnet?** — Your phone/laptop and Taskmaster must be on the **same network subnet**. The `.local` address uses mDNS, which only works between devices on the same subnet. Common pitfall: the Pi is plugged into Ethernet while your phone is on WiFi, and your router puts them on different subnets (e.g. `192.168.88.x` vs `192.168.10.x`). Fix: connect the Pi to WiFi instead, or ensure both are on the same network. See "WiFi (Raspberry Pi)" above
 2. **Check the URL** — go to **http://taskmaster.local:18789** (the browser will redirect to HTTPS automatically). If you see a certificate warning, see "Secure Connection (HTTPS)" above
 3. **Wait for boot** — after powering on the device, it takes 2–3 minutes for everything to start. If you just plugged it in, give it a moment
 4. **Try a different browser** — some browsers (especially on older devices) have trouble with `.local` addresses. Try Chrome or Safari
-5. **Use the IP address** — if `.local` doesn't resolve, find the device's IP address on your router and go to `http://<ip-address>:18789` instead
+5. **Use the IP address** — if `.local` doesn't resolve, find the device's IP address on your router's admin page and go to `http://<ip-address>:18789` instead
 
 ### Messages not getting through?
 
@@ -1435,6 +1458,28 @@ A chat button appears in the bottom-right corner of the page. Clicking it opens
 
 You can optionally set colours to match your website: `color` controls the floating chat button, and `bgColor` controls the chat overlay background. If you've set up branding on the Setup page, the widget uses your brand colours automatically — these init options override them if provided.
 
+> **Tip:** On the Setup page, the **Public Chat** status card has a **Widget Code** button that generates the embed snippet for you — just copy and paste it into your website.
+
+### Visitor Verification
+
+By default, anyone who opens the public chat can start a conversation immediately (anonymous mode). If you want to verify visitors before they chat — for example, to collect contact details or reduce spam — you can enable identity verification.
+
+1. Go to the **Setup** page
+2. Find the **Public Chat** status card
+3. Click the settings icon to open the verification settings modal
+4. Choose a verification method:
+
+| Method | How it works | What you need |
+|--------|-------------|---------------|
+| **Anonymous** | No verification — visitors chat immediately | Nothing (default) |
+| **Email OTP** | Visitors enter their email, receive a one-time code | A [SendGrid](https://sendgrid.com) API key and a verified sender (free tier available). The sender address is configured in SendGrid, not in Taskmaster. |
+| **SMS OTP** | Visitors enter their phone number, receive a one-time code | [Twilio](https://twilio.com) account SID, auth token, and a Twilio phone number |
+
+5. Enter your provider credentials — for email, add the SendGrid API key in the **API Keys** section on the Setup page; for SMS, enter Twilio credentials in the SMS Fallback fields
+6. Settings auto-save when you leave each field
+
+Once enabled, visitors must authenticate before they can send their first message. Verified contact details are stored and available to the agent via the `verify_contact` tool, so your assistant knows who it's talking to.
+
 ---
 
 ## Chat Commands