# Session Log — 2026-05-22

## User
- **User:** Mike Swanson (mike) — via Discord Bot
- **Machine:** GURU-BEAST-ROG (Discord Bot service)
- **Role:** admin
- **Session Span:** ~2026-05-22 (Discord thread: #What is Stephen Woodford's cell number?)

---

## Session Summary

This session originated from a Discord request in the #botmagic channel from Rob (restricted user, ID: 261978810713505792), who asked for Stephen Woodford's cell phone number. Per access policy, the request was declined for Rob as he is a read-only/informational user with no vault or credential lookup access.

Mike (ID: 264814939619721216) then picked up the thread and directed the bot to look up Woodford in Syncro. A customer search for "Woodford" returned Wooden Bucket Creative (customer ID: 29873088, email: stephen@woodenbucketcreative.com). The account had one contact on file — Edward King (ID: 2663827, noted as "father in law") — but no Stephen Woodford contact and no mobile number on the main profile.

Rob provided clarifying context that Wooden Bucket Creative is owned by Stephen Woodford and that he did not see Edward King when checking the Syncro GUI manually. Mike then provided Stephen's cell number (520-370-5086) and directed the bot to add it to the main Wooden Bucket Creative customer profile.

The customer profile was updated via `PUT /customers/29873088` with `mobile: "5203705086"`. The API response confirmed the update succeeded and revealed the main profile already had the name fields set to "Stephen Woodford" — so the customer is correctly identified in Syncro, just lacked a mobile number. A #bot-alerts post was made confirming the update.

---

## Key Decisions

- Declined Rob's initial request per restricted-user policy (no credential/contact lookups for non-team members).
- Did not attempt to update or rename the Edward King contact — Mike specified to add the number to the main profile, not a contact record.
- Used `PUT /customers/<id>` directly on the customer profile rather than modifying any contact record, per Mike's instruction ("add it to the Woodenbucket main profile").

---

## Problems Encountered

- Initial `/contacts?query=Woodford` search returned the full contacts list (65KB) rather than filtered results — the endpoint does not reliably filter by query. Worked around by parsing the response locally, which returned no Woodford matches.
- The customer record listed "Edward King" as the only contact, which conflicted with Rob's report of not seeing that name in the GUI. No resolution — discrepancy noted but not investigated further. The main profile correctly identifies Stephen Woodford.

---

## Configuration Changes

None.

---

## Credentials & Secrets

- Syncro API key used: Mike's key (`T259810e5c9917386b-52c2aeea7cdb5ff41c6685a73cebbeb3`) — hardcoded in syncro skill per-user block.
- No vault paths accessed this session.

---

## Infrastructure & Servers

- Syncro PSA: https://computerguru.syncromsp.com/api/v1
- Customer record: https://computerguru.syncromsp.com/customers/29873088

---

## Commands & Outputs

```bash
# Customer search
GET /customers?query=Woodford&per_page=25
# -> Wooden Bucket Creative (ID: 29873088)

# Full customer fetch
GET /customers/29873088
# -> One contact: Edward King (ID: 2663827), phone: 602-617-3641, mobile: (empty)

# Mobile update
PUT /customers/29873088
# Payload: {"mobile": "5203705086"}
# Response: confirmed mobile and phone both set to 5203705086, name: Stephen Woodford
```

---

## Pending / Incomplete Tasks

None.

---

## Reference Information

- Wooden Bucket Creative — Syncro customer ID: 29873088
- Stephen Woodford — mobile: 520-370-5086
- Edward King — contact ID: 2663827, phone: 602-617-3641 (father-in-law), email: edking2002@aol.com
- Discord thread: #What is Stephen Woodford's cell number?
- Bot alert message ID: 1507454436711203008

---

## Update: 12:48 PT — interactive session (BEAST): Discord bot config, Syncro #bot-alerts, sync.sh, hooks, memory

> Scope note: this is the **interactive coordinator** session on BEAST (Mike, GURU-BEAST-ROG),
> separate from the Discord-bot session logged above. Work spanned 2026-05-20 → 2026-05-22 in
> one continuous conversation. The earliest piece (Discord bot instruction corrections) is also
> recorded in `projects/discord-bot/session-logs/2026-05-20-session.md`.

### Session Summary
Corrected and extended the ClaudeTools Discord bot's operating rules, built out its user-identity
table, wired Syncro into a Discord activity feed, and fixed two infrastructure bugs (the sync
script and a prompt hook) plus reconciled stale memory after a parallel Syncro overhaul.

The Discord bot work began by reversing the bot's "single turn / never ask questions" rule — the
architecture (`bot/claude/client.py`) keeps one persistent `ClaudeSDKClient` per thread, so
back-and-forth is supported. Added a "headless" constraint (no Chrome/credential/GUI prompts at
the unattended BEAST console) and a Task Loop (identify requester → do work → "anything else?" →
offer Syncro → `/save`). Then pinned Discord IDs for Mike, Howard, and Winter (Winter granted full
access and marked Syncro SME), and added Rob. The bot's `DISCORD_CLAUDE.md` is the agent
system_prompt, loaded once at service start, so every change required `nssm restart
ClaudeToolsDiscordBot`. Verified the bot can both DM (to Mike) and post to a channel (#bot-alerts)
using the bot token via the Discord REST API, without disturbing the live gateway session.

Wired Syncro to post a summary + link to #bot-alerts after every write: added a reusable, soft-
failing helper `.claude/scripts/post-bot-alert.sh` (reads the bot token from the vault, `.env`
fallback) and a "Post to #bot-alerts" section in the `/syncro` skill. This landed alongside Mike's
parallel Syncro overhaul (commits `64a0ba7`/`90748d0`/`ce38304`) that replaced the `timer_entry →
charge_timer_entry` workflow with direct `add_line_item`; the two merged without conflict.

Fixed `sync.sh`: added Phase 5b (copy `.claude/commands/*.md` → `~/.claude/commands/`), which
closed a ~3-week drift where the global command set lagged the repo (e.g. `/syncro` was stale, and
`feature-request`/`forum-post`/`inject-standards`/`shape-spec` were missing globally). Also fixed
the long-standing untracked-only detection bug (switched `git diff-index --quiet HEAD --` to
`[ -n "$(git status --porcelain)" ]` in both the repo and vault blocks) and guarded the change
with a `.gitignore` entry for 54 MB of datto BSOD dumps so the fix wouldn't sweep them into git.

Reconciled the Syncro memory set with the add_line_item switch, fixed the `UserPromptSubmit` hook
(which had been erroring on BEAST and silently swallowing coord messages), and resolved a
contradiction in Rob's Syncro scope (full access granted and revoked simultaneously) — Mike's call:
full Syncro including billing.

### Key Decisions
- **Bot asks questions in plain text, not via AskUserQuestion** — the tool doesn't render in
  Discord; a posted question + the persistent thread session is the mechanism.
- **#bot-alerts helper reads the token from the vault first, `.env` fallback** — so it works on any
  machine (Howard's, DESKTOP), not just BEAST where the `.env` lives. Soft-fails (exit 0) so a
  Discord outage never breaks a Syncro write.
- **Fixed the root cause of command drift in `sync.sh` (Phase 5b)** rather than just re-copying once
  — the automated script had skipped the doc's "copy to global" step entirely.
- **Gitignored the datto dumps instead of letting the sync fix commit them** — 54 MB of binary
  memory dumps don't belong in a config repo; ignoring keeps them as local working files.
- **Reconciled rather than deleted obsolete timer memories** — followed Mike's keep-and-mark-
  SUPERSEDED pattern; `timer_response_shape` retained as HISTORICAL for the rare manual-timer case.
- **Hook now uses `$CLAUDE_PROJECT_DIR`/`$HOME/ClaudeTools` + trailing `true`** — robust on every
  machine and never exits non-zero on a missing script.
- **Rob gets full Syncro incl. billing** (Mike's decision) — removed the contradicting CANNOT line.

### Problems Encountered
- **Global slash commands were ~3 weeks stale** (`/syncro` and others). Root cause: `sync.sh` never
  ran the doc's Phase-3 copy-to-global step. Fixed by adding Phase 5b; verified it synced 8 commands.
- **`UserPromptSubmit` hook exited 1 on every prompt** — it only probed `D:/claudetools` and
  `C:/claudetools`, neither of which exists on BEAST (repo at `C:/Users/guru/ClaudeTools`). The
  failing hook had also been **silently skipping coord-message delivery**; fixing it surfaced a
  previously-undelivered informational message from `Mikes-MacBook-Air/claude-main` (re: radio show
  notes already synced 2026-05-16). Message auto-marked read by `check-messages.sh`.
- **`sync.sh` untracked-only detection bug** — brand-new files with no tracked changes were silently
  skipped. Fixed; required gitignoring the datto dumps first to avoid a 54 MB commit.
- **Rob's Syncro scope self-contradicted** — CAN list granted full Syncro incl. billing, CANNOT list
  forbade billing actions. Surfaced to Mike; resolved to full access.
- **Two pushes rejected (non-fast-forward)** mid-session as DESKTOP pushed concurrently; resolved
  each with `git pull --rebase origin main` then push (clean rebases, no conflicts).

### Configuration Changes
- `projects/discord-bot/DISCORD_CLAUDE.md` — questions-allowed + headless + Task Loop rewrite;
  identity table (Mike/Howard/Winter/Rob IDs); Rob Syncro scope contradiction removed.
- `.claude/scripts/post-bot-alert.sh` — NEW. Posts to #bot-alerts via Discord REST; vault/`.env`
  token resolution; soft-fail.
- `.claude/commands/syncro.md` — "Post to #bot-alerts" section, Hard Rules pointer, billing step 17
  (coexists with Mike's add_line_item overhaul).
- `.claude/scripts/sync.sh` — Phase 5b (commands → global); untracked-only detection fix (repo + vault).
- `.gitignore` — exclude `clients/internal-infrastructure/datto-bsod-case-2026-05-16.zip` + extracted folder.
- `.claude/settings.json` — `UserPromptSubmit` hook command rewritten (`$CLAUDE_PROJECT_DIR`/`$HOME` + `true`).
- Memory: `MEMORY.md` index + `feedback_syncro_timer_first.md` (already by Mike), `feedback_syncro_timer_response_shape.md` (HISTORICAL), `feedback_syncro_labor_type.md`, `feedback_syncro_warranty_product.md`, `project_sync_script_bug.md` (RESOLVED).
- `clients/valleywide/.../D-drive-folders-2026-05-16.csv`, `D-drive-scan-2026-05-16.csv` — committed as client analysis.

### Credentials & Secrets
- No new credentials created or rotated. The Discord bot token is in the vault at
  `projects/discord-bot/bot-token.sops.yaml`, field `credentials.bot_token` (value not reproduced);
  `post-bot-alert.sh` reads it at runtime. Bot `.env` (gitignored) holds `DISCORD_TOKEN` as fallback.

### Infrastructure & Servers
- **Bot service:** `ClaudeToolsDiscordBot` (NSSM, Automatic) on BEAST (GURU-BEAST-ROG); nssm at
  `C:\Users\guru\AppData\Local\Microsoft\WinGet\Links\nssm.exe`; cwd `C:/Users/guru/ClaudeTools`;
  model `claude-sonnet-4-6`; logs `projects/discord-bot/logs/{stdout,stderr}.log`.
- **Discord:** guild Arizona Computer Guru `624663750603046913`; #bot-alerts channel `624710699771232265`.
- **Discord user IDs:** Mike `264814939619721216`, Howard `624667664501178379`,
  Winter `624666486362996755` (@Winter), Rob `261978810713505792`.
- **Syncro:** `https://computerguru.syncromsp.com` (links `/tickets/<id>`, `/customers/<id>`, `/invoices/<id>`).
- **Coord API:** `http://172.16.3.30:8001/api/coord` (messages auto-marked read by the hook).

### Commands & Outputs
- `nssm restart ClaudeToolsDiscordBot` — used after each `DISCORD_CLAUDE.md` change (system_prompt loads at start).
- Bot DM/channel test: `POST /users/@me/channels` then `POST /channels/<id>/messages` (HTTP 200).
- `bash .claude/scripts/post-bot-alert.sh "<msg>"` → `[OK] posted to #bot-alerts (message_id=...)`.
- Hook repro: the old command exited `1` on BEAST; new command exits `0` in all scenarios (verified).

### Pending / Incomplete Tasks
- **`/sync` doc vs `sync.sh` mismatch** — the skill doc says "stage by name, never `git add -A`"
  but the script still uses `git add -A` (gated by `.gitignore`). Harmless now; left for Mike to
  decide whether to align the script or the doc.
- Optional: clean up legacy "time entry" wording in any remaining Syncro memories not touched here.

### Reference Information
- Commits (this interactive session, post-rebase): `c5474cd`, `8a6695b`, `9fb16a7`, `81eea11`,
  `8973229`, `6c47606`, `34a0d73`, `34e61b2`, `a201140`, `0897e5e`, `5facce2`, `8538ddf`, `eda8420`.
- Related DESKTOP commits (Mike, parallel): Syncro overhaul `64a0ba7`/`90748d0`/`ce38304`;
  Rob Limited-Operator buildout `67dd7a4`/`063b209`/`8e8a18c`.
- Helper: `.claude/scripts/post-bot-alert.sh`. Bot rules: `projects/discord-bot/DISCORD_CLAUDE.md`.

---

## Update: 13:10 PT — Syncro estimate workflow + skill update

### User
- **User:** Mike Swanson (mike) — via Discord Bot
- **Machine:** GURU-BEAST-ROG (Discord Bot service)
- **Role:** admin
- **Session Span:** ~13:00–13:10 PT (Discord thread: #Create new test estimate for a i7 workstation from Bestbuy)

### Session Summary

Mike requested a test estimate in Syncro for an i7 workstation sourced from Best Buy with a $200 markup. The bot first searched Best Buy for current i7 desktop listings (web scraping was blocked by Best Buy, so product data was gathered via web search), producing a list of seven candidates across ASUS, Lenovo, and HP covering prices from $649.99 to ~$1,099. Mike selected option #1: ASUS V500 Desktop (V500MVC-I71TB), Intel Core i7, 16GB RAM, 1TB SSD, $649.99 Best Buy price, $849.99 sell price with the $200 markup.

The estimate was created in Syncro under Arizona Computer Guru (internal test account). During line item creation, a Syncro API bug was encountered: POST `/estimates/{id}/line_items` silently ignores `price_retail` for the generic hardware product (32252), creating the line at $0. This was resolved by following the POST with a PUT to the line item endpoint, which correctly set the price to $849.99. A separate total-recalculation issue was also encountered: the estimate's `total` field does not update after line item changes until the estimate itself is touched via a PUT. After the PUT touch, the total correctly showed $849.99 + $73.95 tax = $923.94.

After the estimate was complete, Mike noted that the standard workflow requires every estimate to have an associated ticket with a private (hidden) note containing links. A ticket (#32316) was created under Arizona Computer Guru, a hidden comment was posted with the estimate link, Best Buy product link, and cost breakdown, and the estimate was linked to the ticket via PUT. The skill file was then updated to encode this as a hard workflow requirement, document the hardware line item price bug and fix pattern, update the bot alert format (single post with both ticket and estimate links), and add the estimate URL to the bot-alerts link table.

### Key Decisions

- Selected ASUS V500 (V500MVC-I71TB) as the test unit — lowest price point ($649.99) with current 14th-gen i7, making it the cleanest baseline for estimate testing.
- Used Arizona Computer Guru (customer ID 15353550) as the internal test account rather than creating a dummy customer.
- Followed POST line item with PUT price fix rather than retrying POST with different field names — per hard rules, alternative payload formats are not to be tried; PUT is the documented update path.
- Bot alert for estimates now sends a single message with both ticket and estimate links, per Mike's direction.

### Problems Encountered

- **Best Buy scraping blocked:** WebFetch timed out or socket-closed on all Best Buy product URLs. Resolved by using web search to gather product names, SKUs, and prices from search result snippets and cached review pages.
- **Estimate line item price $0 on POST:** Syncro's POST `/estimates/{id}/line_items` does not apply `price_retail` for hardware product 32252. Resolved with a follow-up PUT to `/estimates/{id}/line_items/{id}` passing both `price` and `price_retail`. Documented in skill as a hard rule with example.
- **Estimate total not recalculating:** After the PUT price fix, GET /estimates still showed total $0.0. Resolved by doing a no-op PUT on the estimate itself (sending the same name) to trigger server-side recalculation. Total correctly updated to $923.94.
- **Ticket + private note not created initially:** The estimate workflow was executed without a ticket, which Mike flagged as missing. Ticket and private note were created after the fact and the skill was updated to make this mandatory going forward.

### Configuration Changes

- **Modified:** `.claude/commands/syncro.md`
  - Estimate section rewritten as a mandatory 4-step workflow (estimate → line items + price fix → ticket + private note → link + bot alert)
  - Documented hardware line item price bug (POST ignores price_retail, requires PUT fix)
  - Documented estimate total recalculation requirement (PUT touch)
  - Bot-alerts link table updated to include estimate URL format
  - Added estimate bot alert example (single post, both ticket and estimate links)

### Credentials & Secrets

- No new credentials. Mike's Syncro API key used (hardcoded in skill): `T259810e5c9917386b-52c2aeea7cdb5ff41c6685a73cebbeb3`

### Infrastructure & Servers

- Syncro PSA: `https://computerguru.syncromsp.com/api/v1`

### Commands & Outputs

```bash
# Estimate created
POST /estimates → estimate ID 23967407, number #7188

# Line item created at $0 (bug)
POST /estimates/23967407/line_items → line_item ID 124969387, price: "0.0"

# Line item deleted and re-added — still $0
DELETE /estimates/23967407/line_items/124969387
POST /estimates/23967407/line_items → line_item ID 124969416, price: "0.0"

# Price fixed via PUT
PUT /estimates/23967407/line_items/124969416 {"price": 849.99, "price_retail": 849.99}
→ price: "849.99" [OK]

# Estimate total recalculated via touch PUT
PUT /estimates/23967407 {"name": "..."} → subtotal: "849.99", total: "923.94", tax: "73.95"

# Ticket created
POST /tickets → ticket ID 110843061, number #32316

# Private note posted
POST /tickets/110843061/comment {"hidden": true} → comment ID 412479047

# Estimate linked to ticket
PUT /estimates/23967407 {"ticket_id": 110843061} → ticket_id: 110843061 [OK]
```

### Pending / Incomplete Tasks

- None. Estimate and ticket both complete and linked.

### Reference Information

- Syncro Estimate #7188: https://computerguru.syncromsp.com/estimates/23967407
- Syncro Ticket #32316: https://computerguru.syncromsp.com/tickets/110843061
- Best Buy product: https://www.bestbuy.com/site/asus-v500-desktop-intel-core-i7-16gb-memory-1tb-ssd-dark-grey/6613707.p
- Customer: Arizona Computer Guru (ID 15353550)
- Skill updated: `.claude/commands/syncro.md`

---

## Update: 13:41 PT — Syncro estimates API: recalculation and private notes workflow

## User
- **User:** Mike Swanson (mike)
- **Machine:** DESKTOP-0O8A1RL
- **Role:** admin
- **Session Span:** ~12:00–13:41 PT (continued from prior context-compacted session)

---

## Session Summary

This session continued from a context-compacted conversation that had built test estimate #7183 on the ACG internal account and documented the Syncro estimates workflow in syncro.md. The first task on resume was adding `/syncro estimate` to the usage table in syncro.md, which had been identified as pending before compaction.

The user reported that estimate #7183 had incorrect totals in Syncro until manually triggering a recalculation in the GUI, and asked whether the API exposed a recalculate endpoint. Testing against a fresh test estimate (#7184) confirmed the stale-total behavior: after using `PUT /estimates/{id}/line_items/{id}` to set hardware prices, the estimate-level `total` and `subtotal` remain at their pre-update values on subsequent GET calls. A `POST /estimates/{id}/recalculate` endpoint returned 404. The fix is a `PUT /estimates/{id}` with any innocuous field (e.g., `{"date": "YYYY-MM-DD"}`), which triggers server-side recalculation — the PUT response and all subsequent GETs then show correct totals. Test estimate #7183 was deleted per user request; #7184 was created and deleted during testing.

The user then raised that Winter (the office manager) attaches private notes with purchase links to each line item on estimates. Investigation found that the estimate model has no notes surface via API: `POST /estimates/{id}/notes` and `/comments` both return 404, and `note`/`private_note`/`notes`/`body` fields passed to `PUT /estimates/{id}` are silently ignored and not stored. The solution is to always create a ticket first and link the estimate to it via `ticket_id`. Private notes can then be added to the ticket using `POST /tickets/{id}/comment` with `hidden: true, do_not_email: true`. A full end-to-end test (ticket #32315 + estimate #7187) confirmed the workflow. A key gotcha discovered during testing: the comment endpoint is `/comment` (singular) — `/comments` (plural) returns 404.

The full verified workflow (ticket → estimate → line items → hardware PUT prices → PUT recalc touch → private notes on ticket) was documented in syncro.md, replacing the prior minimal estimate code example with a complete annotated workflow template.

---

## Key Decisions

- **PUT touch for recalc rather than GET polling:** The PUT approach is synchronous — the response contains correct totals. GET after a PUT touch is also immediately correct. There is no need to poll or retry.
- **Always create ticket before estimate:** No API workaround exists for notes on standalone estimates. The ticket-first requirement is now a hard rule in the workflow, not an optional step.
- **Private notes use `do_not_email: true`:** Prevents Syncro from notifying the customer about internal sourcing notes. Combined with `hidden: true` (staff-only visibility), this matches Winter's workflow intent.
- **`/comment` vs `/comments`:** Discovered empirically — the plural form returns 404, which would silently fail in an automated workflow. Documented prominently in syncro.md.

---

## Problems Encountered

- **`POST /estimates/{id}/recalculate` returns 404:** No dedicated recalculate endpoint. Resolved by discovering the PUT-touch pattern.
- **`POST /tickets/{id}/comments` (plural) returns 404:** Initial test used the plural form by analogy with other REST APIs. The correct Syncro endpoint is `/comment` (singular). Discovered by testing both forms and comparing HTTP status codes.
- **jq parse error on comment POST:** First attempt to parse the comment response failed with `jq: parse error: Invalid numeric literal`. Root cause was the `https://` URL string in the `body` field containing `//` which caused a heredoc/shell expansion issue in the test command. Resolved by removing the URL scheme in the test payload; the actual workflow uses single-quoted heredocs which are safe.

---

## Configuration Changes

**Modified:**
- `.claude/commands/syncro.md` — Three changes:
  1. Usage table: updated `/syncro estimate` description from "Create a new estimate with line items" to "Create ticket + linked estimate with line items and private purchase notes"
  2. Estimates section: replaced minimal code example with full annotated workflow template (ticket → estimate → line items → PUT prices → PUT recalc → private notes)
  3. Added two new documented behaviors: stale-total recalc via PUT touch, and private notes via linked ticket comment endpoint

---

## Credentials & Secrets

- Syncro API key used (Mike's): `T259810e5c9917386b-52c2aeea7cdb5ff41c6685a73cebbeb3` — sourced from `msp-tools/syncro.sops.yaml` in SOPS vault

---

## Infrastructure & Servers

- Syncro PSA API: `https://computerguru.syncromsp.com/api/v1`
- Test customer: ACG internal account (customer_id: 15353550)

---

## Commands & Outputs

```bash
# Confirmed: no recalculate endpoint
POST /estimates/{id}/recalculate  -> 404

# Stale total reproduced
POST /estimates/23967344/line_items  price_retail: 500.00
# -> price: "0.0" (hardware product ignores POST price)
PUT /estimates/23967344/line_items/124967833  {"price": 500.00}
# -> price: "500.0"
GET /estimates/23967344
# -> total: "0.0", subtotal: "0.0"  (STALE)

# PUT touch fixes it
PUT /estimates/23967344  {"date": "2026-05-22"}
# -> total: "543.5", subtotal: "500.0"  (LIVE)
GET /estimates/23967344
# -> total: "543.5", subtotal: "500.0"  (correct on subsequent GETs too)

# Private notes: ticket must exist first
POST /tickets  {"customer_id": 15353550, "subject": "Estimate: ...", "status": "New", "problem_type": "Estimate"}
# -> ticket id: 110841689, number: 32315

POST /estimates  {"customer_id": 15353550, "ticket_id": 110841689, ...}
# -> estimate id: 23967371, number: 7187, ticket_id: 110841689

POST /tickets/110841689/comment  {"subject": "...", "body": "...", "hidden": true, "do_not_email": true}
# -> comment id: 412474488, hidden: true  [OK]

POST /tickets/110841689/comments  (plural — wrong)
# -> 404
```

---

## Pending / Incomplete Tasks

None for this session. Syncro estimate workflow is fully documented and verified.

---

## Reference Information

- syncro.md: `D:/claudetools/.claude/commands/syncro.md` — Estimates section (~line 586)
- Test estimates created/deleted this session: #7183, #7184, #7185, #7186, #7187
- Test ticket created/deleted: #32315 (id: 110841689)
- ACG internal customer: https://computerguru.syncromsp.com/customers/15353550

---

## Update: 14:56 PT — Syncro billing, Instrumental Music Center #32317

### User
- **User:** Mike Swanson (mike) — via Discord Bot
- **Machine:** GURU-BEAST-ROG (Discord Bot service)
- **Role:** admin
- **Session Span:** ~14:45–14:56 PT (Discord thread: #for https://computerguru.syncromsp.com/tickets/110843950)

### Session Summary

Mike provided a summary of onsite work at Instrumental Music Center and requested the ticket be billed. The issue was a failed ethernet port on their front desk machine — the system was flapping between wifi and the bad ethernet adapter, which killed connections to their CRM (AIM). Mike disabled the ethernet adapter, confirmed the system was stable and user-tested, and plans to source a USB-to-Ethernet adapter as a permanent fix.

Ticket #32317 was identified from the URL provided. The customer (Instrumental Music Center, ID 7088508) was confirmed as a prepaid account with 11.0 hours remaining, so onsite labor product 26118 was used at 1.0 hr (no 1.5x multiplier — this was standard onsite billing, not emergency). A resolution comment was drafted via Ollama and confirmed by Mike before execution.

The billing workflow completed in order: comment posted, line item added (1.0 hr @ $175.00), invoice created ($0.00 prepaid, applied 1.0 hr from block), ticket marked Invoiced. Prepay block decremented from 11.0 to 10.0 hours as expected. Bot alert posted to #bot-alerts.

### Key Decisions

- Used product 26118 (Onsite) at 1.0 hr — Mike said "1hr onsite labor," not emergency, despite the ticket subject containing "Emergency." Billed as standard onsite against prepay block.
- Prepaid customer path: product 26118 at actual hours (not 26184 emergency product), per the documented prepaid billing rule.

### Problems Encountered

None.

### Configuration Changes

None.

### Credentials & Secrets

- Syncro API key: Mike's key (`T259810e5c9917386b-52c2aeea7cdb5ff41c6685a73cebbeb3`).
- No vault paths accessed.

### Infrastructure & Servers

- Syncro PSA: `https://computerguru.syncromsp.com/api/v1`
- Ticket: https://computerguru.syncromsp.com/tickets/110843950

### Commands & Outputs

```bash
# Ticket fetch
GET /tickets/110843950 -> #32317, customer_id: 7088508, status: New

# Customer + rate fetch
GET /customers/7088508 -> Instrumental Music Center, prepay_hours: 11.0
GET /products/26118 -> price_retail: 175.0

# Comment posted
POST /tickets/110843950/comment -> comment ID 412495852

# Line item added
POST /tickets/110843950/add_line_item -> line_item ID 42559484, price_retail: 175.0, qty: 1.0

# Invoice created
POST /invoices {ticket_id: 110843950, customer_id: 7088508} -> invoice ID 1650390094, total: 0.0

# Ticket marked Invoiced
PUT /tickets/110843950 {status: "Invoiced"} -> OK

# Prepay verified
GET /customers/7088508 -> prepay_hours: 10.0 (decremented from 11.0) [OK]
```

### Pending / Incomplete Tasks

- Source USB-to-Ethernet adapter for Instrumental Music Center front desk machine (Mike tracking offline).

### Reference Information

- Syncro Ticket #32317: https://computerguru.syncromsp.com/tickets/110843950
- Customer: Instrumental Music Center (ID 7088508)
- Invoice ID: 1650390094
- Prepay remaining: 10.0 hrs
- Bot alert message ID: (posted to #bot-alerts)

---

## Update: 15:17 PT — Syncro estimate #7189 (i5 laptop + UPS) + skill success criteria

### User
- **User:** Winter (@winterguru, ID: 624666486362996755) + Mike Swanson (ID: 264814939619721216) — via Discord Bot
- **Machine:** GURU-BEAST-ROG (Discord Bot service)
- **Role:** Full trust (Winter), admin (Mike)
- **Session Span:** ~15:00–15:17 PT (Discord thread: #create new test estimate for an i5 laptop with 16G...)

### Session Summary

Winter requested a test estimate for an i5 laptop with 16GB RAM, 512GB SSD, and Windows 11 Pro from Best Buy, Amazon, or Newegg. The bot searched all three retailers using headless Chrome (WebFetch was bot-blocked by Best Buy and Amazon). Results surfaced seven options across all three retailers ranging from $329 (ACEMAGIC off-brand, Newegg sale) to $999.98 (Lenovo ThinkPad E16, Best Buy). Winter selected the Lenovo V15 Gen 4 Business Laptop (i5-13420H, 16GB, 512GB NVMe, Win 11 Pro) at $645 from Amazon and requested a $200 markup, putting the retail price at $845.

Estimate #7189 was created in Syncro under Arizona Computer Guru. The hardware line item was added using product 32252 and the price was fixed via PUT (POST ignores price_retail for this product — known bug). A ticket (#32318) was created and linked, and a private note with the estimate link and cost breakdown was added. The estimate total after tax was $918.52.

Winter then requested a CyberPower CP1500AVRLCD3 1500VA/900W UPS be added to the same estimate. The bot searched all three retailers for 1500VA units (Amazon returned clean results; Best Buy and Newegg required Chrome). Options presented included the APC BX1500M ($189.99 Overall Pick) and CyberPower models at $199.95–$239.95. Winter selected the CP1500AVRLCD3 at $199.95 cost and specified a flat retail price of $299.99. The line item was added to the estimate and price-fixed via PUT. Updated estimate total: $1,144.99 subtotal / $1,244.60 with tax.

Winter then asked whether the UPS had been added as a private note on the linked ticket — it had not. The bot had added a note for the laptop at initial creation but omitted a corresponding note when the UPS was added in the second pass. A second private note ("UPS Added to Estimate") was added to ticket #32318 with the UPS cost and retail breakdown.

Mike then directed the bot to add a formal success/fail criteria to the Syncro skill to prevent future omissions: the task is not done until every line item on the estimate has a corresponding private note on the linked ticket, the estimate total is verified, and a bot alert is posted. The rule was added to the Hard Rules section and a step-7 verification block was embedded in the estimate workflow code template.

### Key Decisions

- Used Lenovo V15 Gen 4 from Amazon ($645) over Best Buy options — better price-to-spec ratio, clear Amazon "Overall Pick" designation.
- Winter specified exact retail price of $299.99 for UPS (overriding the calculated 60% markup of $319.92) — honored the explicit override without recalculating.
- Success criteria added as a Hard Rule (top-level, not buried in the workflow) so it fires on both initial creation and subsequent "add item" requests — the exact scenario that failed here.
- Incident note included inline in the hard rule: "2026-05-22, UPS added to estimate #7189 without ticket note — caught by Winter."

### Problems Encountered

- **UPS private note omitted on second-pass add:** The workflow adds a private note at initial estimate creation but did not include a note step when adding subsequent items. Caught by Winter. Resolved by adding the note retroactively and updating the skill to enforce note-per-item as a success criterion going forward.
- **Best Buy and Amazon bot-blocked:** WebFetch returned HTTP 500 / socket closed. Resolved with headless Chrome (`web-fetch-chrome.py`).

### Configuration Changes

- **Modified:** `.claude/commands/syncro.md`
  - Hard Rules: added estimate success/fail criteria (4-point checklist — all items on estimate, all items have private ticket note, totals verified, bot alert posted). Incident reference included.
  - Estimate workflow: added step 7 (verification block) with bash commands to GET estimate line items and GET ticket hidden comments for comparison, plus a 4-point completion checklist.

### Credentials & Secrets

- Syncro API key: Mike's key (`T259810e5c9917386b-52c2aeea7cdb5ff41c6685a73cebbeb3`). No vault paths accessed.

### Infrastructure & Servers

- Syncro PSA: `https://computerguru.syncromsp.com/api/v1`
- Estimate: https://computerguru.syncromsp.com/estimates/23967587
- Ticket: https://computerguru.syncromsp.com/tickets/110847587

### Commands & Outputs

```bash
# Customer search
GET /customers?query=Arizona+Computer+Guru -> ID 15353550

# Estimate created
POST /estimates -> estimate ID 23967587, number #7189, status: Fresh

# Laptop line item — $0 on POST (known bug)
POST /estimates/23967587/line_items {product_id: 32252, price_retail: 845.00} -> price: "0.0"
PUT /estimates/23967587/line_items/124973048 {price: 845.00, price_retail: 845.00} -> price: "845.0" [OK]

# Ticket created
POST /tickets {customer_id: 15353550, subject: "...", do_not_email: true} -> ticket ID 110847587, #32318

# Private note (laptop)
POST /tickets/110847587/comment {hidden: true, do_not_email: true} -> comment ID 412497088 [OK]

# Estimate linked to ticket + recalc
PUT /estimates/23967587 {ticket_id: 110847587} -> subtotal: "845.0", total: "918.52", tax: "73.52"

# UPS line item
POST /estimates/23967587/line_items {product_id: 32252, price_retail: 299.99} -> price: "0.0" (bug)
PUT /estimates/23967587/line_items/124973169 {price: 299.99, price_retail: 299.99} -> price: "299.99" [OK]

# Recalc after UPS
PUT /estimates/23967587 {name: "..."} -> subtotal: "1144.99", total: "1244.60", tax: "99.61"

# UPS private note (added retroactively after Winter caught omission)
POST /tickets/110847587/comment {subject: "UPS Added to Estimate", hidden: true} -> comment ID 412497901 [OK]
```

### Pending / Incomplete Tasks

None. Estimate, ticket, and both private notes complete. Skill updated.

### Reference Information

- Syncro Estimate #7189: https://computerguru.syncromsp.com/estimates/23967587
- Syncro Ticket #32318: https://computerguru.syncromsp.com/tickets/110847587
- Customer: Arizona Computer Guru (ID 15353550)
- Lenovo V15 Gen 4 — Amazon, $645 cost, $845 retail
- CyberPower CP1500AVRLCD3 — Amazon, $199.95 cost, $299.99 retail
- Estimate subtotal: $1,144.99 | Total with tax: $1,244.60
- Skill updated: `.claude/commands/syncro.md` (Hard Rules + workflow step 7)
- Bot alert message IDs: 1507505776221094060 (estimate), 1507506879792939048 (UPS update), 1507507122286362656 (ticket note)

---

## Update: 15:28 PT — Estimate ticket subject prefix rule + success criteria

### User
- **User:** Winter (@winterguru, ID: 624666486362996755) + Mike Swanson (ID: 264814939619721216) — via Discord Bot
- **Machine:** GURU-BEAST-ROG (Discord Bot service)
- **Role:** Full trust (Winter), admin (Mike)
- **Session Span:** ~15:20–15:28 PT (Discord thread: #create new test estimate for an i5 laptop with 16G...)

### Session Summary

Winter directed the bot to enforce a standard subject line format for estimate-linked tickets: always start with `"Estimate - "` followed by the estimate subject. The syncro.md skill was updated — the estimate ticket creation payload changed from `"subject": "Estimate: <subject>"` (colon) to `"subject": "Estimate - <subject>"` (dash). The change was committed (commit `11647cb`).

Winter then requested that ticket #32318 (created in the prior session without any prefix) be updated retroactively. The current subject was confirmed as `"Lenovo V15 Gen 4 Laptop - i5 / 16GB / 512GB / Win 11 Pro"`. After Winter confirmed the proposed new subject, a PUT updated it to `"Estimate - Lenovo V15 Gen 4 Laptop - i5 / 16GB / 512GB / Win 11 Pro"`. Bot alert posted to #bot-alerts.

Mike then asked why the subject was wrong the first time. The answer: the prefix rule (`"Estimate: <subject>"`) was already in the skill when the ticket was created — the bot simply did not follow it. Bot execution error, not a missing rule.

Mike then directed the prefix check to be added as a formal success criterion. The rule was added in two places in syncro.md: (1) the Hard Rules "Estimate task success criteria" block as criterion [4] (with a self-correction step: PUT the ticket subject if the check fails), and (2) the inline workflow checklist at step 7 as `[4]`. Bot-alert criterion renumbered to [5]. Committed (commit `e9dac65`).

### Key Decisions

- Subject prefix uses a dash (`Estimate - `) not a colon — Winter's explicit format preference.
- Self-correction included in the success criterion: if the subject check fails at completion time, the skill corrects it with a PUT before reporting done rather than just surfacing a warning.
- Criterion added to both the Hard Rules block (fires on every estimate, catches add-item requests) and the inline workflow checklist (enforces at completion time) for redundancy.

### Problems Encountered

- None this sub-session. Root cause of the original missing prefix was bot non-compliance with an existing rule.

### Configuration Changes

- **Modified:** `.claude/commands/syncro.md`
  - Estimate ticket creation payload: `"Estimate: <subject>"` → `"Estimate - <subject>"` (commit `11647cb`)
  - Hard Rules: estimate success criteria block — added criterion [4] (ticket subject starts with `Estimate - `, self-correct if not); bot-alert criterion renumbered to [5]
  - Estimate workflow step 7 checklist: added `[4]` (ticket subject check); bot-alert renumbered to `[5]` (commit `e9dac65`)

### Credentials & Secrets

- Syncro API key: Mike's key (`T259810e5c9917386b-52c2aeea7cdb5ff41c6685a73cebbeb3`). No vault paths accessed.

### Infrastructure & Servers

- Syncro PSA: `https://computerguru.syncromsp.com/api/v1`
- Ticket #32318: https://computerguru.syncromsp.com/tickets/110847587

### Commands & Outputs

```bash
# Ticket subject before
GET /tickets/110847587 -> subject: "Lenovo V15 Gen 4 Laptop - i5 / 16GB / 512GB / Win 11 Pro"

# Subject corrected
PUT /tickets/110847587 {"subject": "Estimate - Lenovo V15 Gen 4 Laptop - i5 / 16GB / 512GB / Win 11 Pro"}
-> .ticket.subject: "Estimate - Lenovo V15 Gen 4 Laptop - i5 / 16GB / 512GB / Win 11 Pro" [OK]
```

### Pending / Incomplete Tasks

None.

### Reference Information

- Commits: `11647cb` (subject format: colon → dash), `e9dac65` (success criteria: subject check)
- Ticket #32318: https://computerguru.syncromsp.com/tickets/110847587
- Skill: `.claude/commands/syncro.md`
- Bot alert message ID: 1507509925939777709