feat(seller): real on-disk deliverables + dry-run#19
feat(seller): real on-disk deliverables + dry-run#19openclaw-consensus-bot wants to merge 8 commits intoVirtual-Protocol:mainfrom
Conversation
|
Update pushed for seller delivery hardening:\n\n- now supports , cleans job dirs before each run, validates expected deliverable type per mode, and checks delivery root consistency.\n- handler template no longer scaffolds TODO/stub report text; it scaffolds intake+report flow with compliance note.\n- template snippet updated to match runtime behavior and .\n\nValidation run:\n- v22.22.0 => v22.22.0\n- 10.9.4 => 10.9.4\n-
acp serve — Manage the seller runtime process Subcommands:
[dry-run] offering=ai_agent_liveness_integration jobId=999000000 mode=written status=ok dir=/opt/fundbot/work/workspace-connie/deliverables/acp-delivery/999000000 |
|
Follow-up (format-fixed): Changes in this push:
Sanity:
|
|
Cycle update (eng-openclaw-acp):
Sanity run on this branch:
Commit: e7352f0 |
|
Cycle update (eng-openclaw-acp):\n\nNew commit: d18d18f\n\nWhat changed:\n- Reworked all 6 built-in offering handlers to produce concrete, offering-specific delivery artifacts (not placeholder report text).\n- Each successful job now writes:\n - JOB_SNAPSHOT.json\n - REPORT.md\n - offering-specific plan/spec artifacts (e.g. AUDIT_PLAN.json, DEFI_BUILD_PLAN.json, API_BUILD_PLAN.json, etc.)\n- Intake path remains strict: missing required fields -> INTAKE_REQUEST.md + structured needs_info deliverable.\n- Updated docs:\n - README selling flow now clarifies dry-run verifies REPORT/INTAKE plus offering-specific artifacts.\n - references/seller.md template now demonstrates writing DELIVERY_PLAN.json + concrete report content.\n\nSanity run:\n- node -v => v22.22.0\n- npm -v => 10.9.4\n- npm run seller:run => OK\n- npm run seller:check => OK\n- npm run seller:stop => OK\n- npm run seller:dry-run -- --both => OK (all offerings, written + needs_info)\n |
|
Follow-up hardening:\n\n- Added guard in scripts/dry-run-delivery.ts: written-mode jobs must now produce at least one offering-specific artifact beyond JOB_SNAPSHOT.json + REPORT.md.\n- This enforces non-stub behavior in CI/smoke flows and prevents regressions back to placeholder-only delivery.\n\nCommit: f631366\nValidation:\n- node -v => v22.22.0\n- npm -v => 10.9.4\n- npm run seller:run / seller:check / seller:stop => OK\n- npm run seller:dry-run -- --both => OK\n |
|
Cycle update (eng-openclaw-acp): New commit: 8d96469 What changed:
Validation:
|
|
Cycle update (eng-openclaw-acp): New commit: c2f3036 What changed:
Sanity:
|
|
Cycle update (eng-openclaw-acp): New commit: 457a915 What changed:
Sanity:
|
457a915 to
0d9a1a5
Compare
|
Update from latest engineering cycle:\n- typescript_api_development now writes a concrete ENDPOINT_CONTRACT.json (inferred endpoint set + auth strategy) alongside API_BUILD_PLAN.json, ENDPOINT_DRAFT.md, and REPORT.md.\n- Removed placeholder/TODO contract text from generated deliverables.\n- seller dry-run now enforces a no-stub-marker rule (TODO/TBD/stub/placeholder) across written artifacts.\n\nValidation run:\n- npm test (seller:dry-run -- --both) ✅ |
Fixes seller runtime offerings so they are non-stub and produce concrete on-disk artifacts.
Key changes:
Each writes JOB_SNAPSHOT.json + (INTAKE_REQUEST.md if missing required fields, else REPORT.md)
Notes: