The linked ticket subject must start with "Estimate - " before an estimate
task is considered complete. Added as criterion [4] in both the hard rules
block and the workflow success criteria block, with a self-correction step
(PUT /tickets/{id}) if the check fails.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Change the linked ticket subject format from "Estimate: <subject>" to
"Estimate - <subject>" per Winter's request for consistent formatting.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@@ -63,7 +63,8 @@ py -c "import datetime; d = datetime.date(YYYY, M, D); print(d.strftime('%A %Y-%
1. Every line item requested by the user has been added to the estimate and price-fixed via PUT (verify with GET /estimates/{id} — check `.estimate.line_items[]`)
2. Every line item has a corresponding private note on the linked ticket (hidden: true, do_not_email: true) containing: item name, source/retailer, cost, retail price, and any markup
3. The estimate total (subtotal + tax) matches the sum of all line items after recalc
4.A bot alert has been posted to #bot-alerts
4.The linked ticket subject starts with `Estimate - ` (verify with GET /tickets/{id} — check `.ticket.subject`). If it does not, PUT the ticket with the corrected subject before reporting done.
5. A bot alert has been posted to #bot-alerts
If any check fails, complete the missing step before reporting done. This rule fires on initial estimate creation AND on every subsequent "add X to the estimate" request. Incident: 2026-05-22, UPS added to estimate #7189 without a ticket note — caught by Winter.
@@ -606,7 +607,7 @@ TICKET_RESP=$(curl -s -X POST "${BASE}/tickets?api_key=${API_KEY}" \
- **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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
