chore: restore mark-stable script on the block facade

[AStaroverov]

Problem

The Mark Platforma Block as Stable workflow fails:

ERR_PNPM_NO_SCRIPT  Missing script: mark-stable

But script matched with mark-stable is present in the root of the workspace,
so you may run "pnpm -w run mark-stable"

Failing run

The reusable milaboratory/github-ci/.github/workflows/block-mark-stable.yaml@v4 does:

cd "${BLOCK_PATH}"   # BLOCK_PATH = block (default)
pnpm run mark-stable

block/package.json lost that script in f54d8fe ("SDK Upgrade, fix page title"), during the migration to the new project template. The root mark-stable (turbo run mark-stable) is not a substitute: CI never runs it, and no workspace package implements the turbo task.

Change

Restore mark-stable on the facade, with the same registry coordinates prepublishOnly already uses.

The changeset is intentionally empty: the published block content does not change, this is a repo-side CI script only.

Note

block-tools structure refresh currently strips this script again — the facade rule carries an unconditional removeScript("mark-stable"). A companion PR removes that call: milaboratory/platforma#1790. Merge order does not matter for this PR to fix the workflow, but the script will not stay put until the block-tools change ships.

Greptile Summary

Restores the block-facade script required by the reusable mark-stable workflow without changing published block content.

• mark-stable — A package script that invokes block-tools mark-stable to mark a block release as stable in the configured S3 registry. This PR restores it in block/package.json using the registry coordinates already used for publishing.
• Block facade — The block workspace package from which reusable block workflows execute package scripts. Its script surface now exposes mark-stable again.
• Changeset — Release metadata used to declare package version changes. This PR adds an intentionally empty changeset because the modification affects repository CI behavior rather than published block content.

Confidence Score: 5/5

The PR appears safe to merge because the restored script matches the documented workflow entry point and no actionable defect was identified.

The workflow can again invoke mark-stable from the block facade, while the empty changeset follows the repository’s documented waiver for changes that do not alter published package content.

Important Files Changed

Filename	Overview
block/package.json	Restores the facade-level mark-stable script expected by the reusable workflow, targeting the same registry used by the existing publish script.
.changeset/lucky-pandas-return.md	Adds an intentionally empty changeset so the CI-only script restoration does not request a package version bump.

Sequence Diagram

sequenceDiagram
    participant CI as Mark Stable Workflow
    participant Facade as block/package.json
    participant Tools as block-tools
    participant Registry as S3 Block Registry
    CI->>Facade: pnpm run mark-stable
    Facade->>Tools: "block-tools mark-stable -r <registry>"
    Tools->>Registry: Mark block release stable

Loading

_{Reviews (1): Last reviewed commit: "chore: restore mark-stable script on the..." | Re-trigger Greptile}