# Stage 8: awesome-dsh-plugin Submission

Stage 8 submits the published `dsh-control-plane` Bundle to the upstream
`awesome-dsh-plugin` registry. It is a directory submission, not proof of
security endorsement or upstream acceptance. The project must not claim that
it is included until the upstream pull request is merged.

## Scope

- synchronize the maintainer fork from the upstream repository;
- add one generated plugin entry for `Harzva/dsh-control-plane`;
- point the entry at the public GitHub repository and immutable release asset;
- run the upstream schema, README-generation, install smoke-test, and CI
  checks;
- create a reviewable PR without changing the upstream repository directly.

## Submission metadata

- Repository: `https://github.com/Harzva/dsh-control-plane`
- Release: `v0.1.0`
- DSH target: `0.1.0-rc.8`
- Required topic: `dsh-plugin` (added and verified on the public repository).

## Gates

The submission must have a public release, enough public Git history, and the
minimum repository age required by the upstream project. The generated README
must be produced by the upstream generator; hand-edited generated output is
not an acceptable shortcut. The PR description must link to the public release
and state that the Bundle is version-qualified to the inspected DSH contract.

The entry must not contain credentials, local paths, private configuration,
raw Sessions, private knowledge, or claims of official DSH endorsement. CI
failure caused only by the newly-created repository age gate must be recorded
as pending rather than bypassed.

## Review and acceptance

Prepare an ignored, sanitized Stage 8 Review Pack containing the exact entry,
generator diff, test summaries, upstream base/head, and PR URL. Use an
isolated local DSH DeepSeek Pro Profile to review the entry and privacy claims.
The parent Agent must inspect the generated diff and CI result. A created PR is
`submitted`; only an upstream merge is `accepted`.

## Exit criteria

- the generated entry is pushed to a maintainer fork branch;
- the upstream PR is created with the exact base/head recorded;
- local schema, generation, install smoke test, and privacy checks pass;
- the public release and the upstream PR are linked in the review record;
- merge status is reported separately from submission status.