reprise v1.0.0 — stable documentation & brand release

reprise v1.0.0 — stable documentation & brand release

It is designed for the question infrastructure teams ask during a difficult rollback:

Highlights

• Official logo shipped at docs/logo.svg and featured in the README
• Badge pack with docs, release, license, status, version, category, and pages badges
• Detailed notes for integrators and diligence readers (CHANGELOG, SUPPORT, SECURITY, CONTRIBUTING)
• GitHub Pages documentation surface at https://theworker02.github.io/reprise/
• Stable tag v1.0.0 as the portfolio baseline for this product

What changed in this release

1. Ensured brand mark and README presentation meet portfolio standards.
2. Expanded badge strip with explanatory notes table.
3. Added or refreshed diligence documentation.
4. Published narrative release notes for the 1.0 documentation line.

Verification

• README shows the official logo.
• Badges resolve via shields.io.
• CHANGELOG.md records the 1.0.0 documentation milestone.
• This GitHub Release tag is v1.0.0.

Upgrade / checkout

git clone https://github.com/theworker02/reprise.git
cd reprise
git checkout v1.0.0

Subsequent feature tags may advance beyond 1.0.0; this release remains the documented stable baseline for brand and docs completeness.

Reprise v1.1.0-rc.3 — Visual proof of concept

Reprise v1.1.0-rc.3 — visual proof of concept

v1.1.0-rc.3 is a technically validated release candidate for evaluating Reprise as a backend recovery and compatibility control plane. It adds an inspectable visual proof-of-concept to the existing deterministic acquisition fixture and introduces the revised Reprise identity. This is not a general-availability production release.

Proof of concept

The repository now contains an executable and visual walkthrough of the same recovery path:

1. observe a failing v1.8 backend state;
2. isolate the change boundary using evidence rather than timestamp proximity;
3. reconstruct the compatible v1.7 compound checkpoint;
4. complete six verification checks; and
5. apply the Recovery Guard before emitting a tamper-evident receipt.

Run it locally:

pnpm install --frozen-lockfile
pnpm release:validate
node apps/cli/dist/index.js demo acquisition --json

Expected decisive output:

{
  "checkpointId": "checkpoint-v17",
  "candidateId": "candidate-checkpoint-v17",
  "verification": "verified",
  "guard": "allow",
  "signal": "READY"
}

The proof-of-concept document defines exactly what this fixture proves and, equally importantly, what it does not.

Visual demonstration

The static product site now includes:

• an animated sample state graph showing unsafe v1.8 evidence flowing into a compatible v1.7 candidate;
• a four-frame recovery briefing with keyboard-accessible playback controls;
• a timed visual console that renders the deterministic CLI sequence; and
• a clearly labelled product-fit walkthrough for a branchable Postgres provider.

These are small, inspectable HTML, CSS, JavaScript, and SVG assets driven by deterministic local fixture data. They are not a recording of a live provider operation, and no downloadable video, GIF, archive, or binary artifact is attached to this release.

Identity update

The repository now uses an original return-path R monogram, high-contrast wordmark, dark lockup, and favicon-scale mark. The visual identity is source-controlled SVG, allowing evaluators to inspect it directly and keeping the repository lightweight.

Validation evidence

The full release validation completed successfully:

• frozen pnpm installation;
• TypeScript build;
• lint and type checks;
• 51 automated tests across 13 workspace packages;
• deterministic acquisition fixture with JSON output; and
• workspace-inventory and CycloneDX SBOM generation.

Safety and provider boundaries

• The visual and command-line demos make no network or provider calls.
• The Neon adapter remains mocked-contract tested for documented branch discovery, creation, and explicit cleanup. It has not been exercised against a live Neon account.
• Snapshot/PITR, schema diffing, Functions, Auth, Object Storage, Data API, AI Gateway, and production promotion are not implemented.
• UNKNOWN compatibility blocks recovery by default. The release adds no automatic production mutation path.

Evaluation paths

• Technical README
• Proof of concept
• Capability matrix
• Known limitations
• Neon provider notes
• Acquisition diligence package

Reprise v1.1.0-rc.2

Reprise v1.1.0-rc.2

v1.1.0-rc.2 is a technically validated release candidate for evaluating Reprise as a backend recovery and compatibility control plane. It is not a general-availability production release and it does not expose a production restore or promotion command.

Release focus

This release makes the v1.1 evaluation surface release-consistent and auditable:

• a detailed public README that distinguishes verified capabilities from proposed work;
• a corrected capability matrix that separates the shipped static recovery site from the unshipped operational dashboard;
• Node 22.13+ CI compatibility for pnpm 11.19.0; and
• refreshed SBOM outputs and detailed changelog history.

What evaluators can run today

Reprise provides a deterministic, credential-free recovery scenario that reconstructs an incompatible v1.7 → v1.8 deployment change, identifies a compatible v1.7 compound checkpoint, performs six verification checks, applies the Recovery Guard, and emits a tamper-evident receipt.

pnpm install --frozen-lockfile
pnpm release:validate
node apps/cli/dist/index.js demo acquisition --json

The scenario is local-only. It does not call Neon, provision infrastructure, or mutate production.

Verified capabilities

• typed State Graph with dependency traversal;
• hash-chained append-oriented Change Ledger;
• evidence-based COMPATIBLE, INCOMPATIBLE, and UNKNOWN decisions;
• compound checkpoints with local atomic persistence;
• deterministic Time Machine reconstruction and change-boundary analysis;
• stale-plan Recovery Guard and tamper-evident recovery receipts;
• mocked contract coverage for Neon Management API branch lifecycle operations; and
• deterministic CLI and CI validation paths.

Validation evidence

The release validation succeeded locally and in GitHub Actions:

• frozen dependency installation;
• TypeScript build;
• linting and type checks;
• 51 automated tests across 13 workspace packages;
• deterministic acquisition demo; and
• workspace inventory and CycloneDX SBOM generation.

Important boundaries

• The Neon adapter supports documented branch discovery, creation, and explicit cleanup only. It has not been exercised against a live Neon account.
• Snapshot/PITR, schema diff, Object Storage, Functions, Auth, Data API, AI Gateway, and production promotion are not implemented.
• UNKNOWN compatibility blocks recovery by default; unsupported provider behavior is surfaced rather than simulated.
• The static interactive site and GitHub Pages workflow are included, but repository Pages configuration is required to publish the site.

Evaluation material

• README
• full changelog
• capability matrix
• limitations
• Neon provider notes
• technical diligence package

Compatibility

No recovery semantics, provider capabilities, ledger format, or receipt format changed from v1.1.0-rc.1. This release advances the workspace package version and adds the Node 22.13+ runtime requirement needed by the pinned pnpm release tooling.

Reprise v1.1.0-rc.1

Reprise v1.1.0-rc.1 release notes

New

• Reprise Signal: signed, dimension-by-dimension recoverability posture for an integrity-valid checkpoint.
• Durable local checkpoint repository with atomic persistence.
• Neon Management API adapter for documented branch lifecycle operations, backed by mocked provider contract tests.
• A polished static public site with an interactive deterministic recovery scenario.
• GitHub Actions validation and Pages deployment workflows.
• CycloneDX SBOM generation and expanded acquisition diligence documents.

Release status

1.1.0-rc.1 is not approved for general production use. It is a technically validated release candidate. The remaining gates are listed in docs/V1_LIMITATIONS.md and acquisition/RISK_REGISTER.md.