security: freeze legacy install and release before DEN-3944 migration

[ORESoftware]

Problem

Issue #1 correctly identified that the current package can still publish and invokes assets/postinstall.sh, which writes into $HOME/.oresoftware during installation. The legacy shell dispatcher also has no repository-local governance or machine-readable command contract.

Change

• mark the npm package private and add a fail-closed prepublishOnly blocker;
• remove the postinstall package hook so npm installation no longer invokes the home-directory write;
• preserve the historical script as review evidence rather than rewriting history;
• add repository-local AGENTS.md tied to the ORESoftware/my-ai policy;
• declare all ten intended commands in root .cli-flags.toml with unknown options rejected and dry-run as the future default;
• add a migration decision covering consumer inventory, parser/effect boundaries, Zed ownership, adversarial tests, packaging, retirement, rollback, and closure evidence;
• replace the README's apparent endorsement of mutable raw-GitHub installs with an explicit historical/migration warning.

Validation state

The JSON and TOML changes were reviewed structurally against current repository content and the active flags-2-env command-manifest format. No package installation, legacy command, remote Git operation, publication, or hosted CI run was executed through this connector. Keep this pull request draft until exact-head checks and consumer-impact review are attached.

Remaining before #1 can close

This PR intentionally does not replace the shell dispatcher, wire flags-2-env into runtime parsing, add .zpkg.toml, publish a release, archive the repository, or claim consumer compatibility. Those require the issue's inventory, implementation, packaging, and release/retirement gates.

Rollback

Reverting this branch restores the prior package metadata, but release/install side effects should not be re-enabled without the explicit owner review described in the migration decision.

Refs #1 and Linear DEN-3944. No chat-supplied credential was used or copied, and no token was revoked or modified.

[linear-code]

DEN-3944

[ORESoftware]

Validation status — 2026-09-03

No pull-request workflow run is observable for head 7ccf43bbcf943b28b1c035071ec866a69700075d. This is therefore not a green receipt. The PR remains draft.

The reviewed source change removes the npm postinstall invocation, marks the package private, blocks publication, adds the command/migration contract, and preserves legacy source for consumer discovery. Before readiness it still needs exact-head package JSON/TOML validation, isolated install/pack tests, command characterization, consumer inventory, and owner review; no npm/Zed release or archive action was performed.