ACTIVATION AUDIT: ship-soon

[4444J99]

Identity: Recursive Engine / Generative Entity is a flagship I-plane repo with no public shipping proof.
Frozen-state classification: built-never-deployed
Shipped-test: FAIL: no public endpoint or release artifact is currently visible.

Activation path:

1. Create explicit runtime entrypoint and ensure packaging settings are complete.
2. Add release workflow to generate versioned artifacts from CI and publish them.
3. Add user installation/run guidance and a smoke-check result path in README and seed metadata.

[github-actions]

Marked stale due to inactivity. Will close in 14 days.

[4444J99]

Execution plan

Outcome
Produce a reviewable, evidence-backed disposition for ACTIVATION AUDIT: ship-soon and close #11 only after its acceptance predicate is demonstrably satisfied.

Current scope
Identity: Recursive Engine / Generative Entity is a flagship I-plane repo with no public shipping proof. Frozen-state classification: built-never-deployed Shipped-test: FAIL: no public endpoint or release artifact is currently visible. Activation path: 1. Create explicit runtime entrypoint and ensure packaging settings are complete. 2. Add release workflow t…

Prerequisites / dependencies

• Re-read the default branch and repository-local instructions/governance before editing.
• Confirm this issue is current, uniquely owned, and not superseded; visible cross-references: none stated.
• Convert every stated requirement/checklist item into a concrete acceptance check; record unavailable fixtures, credentials, platforms, or upstream dependencies here.

Bounded work packets (in order)

1. Reproduce or inventory the live state and record the smallest failing or missing predicate for “ACTIVATION AUDIT: ship-soon.”
2. Implement the minimal coherent change on a non-protected branch; keep unrelated cleanup out of scope.
3. Add focused regression tests, static checks, fixtures, and operator/user documentation for the changed behavior.
4. Run repository-prescribed validation and record exact commands, versions, results, and tested commit SHA.
5. Open or update one owning PR linked to ACTIVATION AUDIT: ship-soon #11; resolve exact-head review findings, then use only the authorized merge rail.
6. Attach a completion receipt (merged commit/PR, mapped acceptance evidence, residual risks) and close only when no acceptance item remains.

Verification / acceptance evidence

• Exact-head tests and relevant lint/type/security/build checks pass with logs or stable links.
• Every body requirement maps to code, test, documentation, or an explicit non-code disposition.
• Negative and recovery/rollback paths are exercised where applicable; protected controls are not bypassed.

Human / external gates
This item touches a human/external authority boundary. The responsible owner must supply that decision/evidence; agents may prepare artifacts but must not impersonate approval, rights, credentials, terms acceptance, release, deployment, publication, or submission.

Next action
Perform packet 1 now: re-read the live default branch and turn this issue's present scope into an executable acceptance checklist before changing code.

[4444J99]

@jules Take the bounded artifact-readiness slice of #11 on current main. Packaging and a CLI already exist (pyproject.toml declares package rege and console script rege = "rege.cli:main"), so do not invent a new runtime. Make that existing package verifiably consumable without publishing: add focused installed-artifact smoke coverage, ensure README has exact install/run commands, build wheel+sdist, install the wheel into an isolated environment, and prove a finite non-destructive CLI invocation such as rege --help works from the installed artifact. Repair only minimal packaging/entrypoint defects uncovered by that proof. Do not publish/release/deploy, change credentials/settings, or edit generated AGENTS.md. Open Dependabot PR #32 owns GitHub Actions dependency updates; keep this work disjoint from those workflow lines. Verify python -m pip install -e '.[dev]', the repo's prescribed pytest suite, python -m build, and the isolated wheel/CLI smoke. Open one narrow PR against main linked to #11 and report the tested SHA and artifact-smoke evidence.

[google-labs-jules]

Jules is on it. When finished, you will see another comment and be able to review a PR.

[google-labs-jules]

Ready for a review! A PR has been created.