dist: publish provenance-bound RUMBO Agent Operating public profile

[fscfede-beep]

Objective

Publish a public, non-authoritative distribution profile derived from canonical rumbo-agent-operating v0.1.5 without reviving the superseded rumbo-coding-agent-reliability candidate or exposing private runtime topology.

Canonical upstream

• Authority repository: RUMBO-IA/rumbo-control-queue
• Exact upstream commit: 6e3de8017833715e15821f80b2ef691da68cdf09
• Upstream plugin: plugins/rumbo-agent-operating
• Upstream marketplace: rumbo-canonical
• Upstream version: 0.1.5

Public derivative built

• Target repository: RUMBO-IA/Rumbo
• Target branch prepared from main: dist/rumbo-agent-operating-public-v015
• Exact base: d798e226ed5fec35ee995dc422e5aa6067979d43
• Built Git tree: 63641c8362895acd6307899a1cae6aa6d35a7342
• Unpublished commit object: 011e09f1f9588ecdd8bafb3110ed67352ac6365f
• Marketplace: rumbo-public
• Plugin: rumbo-agent-operating-public
• Version: 0.1.5-public.1

The public profile contains six skills. Four are byte-identical public-safe upstream skills; canonical-state-recovery and goal-loop-controller are sanitized to remove private repository preflights; openai-rumbo-reliability is intentionally omitted because it contains private repository/runtime topology. PROVENANCE.json binds the derivative to the exact upstream commit and explicitly grants no canonical-state, execution, or production authority.

Publication blocker reproduced

Both Git Data ref update and Contents API writes were rejected by the repository's existing author/committer email rule. The rule was not weakened. The current GitHub connector cannot specify an approved author/committer email, GDP exposes only a demo workspace, and the authorized desktop host is currently offline.

Expected approved local identity:
293577326+fscfede-beep@users.noreply.github.com (or another already allowlisted identity).

Exact safe publication handoff

When an authorized local Git surface is available:

1. checkout dist/rumbo-agent-operating-public-v015 from exact base d798e226ed5fec35ee995dc422e5aa6067979d43;
2. materialize the built tree/diff represented by commit object 011e09f1f9588ecdd8bafb3110ed67352ac6365f without preserving its rejected connector-generated commit identity;
3. commit once using an existing allowlisted author/committer identity;
4. push the branch without force;
5. open a draft PR to main;
6. require Public privacy gate + RUMBO Public Plugin Validation + Vercel on the same exact head before any promotion decision.

No merge, production promotion, workspace import, or public/global Plugin Directory listing is implied by this issue.

Current classification

PUBLIC_PROFILE_CONTENT=BUILT_AND_READ_BACK
PUBLIC_PROFILE_REF_PUBLICATION=BLOCKED_BY_IDENTITY_RULE
CANONICAL_AUTHORITY=UNCHANGED
PRODUCTION=NO_GO

[fscfede-beep]

Product-surface reconciliation

Fresh OpenAI documentation check confirms the public-profile architecture is product-compatible:

• plugins may contain only Skills and require no app connection;
• workspace admins can import a plugin marketplace from a public or private GitHub repository;
• imported GitHub marketplaces can be synced and governed by workspace installation policy;
• Plugin Directory visibility/listing is a separate product-distribution state from GitHub marketplace availability.

Therefore publication of this mirror has independent value even before any global Plugin Directory listing. The correct sequence remains: publish branch with approved Git identity -> exact-head CI -> draft PR -> no merge until gates are green -> optional managed-workspace import/runtime acceptance -> treat any global directory/verification path as a separate later gate.

Final consistency check: dist/rumbo-agent-operating-public-v015 still points to exact base d798e226ed5fec35ee995dc422e5aa6067979d43; the rejected connector writes left no partial branch state.