create-mercato-app 0.10.1-develop.8163.1.2bd25666ca → 0.10.1-develop.8165.1.3de4ce96a8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (88) hide show
  1. package/agentic/shared/ai/trackers/github.md +57 -42
  2. package/dist/agentic/guides/module-facts.json +162 -162
  3. package/dist/agentic/guides/module-facts.v2.json +162 -162
  4. package/dist/agentic/guides/modules/agent_orchestrator/index.md +1 -1
  5. package/dist/agentic/guides/modules/ai_assistant/index.md +1 -1
  6. package/dist/agentic/guides/modules/api_docs/index.md +1 -1
  7. package/dist/agentic/guides/modules/api_keys/index.md +1 -1
  8. package/dist/agentic/guides/modules/attachments/index.md +1 -1
  9. package/dist/agentic/guides/modules/audit_logs/index.md +1 -1
  10. package/dist/agentic/guides/modules/auth/index.md +1 -1
  11. package/dist/agentic/guides/modules/availability/index.md +1 -1
  12. package/dist/agentic/guides/modules/business_rules/index.md +1 -1
  13. package/dist/agentic/guides/modules/carrier_inpost/index.md +1 -1
  14. package/dist/agentic/guides/modules/cart/index.md +1 -1
  15. package/dist/agentic/guides/modules/catalog/index.md +1 -1
  16. package/dist/agentic/guides/modules/channel_apns/index.md +1 -1
  17. package/dist/agentic/guides/modules/channel_discord/index.md +1 -1
  18. package/dist/agentic/guides/modules/channel_expo/index.md +1 -1
  19. package/dist/agentic/guides/modules/channel_fcm/index.md +1 -1
  20. package/dist/agentic/guides/modules/channel_gmail/index.md +1 -1
  21. package/dist/agentic/guides/modules/channel_imap/index.md +1 -1
  22. package/dist/agentic/guides/modules/channel_resend/index.md +1 -1
  23. package/dist/agentic/guides/modules/channel_ses/index.md +1 -1
  24. package/dist/agentic/guides/modules/channel_smtp/index.md +1 -1
  25. package/dist/agentic/guides/modules/checkout/index.md +1 -1
  26. package/dist/agentic/guides/modules/communication_channels/index.md +1 -1
  27. package/dist/agentic/guides/modules/configs/index.md +1 -1
  28. package/dist/agentic/guides/modules/content/index.md +1 -1
  29. package/dist/agentic/guides/modules/currencies/index.md +1 -1
  30. package/dist/agentic/guides/modules/customer_accounts/index.md +1 -1
  31. package/dist/agentic/guides/modules/customer_groups/index.md +1 -1
  32. package/dist/agentic/guides/modules/customers/index.md +1 -1
  33. package/dist/agentic/guides/modules/dashboards/index.md +1 -1
  34. package/dist/agentic/guides/modules/data_sync/index.md +1 -1
  35. package/dist/agentic/guides/modules/design_system/index.md +1 -1
  36. package/dist/agentic/guides/modules/devices/index.md +1 -1
  37. package/dist/agentic/guides/modules/dictionaries/index.md +1 -1
  38. package/dist/agentic/guides/modules/directory/index.md +1 -1
  39. package/dist/agentic/guides/modules/documents/index.md +1 -1
  40. package/dist/agentic/guides/modules/ecommerce/index.md +1 -1
  41. package/dist/agentic/guides/modules/entities/index.md +1 -1
  42. package/dist/agentic/guides/modules/eudr/index.md +1 -1
  43. package/dist/agentic/guides/modules/events/index.md +1 -1
  44. package/dist/agentic/guides/modules/feature_toggles/index.md +1 -1
  45. package/dist/agentic/guides/modules/forms/index.md +1 -1
  46. package/dist/agentic/guides/modules/gateway_autopay/index.md +1 -1
  47. package/dist/agentic/guides/modules/gateway_stripe/index.md +1 -1
  48. package/dist/agentic/guides/modules/gateway_tpay/index.md +1 -1
  49. package/dist/agentic/guides/modules/generators/index.md +1 -1
  50. package/dist/agentic/guides/modules/inbox_ops/index.md +1 -1
  51. package/dist/agentic/guides/modules/integrations/index.md +1 -1
  52. package/dist/agentic/guides/modules/messages/index.md +1 -1
  53. package/dist/agentic/guides/modules/notifications/index.md +1 -1
  54. package/dist/agentic/guides/modules/onboarding/index.md +1 -1
  55. package/dist/agentic/guides/modules/payment_gateways/index.md +1 -1
  56. package/dist/agentic/guides/modules/perspectives/index.md +1 -1
  57. package/dist/agentic/guides/modules/phone_calls/index.md +1 -1
  58. package/dist/agentic/guides/modules/planner/index.md +1 -1
  59. package/dist/agentic/guides/modules/portal/index.md +1 -1
  60. package/dist/agentic/guides/modules/progress/index.md +1 -1
  61. package/dist/agentic/guides/modules/promotions/index.md +1 -1
  62. package/dist/agentic/guides/modules/push_notifications/index.md +1 -1
  63. package/dist/agentic/guides/modules/query_index/index.md +1 -1
  64. package/dist/agentic/guides/modules/record_locks/index.md +1 -1
  65. package/dist/agentic/guides/modules/resources/index.md +1 -1
  66. package/dist/agentic/guides/modules/sales/index.md +1 -1
  67. package/dist/agentic/guides/modules/scheduler/index.md +1 -1
  68. package/dist/agentic/guides/modules/search/index.md +1 -1
  69. package/dist/agentic/guides/modules/security/index.md +1 -1
  70. package/dist/agentic/guides/modules/seeds/index.md +1 -1
  71. package/dist/agentic/guides/modules/shipping_carriers/index.md +1 -1
  72. package/dist/agentic/guides/modules/sso/index.md +1 -1
  73. package/dist/agentic/guides/modules/staff/index.md +1 -1
  74. package/dist/agentic/guides/modules/storage_s3/index.md +1 -1
  75. package/dist/agentic/guides/modules/sync_akeneo/index.md +1 -1
  76. package/dist/agentic/guides/modules/sync_excel/index.md +1 -1
  77. package/dist/agentic/guides/modules/system_status_overlays/index.md +1 -1
  78. package/dist/agentic/guides/modules/telemetry/index.md +1 -1
  79. package/dist/agentic/guides/modules/tillio/index.md +1 -1
  80. package/dist/agentic/guides/modules/translations/index.md +1 -1
  81. package/dist/agentic/guides/modules/warranty_claims/index.md +1 -1
  82. package/dist/agentic/guides/modules/webhooks/index.md +1 -1
  83. package/dist/agentic/guides/modules/wms/index.md +1 -1
  84. package/dist/agentic/guides/modules/workflows/index.md +1 -1
  85. package/dist/agentic/guides/reference-module-facts.json +1 -1
  86. package/dist/agentic/guides/upstream/manifest.json +1 -1
  87. package/dist/agentic/shared/ai/trackers/github.md +57 -42
  88. package/package.json +3 -3
@@ -6,9 +6,13 @@ At runtime: `om-setup-agent-pipeline` copies this file into the repository at `.
6
6
 
7
7
  ## Prerequisites
8
8
 
9
- - `gh` CLI installed and authenticated. Verify with the **auth-check** operation before a batch run; fail fast when unauthenticated.
9
+ - `gh` CLI installed and authenticated; `jq` is required for JSON operations. Verify with the **auth-check** operation before a batch run; fail fast when unauthenticated.
10
10
  - All operations accept an optional `{repo}` (`owner/name`); when omitted, `gh` infers it from the current checkout's git remote. Pass `--repo {owner}/{repo}` explicitly whenever a skill operates on a repository other than the current one.
11
11
 
12
+ Older GitHub CLI clients can fail mutation commands when GraphQL requests retired
13
+ Projects (classic) fields. Use the REST examples below for automated writes;
14
+ upgrade `gh` if reads also fail. Do not request `projectCards` in JSON field lists.
15
+
12
16
  ## Conventions
13
17
 
14
18
  - Issue and PR identifiers are numbers; in text they are written `#123`.
@@ -18,54 +22,68 @@ At runtime: `om-setup-agent-pipeline` copies this file into the repository at `.
18
22
  - Long, multi-line comment bodies are posted with `--body-file` (or a heredoc via process substitution) so formatting is preserved.
19
23
  - CI status truth comes from **get-pr-checks**; the set of *required* checks comes from **get-required-checks** (branch protection). When branch protection is not readable (404), treat every reported check as required.
20
24
 
25
+ Before declaring CI green, inspect both **get-pr-checks** and **list-runs** for the
26
+ exact head SHA. A workflow can be queued before any check jobs appear. An unfinished
27
+ workflow is pending even if the currently visible checks passed; missing or unreadable
28
+ required evidence is not a successful check.
29
+
21
30
  ## Label guards
22
31
 
23
32
  Every label mutation goes through an existence guard so a missing label degrades to a logged skip instead of a failure, and `labels.enabled: false` in the config skips label operations entirely.
24
33
 
25
34
  ```bash
35
+ tracker_repo() {
36
+ if [ -n "${REPO:-}" ]; then
37
+ printf '%s\n' "$REPO"
38
+ else
39
+ gh repo view --json nameWithOwner --jq .nameWithOwner
40
+ fi
41
+ }
42
+
26
43
  label_exists() {
27
- gh label list --limit 200 --json name --jq '.[].name' | grep -Fxq "$1"
44
+ tracker_labels=$(gh api --paginate "repos/$(tracker_repo)/labels" --jq '.[].name') || return 1
45
+ printf '%s\n' "$tracker_labels" | grep -Fxq -- "$1"
28
46
  }
29
47
 
30
- # PR labels
31
48
  apply_label() {
32
- if [ "$LABELS_ENABLED" != "true" ]; then return 0; fi
49
+ [ "$LABELS_ENABLED" = true ] || return 0
33
50
  if label_exists "$1"; then
34
- gh pr edit "$2" --add-label "$1"
51
+ gh api --method POST "repos/$(tracker_repo)/issues/$2/labels" -f "labels[]=$1" >/dev/null
35
52
  else
36
- echo "Skipping label '$1' (not defined in this repo). Create it with: gh label create '$1'"
53
+ printf "Skipping undefined or unreadable label: %s\n" "$1" >&2
37
54
  fi
38
55
  }
39
56
 
40
- # Issue labels
41
- apply_issue_label() {
42
- if [ "$LABELS_ENABLED" != "true" ]; then return 0; fi
43
- if label_exists "$1"; then
44
- gh issue edit "$2" --add-label "$1"
45
- else
46
- echo "Skipping label '$1' (not defined in this repo). Create it with: gh label create '$1'"
47
- fi
48
- }
57
+ apply_issue_label() { apply_label "$1" "$2"; }
49
58
 
50
- remove_issue_label() {
51
- if [ "$LABELS_ENABLED" != "true" ]; then return 0; fi
52
- if label_exists "$1"; then
53
- gh issue edit "$2" --remove-label "$1"
54
- fi
59
+ remove_label() {
60
+ [ "$LABELS_ENABLED" = true ] || return 0
61
+ tracker_label_path=$(printf '%s' "$1" | jq -sRr @uri) || return 1
62
+ tracker_remove_result=$(gh api --method DELETE "repos/$(tracker_repo)/issues/$2/labels/$tracker_label_path" 2>&1) && return 0
63
+ case "$tracker_remove_result" in
64
+ *"(HTTP 404)"*) return 0 ;;
65
+ *) printf '%s\n' "$tracker_remove_result" >&2; return 1 ;;
66
+ esac
55
67
  }
56
68
 
57
- # Pipeline labels are mutually exclusive: setting one removes the others first.
69
+ remove_issue_label() { remove_label "$1" "$2"; }
70
+
58
71
  set_pipeline_label() {
59
- if [ "$LABELS_ENABLED" != "true" ]; then return 0; fi
60
- for label in $PIPELINE_LABELS; do
61
- [ "$label" = "$2" ] && continue
62
- gh pr edit "$1" --remove-label "$label" 2>/dev/null || true
63
- done
72
+ [ "$LABELS_ENABLED" = true ] || return 0
73
+ label_exists "$2" || return 1
74
+ printf '%s\n' "$PIPELINE_LABELS" | tr ' ' '\n' | while IFS= read -r tracker_label; do
75
+ [ -n "$tracker_label" ] || continue
76
+ [ "$tracker_label" = "$2" ] || remove_label "$tracker_label" "$1" || exit 1
77
+ done || return 1
64
78
  apply_label "$2" "$1"
65
79
  }
66
80
  ```
67
81
 
68
- When operating on a different repository than the current checkout, add `--repo "$REPO"` to each command inside the guards and check label existence against that repo (`gh label list --repo "$REPO"`).
82
+ Set `REPO=owner/name` for another repository: existence checks and writes resolve
83
+ the same target. Pipeline splitting also works in shells that do not implicitly
84
+ split variable expansions. Read labels back before using them as gate evidence;
85
+ a skipped mutation never proves a label was applied. Removal ignores only a
86
+ missing label (404); permission and transport failures stop the transition.
69
87
 
70
88
  ## Operations
71
89
 
@@ -213,13 +231,13 @@ gh issue comment {issueId} --repo {owner}/{repo} --body "<body>"
213
231
  #### update-issue
214
232
  `{issueId}`, new title and/or body (use a body-file for multi-line bodies). Edits the issue's own fields; does not touch labels or assignees (those have their own operations).
215
233
  ```bash
216
- gh issue edit {issueId} --repo {owner}/{repo} --title "<title>" --body-file <file>
234
+ gh api --method PATCH repos/{owner}/{repo}/issues/{issueId} -f title="<title>" -F body=@<file>
217
235
  ```
218
236
 
219
237
  #### assign-issue / unassign-issue
220
238
  ```bash
221
- gh issue edit {issueId} --repo {owner}/{repo} --add-assignee "<login>"
222
- gh issue edit {issueId} --repo {owner}/{repo} --remove-assignee "<login>"
239
+ gh api --method POST repos/{owner}/{repo}/issues/{issueId}/assignees -f "assignees[]=<login>"
240
+ gh api --method DELETE repos/{owner}/{repo}/issues/{issueId}/assignees -f "assignees[]=<login>"
223
241
  ```
224
242
 
225
243
  #### label-issue / unlabel-issue
@@ -487,15 +505,12 @@ PR_NUMBER=$(gh pr view --json number --jq .number)
487
505
  ```
488
506
 
489
507
  #### update-pr
490
- `{prNumber}`, new title and/or new body → the PR's own title/body rewritten in place (not a comment), e.g. reframing a doc-originated spec PR that grew a feature implementation. Pass whichever of `--title` / `--body-file` changed; omit the other. Use a body file so multi-line bodies survive.
491
- ```bash
492
- gh pr edit {prNumber} --title "<title>"
493
- gh pr edit {prNumber} --body-file <path-or-process-substitution>
494
- ```
495
- If `gh pr edit` silently no-ops in this repo (some GitHub setups do), fall back to the REST API:
508
+ `{prNumber}`, new title and/or new body → the PR's own title/body rewritten in place (not a comment), e.g. reframing a doc-originated spec PR that grew a feature implementation. Patch only the fields that changed; omit the other operation. Use a body file so multi-line bodies survive.
496
509
  ```bash
497
- gh api -X PATCH repos/{owner}/{repo}/pulls/{prNumber} -f title="<title>" -f body="$(cat <path>)"
510
+ gh api --method PATCH repos/{owner}/{repo}/pulls/{prNumber} -f title="<title>"
511
+ gh api --method PATCH repos/{owner}/{repo}/pulls/{prNumber} -F body=@<path>
498
512
  ```
513
+ Omit the title or body operation when that field is unchanged.
499
514
 
500
515
  #### comment-pr
501
516
  `{prNumber}`, body. For long structured comments:
@@ -544,14 +559,14 @@ Fallbacks: for a **private** repo the raw URLs need auth and will not render —
544
559
 
545
560
  #### assign-pr / unassign-pr
546
561
  ```bash
547
- gh pr edit {prNumber} --add-assignee "<login>"
548
- gh pr edit {prNumber} --remove-assignee "<login>"
562
+ gh api --method POST repos/{owner}/{repo}/issues/{prNumber}/assignees -f "assignees[]=<login>"
563
+ gh api --method DELETE repos/{owner}/{repo}/issues/{prNumber}/assignees -f "assignees[]=<login>"
549
564
  ```
550
565
 
551
566
  #### label-pr / unlabel-pr
552
567
  Always through the guards: `apply_label "<label>" {prNumber}` / `set_pipeline_label {prNumber} "<label>"` for the mutually exclusive pipeline group; direct removal:
553
568
  ```bash
554
- gh pr edit {prNumber} --remove-label "<label>"
569
+ remove_label "<label>" {prNumber}
555
570
  ```
556
571
 
557
572
  #### get-pr-diff
@@ -582,9 +597,9 @@ gh pr review {prNumber} --request-changes --body "<body>"
582
597
  GitHub rejects self-approval (reviewing your own PR); surface that instead of working around it.
583
598
 
584
599
  #### merge-pr
585
- `{prNumber}`; squash is the default merge strategy. `--auto` merges when checks pass; `--delete-branch` only when asked.
600
+ `{prNumber}`, `{headSha}` (the reviewed full commit SHA); squash is the default merge strategy. GitHub branch rules remain enforced; this operation has no administrative bypass. `--auto` merges when checks pass; `--delete-branch` only when asked.
586
601
  ```bash
587
- gh pr merge {prNumber} --squash
602
+ gh pr merge {prNumber} --repo {owner}/{repo} --squash --match-head-commit "{headSha}"
588
603
  ```
589
604
 
590
605
  #### mark-pr-ready