ls-wf-repository-docs-release-preparation

Use this pipeline package for presentation and quality improvements before sharing. Follow ls-script-docs-authoring for the quality pass, ls-humanize-ai-writing for readability, and ls-github-release-publishing for publishing and README policies and shareability checks. Use the framework docs index to locate the relevant public docs. These skills own the procedures. This pipeline ends with sharing-readiness checks; publishing actions remain with the publishing skill and its gates.

For a GitHub-hosted target, the remote-settings review is a required phase: follow GitHub repository enhancement and run its github-repo audit before declaring the repository share-ready. Build a plan with --policy POLICY.json only from explicit desired policy, review its digest and operation IDs, and apply only that exact authorized subset; then run verification with --plan PLAN.json. The ordinary plan excludes destructive or access-changing operations; each such change needs a separate policy, reviewed plan, digest, and exact operation authorization. Controls without supported typed operations remain report-only. An audit does not authorize a write. If the target is not GitHub-hosted, record that this phase is not applicable and continue with the local sharing checks. The enhancement workflow uses --repository OWNER/REPO and --hostname HOST for the remote identity; global --repo keeps its LocalSetup source-checkout meaning.

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.