@@ -44,32 +44,28 @@ The unscoped `cometapi` package is the primary Node SDK. `@cometapi` is the
4444standard scope for future official scoped packages; do not introduce new
4545official packages under ` @cometapi-dev ` .
4646
47- Before the first remote push:
48-
49- 1 . Apply the accepted identity to package metadata and public documents. Make
50- the Public Preview gate and publish validation require the same normalized
51- ` git+https://github.com/cometapi-dev/cometapi-node.git ` repository value.
52- 2 . Remove ` .github/CODEOWNERS ` and every check, fixture, test, or document that
53- requires it. Do not replace it with an individual owner.
54- 3 . Refactor ` npm run check:public-preview ` to collect and report all violations
55- in one run while returning non-zero if any violation exists. Keep checks for
56- canonical identity, contacts, repository metadata, public-safe language,
57- and standalone content.
58- 4 . Gate scheduled live smoke with a ` LIVE_SMOKE_ENABLED ` repository variable
59- and gate Release Please with ` RELEASE_PLEASE_ENABLED ` . Unset or non-true
60- values must prevent those workflows from running. Leave both disabled
61- throughout Private Remote Validation and leave Release Please disabled
62- through the initial manual alpha.
63- 5 . Run every local offline, package, fixture, compatibility, self-containment,
64- public-content, secret, and workflow-static-validation gate.
65-
66- When authorized, create an empty private repository without generated files,
67- make the sanitized repository content its first commit, push the default
68- branch, and wait for credential-free CI. Do not configure branch or tag rules,
69- Private Vulnerability Reporting, secrets, protected environments, Trusted
70- Publishing, live smoke, tags, releases, or registry publication during the
71- private stage. Record the real CI result and stop before any visibility change,
72- even when all checks pass.
47+ Before requesting visibility-change authorization:
48+
49+ 1 . Confirm the current ` main ` includes every approved private closeout and that
50+ its blocking Node.js 22 and 24 CI checks pass.
51+ 2 . Run the complete local offline, package, fixture, compatibility,
52+ self-containment, public-content, secret, workflow-static-validation, and
53+ Public Preview gates from the final private ` main ` .
54+ 3 . Review open failing dependency-update pull requests before visibility
55+ changes and repair, close, or explicitly defer them with a recorded reason;
56+ do not treat their branch failures as evidence that the current ` main `
57+ failed validation.
58+ 4 . Confirm the repository remains private and that public-only repository or
59+ tag rules, Private Vulnerability Reporting, secrets, protected environments,
60+ Trusted Publishing, live smoke, tags, releases, and registry publication
61+ have not been configured or exercised.
62+ 5 . Record the final private evidence and stop for explicit maintainer
63+ authorization before changing repository visibility.
64+
65+ Private repository creation, the sanitized first history, and the initial push
66+ are complete historical steps and must not be repeated. Their procedure and
67+ evidence belong in ` RELEASING.md ` . Keep Release Please disabled through the
68+ initial manual alpha.
7369
7470## Product Contract
7571
0 commit comments