ls-wf-release-publish-readiness v1.0A

Immutable. This exact content never changes and is served at /api/v1/blob/d0cc8ea8a4b0fde2.

---
name: ls-wf-release-publish-readiness
description: Use when running pre-publish checks, version sync, and framework audit before release actions.
metadata:
  version: "1.0"
---

Use this pipeline package to prepare a repo for publishing.
Follow [ls-github-publishing-workflow](../../skills/ls-github-publishing-workflow/SKILL.md)
for publishing readiness, `ls-automatic-versioning` and
[VERSIONING.md](../../docs/VERSIONING.md) for version consistency, then
[ls-framework-audit](../../skills/ls-framework-audit/SKILL.md) for audit checks.
These owners define the procedures. This pipeline prepares readiness evidence;
release actions remain with the publishing skill and its authorization gates.

For a GitHub-hosted release target, complete the required read-only remote
settings audit with [GitHub repository enhancement](../ls-wf-github-repository-settings-audit/SKILL.md)
before reporting publish readiness. If reviewed explicit repository policy
calls for changes, create its plan with `--policy POLICY.json` and review it
separately; apply only the exact authorized plan digest and operation IDs, then
verify the result with `--plan PLAN.json`. Destructive or access-changing
operations are excluded from the ordinary plan and need a separate policy,
reviewed plan, digest, and exact operation authorization. Unsupported controls
remain report-only. A publish
preflight, repository audit, or release authorization does not authorize remote
settings writes. Use `--repository OWNER/REPO` plus `--hostname HOST` for the
GitHub target; global `--repo` continues to select LocalSetup's source
checkout. Keep release tags, assets, and tracked repository changes on the
existing local signed Git and release workflows.

Remote write operations are enabled only on `github.com` while the GitHub
Enterprise Server API-version matrix remains unverified. Audits and reads may
run on other GitHub hosts; requested drift there remains incomplete and
report-only with a compatibility reason. Inventory caveats and ambient token
authorization-visibility findings do not make the requested policy incomplete;
unmet requested-policy values or handoffs do.

## One preparation pass

1. Finish the source slice and run inexpensive audit/version checks plus focused
   tests. Fix identified failures before starting full validation.
2. Update the versioned release record, then run canonical version/document
   generation once for the final source. Preserve generated provenance.
3. Use one authoritative full-suite result for the candidate. Hosted CI may
   supply it; an additional local full suite is not required. Reuse successful
   exact-commit workflow results when that commit reaches main and release.
4. Review the final material diff once. Follow-up fixes require affected checks;
   rerun broader checks only when their inputs or conclusions are invalidated.
5. Publish through the existing signed-tag and artifact verification path.
   Missing CI evidence stops preparation promptly; it does not trigger a second
   full suite inside the publish job. Keep optional model prose and unrelated
   repository-setting repairs off the release dependency path.

Reuse a still-applicable repository audit for unchanged settings; refresh the
affected controls when settings or requirements change. A report-only social
preview handoff does not require rebuilding or retesting software artifacts.