@go-labs-sg/bb 2.44.0 → 2.45.0

package/README.md

@@ -508,6 +508,8 @@ Project and budget query payloads keep the Asana identities explicit: `asanaTask
 
 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.
 
+Admin/Lead users can run `bb supplier approve <supplierId>` to directly re-approve a `REJECTED` supplier even when no pending approval request exists. This appends a new approval record and activity entry with the current responder/time, retains earlier approval and rejection history unchanged, and synchronizes QuickBooks; it does not send a requester reply email. Non-interactive direct re-approval requires `--allow-state-change --allow-external-write`, without `--allow-email`. An archived supplier remains archived and also needs Admin reactivation (`bb supplier reactivate --ids <supplierId>`) before new use. Reactivating alone does not change approval status. For a pending supplier, the command still resolves the current user's assigned request and queues the existing reply email.
+
 | 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

@@ -4795,7 +4795,7 @@
 	{
 		"path": ["supplier", "approve"],
 		"legacyAliases": ["approve-supplier", "approve_supplier"],
-		"summary": "Approve Supplier.",
+		"summary": "Approve a pending supplier request and send a requester reply email, or directly re-approve a rejected supplier as Admin/Lead without a pending request or email. QuickBooks is synchronized; archived suppliers remain archived. Argument: <supplierId>.",
 		"globalOptions": [
 			{
 				"name": "--help",

package/command-reference.md

@@ -833,7 +833,7 @@ Effects: state-change, email.
 
 ## `bb supplier approve`
 
-Approve Supplier.
+Approve a pending supplier request and send a requester reply email, or directly re-approve a rejected supplier as Admin/Lead without a pending request or email. QuickBooks is synchronized; archived suppliers remain archived. Argument: <supplierId>.
 
 Legacy aliases: `approve-supplier`, `approve_supplier`.
 

package/dist/index.js

@@ -8504,7 +8504,8 @@ var assertSensitiveWorkflowConfirmed = async (input) => {
     await confirmCurrentCommand({
       action: input.action,
       target: input.entity,
-      details: input.details
+      details: input.details,
+      effects: input.effects
     });
     return;
   }
@@ -9953,6 +9954,17 @@ async function getSupplierDetails(supplierId) {
   });
 }
 async function approveSupplier(supplierId) {
+  const supplier = await api2.supplier.getSupplierById.query({ id: supplierId });
+  if (supplier.status === ExtendedApprovalStatus.REJECTED) {
+    await assertSensitiveWorkflowConfirmed({
+      action: "Re-approve supplier",
+      entity: `supplier ${supplierId}`,
+      effects: ["state-change", "external-write"],
+      details: supplier.active ? "and sync its details with QuickBooks; append a new approval and retain earlier history; no requester reply email is sent" : "and sync its details with QuickBooks; append a new approval and retain earlier history; it remains archived and no requester reply email is sent"
+    });
+    out(await api2.supplier.reapproveSupplier.mutate({ supplierId }));
+    return;
+  }
   await assertSensitiveWorkflowConfirmed({
     action: "Approve supplier",
     entity: `supplier ${supplierId}`,
@@ -10894,6 +10906,8 @@ var effectsFor = (legacyTarget) => {
 };
 var titleCase = (value) => value.split("-").map((word) => `${word.slice(0, 1).toUpperCase()}${word.slice(1)}`).join(" ");
 var summaryFor = (legacyTarget) => {
+  if (legacyTarget === "approve-supplier")
+    return "Approve a pending supplier request and send a requester reply email, or directly re-approve a rejected supplier as Admin/Lead without a pending request or email. QuickBooks is synchronized; archived suppliers remain archived. Argument: <supplierId>.";
   if (legacyTarget === "search-existing-companies")
     return "Search BB and QuickBooks companies without writes. --query <name> [--page <number>].";
   if (legacyTarget === "use-existing-company")
@@ -11823,7 +11837,7 @@ Approvals
   reject-bill <billId> --reason <text> (also sends requester reply email)
   approve-budget <budgetId>           (also sends requester reply email)
   reject-budget <budgetId> --reason <text> (also sends requester reply email)
-  approve-supplier <supplierId>       (also sends requester reply email)
+  approve-supplier <supplierId>       (approve a pending request, or Admin/Lead re-approve a rejected supplier)
   reject-supplier <supplierId> --reason <text> (also sends requester reply email)
 
 Companies & projects
@@ -12258,7 +12272,7 @@ Waiting for approval\u2026
       }
       configureAccessToken(accessToken);
     }
-    if (!resolvedCommand.isLegacyAlias && cmd !== "create-bill" && cmd !== "import-qbo-customer-invoice" && resolvedCommand.command.effects.length > 0) {
+    if (!resolvedCommand.isLegacyAlias && cmd !== "create-bill" && cmd !== "import-qbo-customer-invoice" && cmd !== "approve-supplier" && resolvedCommand.command.effects.length > 0) {
       await confirmCurrentCommand({
         action: resolvedCommand.command.path.join(" "),
         target: commandConfirmationTarget(resolvedCommand),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@go-labs-sg/bb",
-  "version": "2.44.0",
+  "version": "2.45.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

@@ -25,7 +25,7 @@ The Budget Builder API, not the CLI, makes the final decision. A request may nee
 2. A sufficient current database role: `USER`, `INSIDE_SALES`, `LEAD`, `ACCOUNTING_TEAM`, or `ADMIN`. Pending approval assignment does not preserve decision authority after a role change.
 3. Access to the specific resource, commonly through creator ownership or project assignment as Business Development, Inside Sales, or Project Manager.
 4. A compatible resource state, such as a bill being `DRAFT` or `REJECTED` before editing.
-5. A pending approval record assigned to the current user for approval decisions.
+5. A pending approval record assigned to the current user for request decisions. Direct Admin/Lead re-approval of a rejected supplier does not require a pending request.
 6. Required evidence and consistent related records, such as payment proof, approved quotation coverage, or matching project/budget IDs.
 
 Therefore, two users with the same role can receive different results for the same command and different resource IDs.
@@ -95,7 +95,8 @@ This table highlights the role-sensitive command groups an agent is most likely
 | `bb project hub status`, `bb project hub setup`, and `bb project hub sync` | `ADMIN`, project creator, or project assignment as Business Development, Inside Sales, or Project Manager. Setup and sync also enforce Project Hub lifecycle/readiness checks. |
 | `bb supplier update`, `bb item update`, `bb item category update` | Any active authenticated role. Normal-user supplier edits are submitted for approval by the shared API; item/category edits apply immediately. Human review and provider synchronization can temporarily block further supplier edits/new usage. |
 | Edit/delete a bill or quotation | Usually creator or `ADMIN`, with a supported status. |
-| `bb budget approve`, `bb budget reject`, `bb supplier approve`, and `bb supplier reject` | Current user must be the pending approver and currently have role `LEAD` or `ADMIN`. |
+| `bb budget approve`, `bb budget reject`, and `bb supplier reject` | Current user must be the pending approver and currently have role `LEAD` or `ADMIN`. |
+| `bb supplier approve` | `LEAD` or `ADMIN`. Pending suppliers require an assigned pending request; rejected suppliers can be directly re-approved without one. Re-approval preserves archive state and does not send a requester email. |
 | `bb bill approve` and `bb bill reject` | Current user must be the pending approver and currently have role `ACCOUNTING_TEAM` for the finance/check stage or `ADMIN` for the final approval stage. |
 | `bb quotation approve` and `bb quotation reject` | Current user must be the pending approver and currently have role `ADMIN`; a normal submitter cannot decide the quotation. |
 | `bb bill status update ... CHECKED` | `ACCOUNTING_TEAM` or `ADMIN`. |