@rezti/dsh-rez-publish

Understanding draft (F.FIVE → Kelvin), updated after your review. Requirements: docs/全平台发布需求.md

A sub-package of @rezti/dsh-rez-suite — like odoo / sso / vision / wechat / tapd / gsc. Users only install the suite; we add this package to the suite's dependencies and bump its version. Nobody adds it on its own.

dsh plugin --profile web add @rezti/dsh-rez-suite@<next version>

From source, link it after @rezti/dsh-rez-odoo and @rezti/dsh-rez-nextcloud.

Odoo is reached through @rezti/dsh-rez-odoo, identity through @rezti/dsh-rez-sso. Adapters touch neither directly.

One PCP feeds two pipelines, sharing assets and product IDs:

| Pipeline | Room | Job | Phase 1 | |---|---|---|---| | ① Product | 电商 | ListingJob | Alibaba.com | | ② Multimedia | 发布 | MediaJob | social distribution |

Tools

| Tool | Does | Gate | |---|---|---| | publish.pcp.assemble | Build a PCP from Odoo + Nextcloud | read-only | | publish.pcp.validate | Fail on missing main image / SKU / wrong company | read-only | | publish.listing.links | List all links on a SKU | read-only | | publish.listing.preview | Channel payload; works even when links exist | read-only | | publish.media.preview | Topic suggestions + copy | read-only | | publish.listing.submit | Real listing | asks, refuses by default | | publish.media.submit | Push the chosen topic | asks, refuses by default | | publish.job.status | Job state, external URL | read-only | | publish.kb.retrieve | Search the Dify publish KB | read-only, fails clearly if not ready |

Submits go through tools/pre-execute and into dsh-rez-token-manager. Logs keep summaries only — no tokens, no full quotations.

Pipeline ① — Product (Odoo → Alibaba.com)

Room 电商 · src/channels/listing/alibaba-icbu.ts

• Mapping product.template → ICBU (title, category, images, specs), documented in docs/publish/alibaba-icbu-mapping.md
• Checks category valid, required attributes, banned words, image count and size
• Preview a payload you can read line by line. The real listing API is not called
• Submit refuses without confirmation. Price never changes automatically — it comes only from the Odoo price list
• Inventory Odoo → Alibaba, dry-run first, never the reverse. With several links, which listings get stock is configurable
• Connector reuse a ready-made one or workctl; if we build our own you get a comparison table first

Write back to Odoo (…001243) after a successful listing:

• key = company + SKU + channel + external listing ID, one row per link
• same SKU, same channel may have many rows
• an existing link never blocks a new one — associate is the default and adds
• update changes only the row you name; listing.links lists them all
• no Studio fields on product.template

Odoo has no channel model today, so we create one — with your written OK first.

Amazon reuses the same 1:N mapping when there is an account. Not phase 1.

Pipeline ② — Multimedia (social)

Room 发布 · src/channels/media/, one file per channel · our main delivery (PR-C …001157)

Not one post per product. We take selling points out of the product info (constant pressure, constant flow…) and the AI suggests topics and copy. Generated content carries no price and no image or video.

| Step | Who | What | |---|---|---| | 1 | AI | Reads selling points from PCP + knowledge base → suggests topics + copy | | 2 | You | Pick a topic | | 3 | You | Upload pictures / videos | | 4 | Person | Confirm → push | | 5 | System | Finished content goes into the Dify KB for reuse |

media.preview produces the topics and copy; media.submit pushes the chosen one. Both need a person. Phase 2: creative generated through Comfy UI + the knowledge base.

No stable API on a channel → preview the copy, export a zip/list, a person posts it from that platform's back office. Steps per channel go here as we build them.

Launch channels (you asked us to name them — please confirm or change):

| API | Export, person posts | |---|---| | Facebook Page · Instagram Business · LinkedIn · X · WeChat Official Account | Douyin 抖音 · Xiaohongshu 小红书 · Bilibili · WeChat Channels 视频号 |

One platform can hold several accounts. For example 凯文_智能家居 and 雷泽智能_小雷 on Xiaohongshu are both added, and you pick which account to push to.

Dashboard (PR-F …001239)

Part of this package's delivery. A standalone board inside Harness — not the settings page, not a separate site — fed by this plugin. Shows: People (Odoo + WeCom bots for 发布 / 电商), media connections, e-commerce (Alibaba phase 1, Amazon later), RAG (Dify KB ready or not), Inbox boundary, inventory / links. No secrets, no hardcoded green lights.

Dify publish KB (PR-E …001237)

Two datasets on the existing Dify: standards and publish. No second Dify, no other vector store. Inbox / RAW files that are not finally reviewed are not indexed.

Keys

Names only, values never in Git: REZ_ODOO_TOKEN, REZ_PUBLISH_ALIBABA_APP_KEY, REZ_PUBLISH_ALIBABA_APP_SECRET, REZ_PUBLISH_DIFY_ENDPOINT, REZ_PUBLISH_DIFY_API_KEY.