# Release v0.1.0 — Scaffolding 
**Date:** 2026-05-19
**Compare:** `v0.0.0...v0.1.0`

## Summary Title

Initial scaffold for `registry-io`. Repository created on GitHub, standards in place, CI configured, ready for Phase 0.2.0 implementation work.

This crate is being built as a **priority** because multiple downstream portfolio crates depend on it for their notification primitives (config-lib hot reload, fsys journal hooks, audit-trail sink fan-out, DISTRO transaction state changes, hive-server connection lifecycle, metrics-lib exporter notifications, bouncer-io threshold notifications).

## Added

- Repository structure: `src/`, `tests/`, `benches/`, `examples/`, `.dev/`, `.github/`
- `Cargo.toml` with MSRV 1.75, edition 2024, Apache-2.0 OR MIT
- `src/lib.rs` with full REPS lint configuration
- `tests/smoke.rs`
- `benches/registry_bench.rs` (placeholder)
- Canonical `REPS.md` at repo root
- Dual licensing: `LICENSE-APACHE` + `LICENSE-MIT`
- `README.md` with design philosophy and roadmap pointer
- `CHANGELOG.md` in Keep a Changelog format
- `.dev/PROMPT.md` - project context, skill areas, design constraints
- `.dev/DIRECTIVES.md` - performance, lock-free, REPS, API design directives
- `.dev/ROADMAP.md` - production roadmap to 1.0
- `.dev/release/v0.1.0.md` - this file
- `.github/workflows/ci.yml` - cross-platform CI on Node 24
- `rustfmt.toml`, `clippy.toml` - portfolio standard configurations
- `.gitignore`, `.editorconfig` - portfolio standard

## Repository setup

- GitHub repo: https://github.com/jamesgober/registry-io
- Topics: rust, reps, registry, callbacks, observer-pattern, lock-free, event-system
- Default branch: main
- License: Apache-2.0 OR MIT

## Next

Phase 0.2.0 - SyncRegistry Foundation. See `.dev/ROADMAP.md`.

---

**Full Changelog:** https://github.com/jamesgober/registry-io/compare/v0.0.0...v0.1.0