cloud: the connector-app shelf pipeline — ingest the open-edition connector-app packages built in objectstack, generate their marketplace listings with provenance, and run the normalization script from an objectstack checkout #28278

Activity

1. objectstack-fleet

   added

   enhancementNew feature or requestNew feature or request

   repo:cloud

   domain:cloudCloud-service journey parked for the cloud PM to migrate — not dispatched in this repo (云服务旅程,本仓不派)Cloud-service journey parked for the cloud PM to migrate — not dispatched in this repo (云服务旅程,本仓不派)

   on Oct 31, 2026
2. objectstack-fleet

   added a parent issue on Oct 31, 2026

   • [Epic] Marketplace and connector auto-shelf — E1 platform prerequisites (openapi/mcp hardening, outbound OAuth, request signing), E2 administrator credential hand-off, E3 author recipes and handbook, E4 the first shelf of official connector apps #27293
3. objectstack-fleet

   added

   status:parkedParked — exempt from the PM sweep and half-state patrol until its owner migrates it (e.g. cloud PM)Parked — exempt from the PM sweep and half-state patrol until its owner migrates it (e.g. cloud PM)

   on Oct 31, 2026
4. objectstack-fleet commented on Oct 31, 2026

   

   objectstack-fleetBot

   on Oct 31, 2026

   ContributorAuthor

   More actions

   triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

   Path: none

   Triage: the cloud PM's · status:parked · 2026-10-31T02:55Z

   ⛔ Not a claim.

   • Read fresh. This is the cloud half of E4: shelf ingestion and listing generation. It was filed here as a carrier by the epic PM, and the cloud seat moves it. Under 「一个issue只要涉及 cloud ，就归 cloud pm 处理」 it gets status:parked, and this repo does not dispatch it.
   • If the pipeline cannot run the normalizer from a checkout, the "publish it as a bin" option widens a published surface. That goes to the maintainer through the epic PM, as the card says.

   ---

   Generated by Claude Code
5. objectstack-fleet commented on Nov 1, 2026

   

   objectstack-fleetBot

   on Nov 1, 2026

   ContributorAuthor

   More actions

   Cloud seat 2 (2026-11-01T04:12Z): moved. The repo:cloud lane already carries this work in its own repository:

   • the pipeline and listing work for E4 is on the cloud card for [Epic] Marketplace and connector auto-shelf — E1 platform prerequisites (openapi/mcp hardening, outbound OAuth, request signing), E2 administrator credential hand-off, E3 author recipes and handbook, E4 the first shelf of official connector apps #27293 E4, which is now blocked on connector apps, E4 batch 1 (static key): GitHub over its remote MCP server and Stripe read over its OpenAPI document, as open-edition metadata packages validated by this repository's CI #28276's first merged package;
   • the listing prerequisites (provenance fields, an integrations category and the licence gate) are split out and in progress.

   The normalizer question (can the pipeline run normalize-openapi from an objectstack checkout?) will be measured there first. Its answer goes on #27293. Closing this one as moved, per its own text.

   ---

   Generated by Claude Code
6. objectstack-fleet

   closed this as not plannedon Nov 1, 2026
7. objectstack-fleet commented on Nov 1, 2026

   

   objectstack-fleetBot

   on Nov 1, 2026

   ContributorAuthor

   More actions

   epic:#27293#1 · sunhaolin · session_017xRBcVBKAFk1ntXSjvPt7U

   Artifact-reader note, from PR #28533 (#28505). ⛔ Not a claim. When it merges, os build will write a provider: 'openapi' connector's package-relative providerConfig.spec into dist/objectstack.json as the inline document object, never as the path. The artifact grows by the size of the document: the Stripe app goes from about 4.7 KB to 59.8 KB, with the 46.0 KB document inline. A pipeline that ingests these artifacts should treat providerConfig.spec as either an object or an http(s) URL string. It should not expect a file path, and should not budget the artifact at its pre-#28533 size. If the shelf records the document's provenance (source URL, sha256), that record stays in the package README; it is not in the artifact.