release(v0.6.0): define publishing connector readiness baseline

[egdev6]

Pre-flight checks

• I searched existing issues and this is not a duplicate
• I understand this issue must be approved before implementation starts
• I will not include real Discord IDs, tokens, credentials, screenshots, raw logs, transcripts, or private payloads in public evidence

Problem

v0.6.0 needs a clear release contract that states what the version carries, not only the mechanical develop -> main promotion steps. The previous promotion-style issue (#212) describes how to release, but leaves the version scope implicit in milestone membership.

Without an explicit scope contract, release notes can overclaim capabilities, open milestone issues can be confused with shipped work, and reviewers have to infer which changes are included, deferred, or intentionally out of scope.

Proposed solution

Plan v0.6.0 as the Publishing connector readiness baseline.

This release should publish the fake-first research and safety contract for social publishing connectors, centered on #203, while explicitly avoiding live publishing or production connector claims.

Release scope

v0.6.0 defines the readiness baseline for future social publishing/scheduling from Discord/OpenClaw. It documents connector options, approval boundaries, credential expectations, and fake-first validation proving publish/schedule actions remain blocked before explicit approval.

Included issues

• feat(capability): evaluate social publishing connectors and Buffer integration #203 — Evaluate social publishing connectors and Buffer integration.

Included artifacts

• Social publishing connector research covering:
  • Buffer API
  • direct LinkedIn/X platform APIs
  • browser-assisted publishing
  • community plugins such as zooclaw-social
  • custom OpenClaw plugin option
• Options matrix covering ToS risk, implementation effort, credential handling, approval/security expectations, and audit/rollback implications.
• Proposal-first publishing flow where draft/suggestion is distinct from publish/schedule.
• Explicit approval-before-publish/schedule contract.
• Fake-first fixture for social publishing connector decisions.
• Validator proving publish/schedule intents are blocked before approval.
• Credential storage and rotation notes, without committing real tokens, account data, screenshots, raw logs, transcripts, or private payloads.
• Expected content-ledger update behavior after a future successful publish/schedule.

Deferred / out of scope

• Live publishing.
• Production Buffer integration.
• Real social tokens or account data.
• Signed-in browser automation against real accounts.
• Real scheduling.
• End-to-end publication workflow.
• Production-readiness claims for LinkedIn/X/Buffer publishing.
• Final credential vault/runtime integration.
• Final publish/schedule approval UX.
• Real content-ledger writeback after publication.

Release notes claim boundaries

Allowed claims:

• Adds a fake-first publishing connector readiness baseline.
• Documents Buffer/direct/browser/community/custom connector options.
• Defines approval-before-publish/schedule constraints.
• Adds validation that publication/scheduling remains blocked without explicit approval.

Disallowed claims:

• Adds Buffer publishing.
• Enables social publishing.
• Supports LinkedIn/X publishing.
• Automates posting.
• Is production-ready for social publishing.

Area

CI/Workflows

Acceptance criteria

• feat(capability): evaluate social publishing connectors and Buffer integration #203 is closed and explicitly included in the v0.6.0 release scope.
• Any open issues in the v0.6.0 milestone are either closed before release or explicitly listed as deferred/out of scope.
• docs/releases/v0.6.0.md exists and uses sanitized evidence only.
• Release notes follow the allowed/disallowed claim boundaries above.
• bash scripts/validate-social-publishing-connectors.sh passes.
• bash scripts/validate-release-promotion.sh --base origin/main --head HEAD --force passes for the release PR.
• Release PR targets main and includes only intended release-promotion changes.
• GitHub Release/tag v0.6.0 is created after merge or explicitly documented if deferred.
• Post-release hygiene records included/deferred issues and moves shipped work to the appropriate project status.

Validation plan

• Follow docs/process/release-workflow.md.
• Confirm milestone v0.6.0 - Publishing connector readiness contains only included or explicitly deferred work.
• Run bash scripts/validate-social-publishing-connectors.sh.
• Generate/refresh docs/releases/v0.6.0.md from the release changeset.
• Run bash scripts/validate-release-promotion.sh --base origin/main --head HEAD --force.
• Review release notes for private-data hygiene and claim boundaries.

Additional context

This supersedes #212 as the release contract for v0.6.0. Promotion mechanics remain part of the checklist, but the issue now also defines the version content.

[egdev6]

Scope update: #299 is now a prerequisite/included item for v0.6.0.

Reason: before publishing connector readiness can be useful, DPM needs a private read-only source registry/context ingestion baseline. v0.5.0 only delivered a fake-first source ingestion contract; #299 defines the next step for config/private sources, bounded RSS/web/manual ingestion, provenance, untrusted-content wrapping, and explicit Notion boundaries.

Updated release interpretation for v0.6.0:

1. source registry/read-only ingestion baseline (feat(sources): add private read-only source registry ingestion baseline #299);
2. publishing connector readiness research (feat(capability): evaluate social publishing connectors and Buffer integration #203).