@go-labs-sg/bb 2.19.0 → 2.20.0

package/README.md

@@ -181,6 +181,10 @@ New sources are registered against an existing Typeform form ID and always start
 with processing disabled in `COLLECT_ONLY`; creating a source does not call any
 external provider.
 
+Deal-lifecycle retries require Slack and Asana to succeed. Google Calendar is
+attempted afterward; a Calendar failure is logged without failing the overall
+lifecycle operation.
+
 ### Mutation safety
 
 While an estimate email is `QUEUED`, `PROCESSING`, or awaiting provider
@@ -233,6 +237,8 @@ The table below is a behavior index keyed by the compatibility dispatcher's lega
 
 Project and budget query payloads keep the Asana identities explicit: `asanaTaskId` is the Deals task GID, while `asanaProjectGid` and `asanaProjectUrl` identify the operational project created for Won delivery work.
 
+Bill, claim, and quotation mutations accept only suppliers whose approval status is `APPROVED`. An active supplier that is `PENDING_APPROVAL`, `REJECTED`, or `SUPERSEDED` must be approved before it can be used.
+
 | Area | Legacy handler labels (reference only; non-exhaustive) |
 | --- | --- |
 | **Budgets** | `list-budgets` (full payload by default; `--summary` or `--includeDetails false` for slim list), `get-budget`, `get-budget-items`, `get-budget-details`, `get-budget-categories`, `get-budget-versions`, `rename-budget-version`, `restore-budget-version`, `update-budget-status` (`ESTIMATE_ACCEPTED` requires win proof, auto-marks `PITCH` or `LOST` projects `WON`, and auto-creates an Asana Event Ops section from Prompt 5 tasks when enabled; Prompt 5 skips quantity-zero items, combines matching non-GO-internal suppliers, keeps each GO internal item separate, removes generated work that repeats another line item or group, and schedules applicable subtasks relative to the project start date; `--projectStatusOnCommercialRejection PITCH\|LOST` is required when rejecting the only accepted/closed budget on a commercial project), `mark-budget-won` (`<budgetId>` + proof file path; `PITCH` or `LOST` projects become `WON` automatically), `create-budget` / `update-budget` (`--payload`; cloned unavailable lines require `unavailableItemReviewAcknowledged: true`), `delete-budget`, `create-budget-approval` (also sends approval request emails), `create-estimate`, `send-estimate-to-contact-person` (same contact-person email workflow as web), `add-budget-items`, `update-budget-item`, `replace-budget-item`, `approve-unavailable-item-exception` (Lead/Admin), `remove-budget-item`, `reorder-budget-items`, `update-budget-item-supplier`, `mark-budget-items-not-utilized`, `restore-budget-item`, `create-placeholder-bill` (admin recovery), `create-budget-category`, `update-budget-category`, `delete-budget-category`, `update-budget-commission`, `delete-budget-commission`, `update-budget-discount`, `delete-budget-discount` (`--payload` where noted), `upload-budget-attachment` (`<budgetId>` + local file path; uses `attachment.requestBudgetAttachmentUpload` + PUT + `attachment.confirmBudgetAttachment`) |

package/command-manifest.json

@@ -1764,7 +1764,7 @@
 	{
 		"path": ["bill", "create"],
 		"legacyAliases": ["create-bill", "create_bill"],
-		"summary": "Create Bill.",
+		"summary": "Create a bill or claim with an approved supplier.",
 		"globalOptions": [
 			{
 				"name": "--help",
@@ -1810,7 +1810,7 @@
 	{
 		"path": ["bill", "selection", "validate"],
 		"legacyAliases": ["validate-bill-selection", "validate_bill_selection"],
-		"summary": "Validate Bill Selection.",
+		"summary": "Validate the approved supplier and selected bill line items.",
 		"globalOptions": [
 			{
 				"name": "--help",
@@ -2658,7 +2658,7 @@
 	{
 		"path": ["quotation", "create"],
 		"legacyAliases": ["create-quotation", "create_quotation"],
-		"summary": "Create Quotation.",
+		"summary": "Create a quotation with an approved supplier.",
 		"globalOptions": [
 			{
 				"name": "--help",
@@ -2704,7 +2704,7 @@
 	{
 		"path": ["quotation", "update"],
 		"legacyAliases": ["update-quotation", "update_quotation"],
-		"summary": "Update Quotation.",
+		"summary": "Update a quotation with an approved supplier.",
 		"globalOptions": [
 			{
 				"name": "--help",

package/command-reference.md

@@ -322,7 +322,7 @@ Effects: state-change, email.
 
 ## `bb bill create`
 
-Create Bill.
+Create a bill or claim with an approved supplier.
 
 Legacy aliases: `create-bill`, `create_bill`.
 
@@ -330,7 +330,7 @@ Effects: state-change, email, external-write, financial-write.
 
 ## `bb bill selection validate`
 
-Validate Bill Selection.
+Validate the approved supplier and selected bill line items.
 
 Legacy aliases: `validate-bill-selection`, `validate_bill_selection`.
 
@@ -474,7 +474,7 @@ Effects: state-change, delete.
 
 ## `bb quotation create`
 
-Create Quotation.
+Create a quotation with an approved supplier.
 
 Legacy aliases: `create-quotation`, `create_quotation`.
 
@@ -482,7 +482,7 @@ Effects: state-change.
 
 ## `bb quotation update`
 
-Update Quotation.
+Update a quotation with an approved supplier.
 
 Legacy aliases: `update-quotation`, `update_quotation`.
 

package/dist/index.js

@@ -204,8 +204,8 @@ Bills
     isClaimable differentiates the shared bill/claim records: false = bill, true = claim.
   Non-legacy supplier bills from 1 Jul 2026 00:00 SGT require approved quotation coverage linked to every selected line item, independent of the bill supplier, including already-paid bills.
   create-bill-approval <billId>       (also queues approval request emails)
-  create-bill                --payload '<json>'  (bill.create; payload.isClaimable false = bill, true = claim)
-  validate-bill-selection    --payload '<json>'  Check project and supplier validity separately, then verify approved quotation links for each budgetItemId; alreadyPaid never bypasses quotation checks.
+  create-bill                --payload '<json>'  (bill.create; payload.isClaimable false = bill, true = claim; supplier must be APPROVED)
+  validate-bill-selection    --payload '<json>'  Require an APPROVED supplier, then verify approved quotation links for each budgetItemId; alreadyPaid never bypasses quotation checks.
   stage-bill-attachment <projectId> <filePath...> [--file <path>] [--files <csv>]   Upload files before create-bill; returns attachment JSON for attachments/paymentProofAttachments
   cleanup-staged-bill-attachments <projectId> --keys <csv>   Delete unattached staged bill/claim uploads.
   update-bill                --payload '<json>'  (bill.update; must include id)

package/dist/registry/index.js

@@ -194,6 +194,18 @@ const titleCase = (value) => value
 const summaryFor = (legacyTarget) => {
     if (legacyTarget === "whoami")
         return "Show the active API-key identity.";
+    if (legacyTarget === "create-bill") {
+        return "Create a bill or claim with an approved supplier.";
+    }
+    if (legacyTarget === "validate-bill-selection") {
+        return "Validate the approved supplier and selected bill line items.";
+    }
+    if (legacyTarget === "create-quotation") {
+        return "Create a quotation with an approved supplier.";
+    }
+    if (legacyTarget === "update-quotation") {
+        return "Update a quotation with an approved supplier.";
+    }
     if (legacyTarget === "download-customer-invoice-pdf") {
         return "Download a customer invoice PDF when permitted.";
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@go-labs-sg/bb",
-  "version": "2.19.0",
+  "version": "2.20.0",
   "description": "Budget Builder CLI for AI agents — manage budgets, bills, claims, quotations, and customer invoices with explicit workflow previews for sensitive changes.",
   "type": "module",
   "main": "./dist/index.js",

package/role-aware-agent-guide.md

@@ -144,6 +144,8 @@ Do not retry with lower-level upload/request procedures, direct tRPC paths, a di
 
 On `BAD_REQUEST` or `CONFLICT`, re-read the resource before deciding whether to retry. These responses commonly indicate an invalid state transition, stale data, missing evidence, or an integration operation already in progress.
 
+Bill, claim, and quotation mutations accept only suppliers whose approval status is `APPROVED`. An active supplier that is `PENDING_APPROVAL`, `REJECTED`, or `SUPERSEDED` must not be submitted or retried until it is approved.
+
 ## Safe examples
 
 Base user preparing a claim: