From f75e29f90b64e982f56eacc11bcd2a859934ed51 Mon Sep 17 00:00:00 2001 From: Altay Date: Sun, 25 Oct 2026 16:56:00 +0300 Subject: [PATCH] docs: drop docs/distribution.md; release config is the doc --- README.md | 3 ++- docs/distribution.md | 21 ------------------- .../evals/repo-verify-delivery/criteria.json | 4 ++-- .../putio-frontend-dev/references/delivery.md | 4 +--- skills/putio-frontend-dev/references/docs.md | 10 +++++---- skills/putio-sdk-dev/references/release.md | 2 -- 6 files changed, 11 insertions(+), 33 deletions(-) delete mode 100644 docs/distribution.md diff --git a/README.md b/README.md index 7c883a5..a1580a4 100644 --- a/README.md +++ b/README.md @@ -40,6 +40,8 @@ claude plugin marketplace add putdotio/putio-dev-agent-plugin claude plugin install putio-dev@putio ``` +There is no publish pipeline: the marketplace serves `main`. + Codex takes the same marketplace with `codex plugin marketplace add` and `codex plugin add`. The root `plugin.json` follows [Agent Plugins](https://agent-plugins.org) for other clients that install @@ -48,7 +50,6 @@ plugins from Git. ## Docs - [Contributing](CONTRIBUTING.md): setup, skill layout rules, and the verify gate -- [Distribution](docs/distribution.md): consumer ownership and the quality gate - [Skill fleet](docs/skill-fleet.md): the put.io skill inventory ## Security diff --git a/docs/distribution.md b/docs/distribution.md deleted file mode 100644 index be8ac89..0000000 --- a/docs/distribution.md +++ /dev/null @@ -1,21 +0,0 @@ -# Distribution - -This repository is the source of truth for its two skills. Consumers install -them directly from the `skills/` tree with the `skills` CLI, or install the -`putio-dev` plugin from the `putio` marketplace in -`.claude-plugin/marketplace.json`, or through the root `plugin.json` (Agent -Plugins). There is no publish pipeline; the marketplace serves `main`. - -Harness-local and repository-local copies are not sources of truth; re-sync -them instead of editing them. The full owner map, including `putio-cli`, is -the [skill fleet inventory](skill-fleet.md#inventory). - -## Quality gate - -Every pull request, push to `main`, and manual dispatch runs `pnpm run verify` -and an offline check of relative Markdown links and anchors -([workflow](../.github/workflows/verify.yml)). The same job then runs the -shared [scan](https://github.com/putdotio/.github#actionsscan): on a push it -runs Actionlint and Zizmor when the pushed range changes `.github/`, and a -manual dispatch lints every workflow. GitHub secret scanning and push -protection cover secrets in this public repository. diff --git a/skills/putio-frontend-dev/evals/repo-verify-delivery/criteria.json b/skills/putio-frontend-dev/evals/repo-verify-delivery/criteria.json index b0998ba..6cc1de1 100644 --- a/skills/putio-frontend-dev/evals/repo-verify-delivery/criteria.json +++ b/skills/putio-frontend-dev/evals/repo-verify-delivery/criteria.json @@ -18,8 +18,8 @@ "max_score": 2 }, { - "name": "documents_distribution_contract", - "description": "Places release, publishing, or deployment contract details in `docs/distribution.md` with contributor docs linking to it when needed.", + "name": "leaves_release_docs_to_config", + "description": "Leaves release, publishing, and deployment behavior to the workflows and release config, with no `docs/distribution.md`; only a human-only step or must-not-break rule gets a line in `AGENTS.md` or `CONTRIBUTING.md`.", "max_score": 2 }, { diff --git a/skills/putio-frontend-dev/references/delivery.md b/skills/putio-frontend-dev/references/delivery.md index c2bc5ec..8c6684e 100644 --- a/skills/putio-frontend-dev/references/delivery.md +++ b/skills/putio-frontend-dev/references/delivery.md @@ -4,7 +4,7 @@ Workflow detail lives in Notion: [Release workflow mechanics](https://app.notion.com/p/3fdd546ba2f58124966ce3993500204e), [Repo secrets setup](https://app.notion.com/p/3fdd546ba2f5813d8a36fd219d145900), and the Delivery pages in [SKILL.md](../SKILL.md#knowledge-base). Each repo's -`docs/distribution.md` owns its targets, triggers, and gates. +workflows and release config own its targets, triggers, and gates. ## Verify @@ -30,8 +30,6 @@ TypeScript repos use Vite+ (`vp`) with `check`, `build`, `test`, and `verify`. - Jobs that run project code never use `pull_request_target`. - After a delivery change, run the artifact or app smoke check, or record the missing one as a repo gap. -- Update `docs/distribution.md` in the same change when release, cache, - provenance, or signing behavior changes. ## Secrets diff --git a/skills/putio-frontend-dev/references/docs.md b/skills/putio-frontend-dev/references/docs.md index 1acfe60..b1cfaa8 100644 --- a/skills/putio-frontend-dev/references/docs.md +++ b/skills/putio-frontend-dev/references/docs.md @@ -9,10 +9,12 @@ templates live in Notion: - Security reporting follows the [org-wide policy](https://github.com/putdotio/.github/blob/main/SECURITY.md); a repo adds `SECURITY.md` only when its policy differs. -- `docs/distribution.md` owns release and publishing; contributor docs link - to it. Name the durable handoff (tested output, Release asset, registry - package, image digest, provider package), never Actions artifacts. -- Docs use kebab-case names, such as `docs/distribution.md`. Conventional root +- No `docs/distribution.md`: workflows and release config document release + and publishing. A step a human must take or a rule they must not break that + no file states (a store submission, a version pin, a setting outside the + repo) gets a line in `AGENTS.md` or `CONTRIBUTING.md` that links the + workflow. +- Docs use kebab-case names, such as `docs/test-harness.md`. Conventional root files (`README.md`, `CONTRIBUTING.md`, `LICENSE`, `SECURITY.md`, `AGENTS.md`, `CLAUDE.md`) and platform-required names (`.github/pull_request_template.md`, `.github/ISSUE_TEMPLATE/`, `CODEOWNERS`, `SKILL.md`) keep theirs. diff --git a/skills/putio-sdk-dev/references/release.md b/skills/putio-sdk-dev/references/release.md index 34aa525..bdd3d43 100644 --- a/skills/putio-sdk-dev/references/release.md +++ b/skills/putio-sdk-dev/references/release.md @@ -38,5 +38,3 @@ Check live provider settings before claiming a security posture. artifact, not an Actions artifact. Verify the published artifact matches what you inspected, then promote it without rebuilding, and record the commit SHA, tag, package version, artifact digest, workflow run, and published artifact identity. -- **Docs**: release and publishing behavior lives in the repo's - `docs/distribution.md`.