[v1 readiness] Kratos release gate epic (no version bump)

Goal

Create a v1.0.0 readiness track for JeremyDev87/kratos that excludes version bump/tag/publish work and instead makes the release candidate contract, artifact verification, and documentation evidence executable.

Source of Truth

• Default branch verified as master.

• Open issues and open PRs were empty at planning time.

• Local package manifest showed @jeremyfellaz/kratos with native addon optional dependencies and CLI commands scan, report, clean; npm latest was checked separately.

• TODO.md still lists WOW roadmap slices such as HTML report, sweep, workspace/cache/watch, and docs verification.

• Parent implementation plan artifact: /Users/pjw/.hermes/thread-workcells/discord/282499436049858561/1508085811139051580/TASKS/v1-ddplan-issues/IMPLEMENTATION_PLAN.md

• This is an issue-planning epic only. It must not create branches, commits, PRs, release tags, npm publishes, or version bumps.

Wiki Context Manifest

• Queries attempted: frontend evidence gates release evidence contract, code is not cheap AI maintenance cost ratio, alex core invariants SSoT No Silent Fallback idempotency, 12-factor agents runtime contract event log release workflow, overeager coding agents task scope destructive action, prompt assets skill issue planning evidence
• Wiki sources read: [wiki: frontend/evidence-gates.md], [wiki: principles/code-is-not-cheap.md], [wiki: principles/alex-core-invariants.md], [wiki: harness-engineering/12-factor-agents-runtime-contract.md], [wiki: harness-engineering/overeager-coding-agents-scope-contract.md], [wiki: harness-engineering/prompt-assets.md], [wiki: raw/2026-05-24-ai-maintenance-cost-ratio-source-map.md]
• Relevant wiki facts: v1 readiness requires artifact/runtime/evidence bundles, not only test-green; release and wrapper flows must preserve SSoT, atomicity, idempotency, and No Silent Fallback; destructive or fix-like commands need task-scope/evidence gates; AI-generated velocity must lower future maintenance cost rather than add broad v1 scope.
• remember-wiki applicability / skip reason: skipped; target repos are JeremyDev87/* personal CLI repos, not Remember/dramancompany repos.
• Non-wiki inference: repo-specific split below is based on live local repo docs/config/workflows and npm registry checks performed before issue creation.

Quality Lens Router Output

• Applicable gate families:
  • evidence-contract: v1 readiness, package install, CLI output, release/publish, and fallback claims need concrete proof.
  • simplicity-deletability: v1 work must prefer contract/evidence gaps over broad new features or nonessential abstractions.
  • tdd-systematic-debugging: false-positive, fallback, exit-code, and packaging regressions should be fixture/test-backed.
• Skipped gates:
  • frontend-design: not-applicable; CLI/runtime/docs work only.
  • vercel-agent-skills: not-applicable; no React/Next/Vercel/mobile surface.
  • deploy-token-safety: limited; no token/deploy mutation in this issue, only release credential evidence requirements.

Evidence Contract

• Required evidence:
  • Candidate SHA/version alignment evidence when a candidate is selected.
  • Repo test evidence plus source CLI smoke.
  • npm pack / packed-install evidence for the user-consumed artifact.
  • Release workflow/check/dist-tag/GitHub Release evidence where release automation is touched.
  • Explicit fallback/unsupported-platform evidence where wrapper/native-runtime selection is touched.
• Evidence not applicable:
  • Browser screenshot/DOM: not-applicable, CLI repos.
  • Production URL: not-applicable, npm/GitHub release surface only.
• Blocking evidence gaps:
  • Final v1 version bump/tag is intentionally out of scope for this issue set.

Non-Goals

• No version bump.
• No release tag or npm publish.
• No live CI workflow dispatch unless a child issue explicitly asks for a safe dry-run and the maintainer approves.
• No broad new product scope without evidence that it reduces future maintenance cost.

Issue-PR Strategy

• One PR per child issue by default.
• If two child issues need the same workflow/docs files, sequence them instead of creating conflicting parallel PRs.
• Parent closes only when all child issues are completed or consciously deferred with evidence.

Child issue matrix

Parallelization Decision

• Contract/scope child should run first when it affects downstream acceptance criteria.
• Artifact/CI children can run in parallel with safety/fixture children if file ownership does not overlap.
• Final docs parity child should usually run last, after contract and evidence gates settle.

Completion criteria

• Child issues have live labels and JeremyDev87 assignee.
• Each child issue includes Owned files, Inspect-only files, Must not touch, validation/evidence, and dependency notes.
• Parent matrix links all children.
• No literal Unicode escape sequences are present in issue titles/bodies.