Refresh HiveGrid Cloud reference snapshot
This commit is contained in:
1 parent
5e99e14772
commit
7f88026f79
5955 files changed
+1177325
-188362
No files matched your search
+5
-4
@@ -12,11 +12,11 @@ Use this when a feature performs slow, retryable, external, scheduled, browser-b
|
||||
- Work should continue after a user navigates away.
|
||||
- Usage metering or cleanup must be reliable.
|
||||
|
||||
## Required Manifest Entries
|
||||
## Required ticket contract
|
||||
|
||||
The feature manifest must declare:
|
||||
The owning ticket doc must declare:
|
||||
|
||||
- `integration.workers.required`.
|
||||
- Whether a worker is required.
|
||||
- Queue names from `packages/queue/src/names.ts`.
|
||||
- Job names from `packages/queue/src/payloads.ts`.
|
||||
- Notes about retries, idempotency and cleanup.
|
||||
@@ -31,7 +31,8 @@ The feature manifest must declare:
|
||||
- Jobs should be idempotent or have explicit duplicate protection.
|
||||
- Browser jobs must enforce admin-owned navigation policy.
|
||||
- Failures should be visible to the initiating user or admin.
|
||||
- AI/browser-backed features use `hivegrid.ai-chatbot` and `hivegrid.browser-automation` unless a manifest explicitly justifies a new queue.
|
||||
- Browser-backed features use the existing queue contracts unless the ticket explicitly approves a
|
||||
new queue.
|
||||
|
||||
## Browser-Backed Work
|
||||
|
||||
|
||||
Reference in new issue
Block a user