# CARBON local release checks

This guide validates the current private, local CARBON plugin surface.

## Required checks

1. Validate plugin manifests and every packaged skill.
2. Confirm no public skill, prompt, MCP tool, settings control, or current
   documentation entry exposes a hosted execution workflow.
3. Open protected local settings and verify test credentials, reusable prompt,
   context documents, output detail, browser control, and optional model-review
   settings remain usable.
4. Run a local project analysis and a focused command without service
   credentials.
5. Exercise an approved local browser controller and preserve screenshots,
   console state, network evidence, and unavailable channels honestly.
6. Verify generated tests remain planned until execution produces evidence.
7. Verify converted tests bake only after observed local passes; product
   failures and infrastructure blockers remain drafts.
8. Confirm every command publishes a responsive CARBON report with evidence
   boundaries, remaining risk, and useful next actions.
9. Run `$carbon-human` on a representative project, confirm that it asks a
   small project-specific question set, persists open questions and answers,
   and qualifies later confidence without blocking technical assessment. In its
   protected local workspace, select a quick answer, add a question comment and
   a project note, then verify the refreshed durable HTML snapshot includes the
   recorded context.
10. Build each supported host package and inspect its contents for only the
    intended public skills and documentation.
11. Run `$carbon-feedback` on a representative artifact. Confirm the protected
    local workspace records a rating, response, and note under
    `.carbon/feedback/requests.json`, refreshes its durable report, and does
    not make any network request without an explicitly configured private
    Feedback Service. For the optional service, exercise create → queue/email
    adapter → reviewer capability → feedback response end to end in a private
    environment.

## Release boundary

A passing package contract does not establish product-wide quality. Record
which hosts, adapters, flows, credentials, and destructive paths were not
measured. Never imply that an unavailable integration or execution dimension
passed.
