openvibers/openvibe.contracts Commits
Contracts 0.181.0: Sites is retired; the estate covers all 50 repositories again (#141)
OP OpenVibers committed 29 days ago · tag v0.181 · 0 files, +0 −0
**Contracts 0.181.0: OpenVibe.Sites is retired, and the estate covers all 50 repositories again.** **Sites retired (plan T11, 2026-10-14):** - **Manifest:** the `sites` service manifest's `status` and `exposure.state` are `retired`, the note says why (nothing deploys it, the repository is archived, tips and vip are parked by Network), and the rollback condition says there is none. - **docs-currency:** `scripts/docs-currency.js` skips a retired service whether or not an old checkout is around, and the summary counts it apart. The ecosystem check now reads `44/44 current, 1 retired skipped`; it reported Sites as eight README gaps before. - **Estate:** in `scripts/estate.js`, a retired service's record is never "deployed", whatever its archived STATUS.json said. **The estate refreshed:** - `docs/ESTATE.md` and `manifests/repositories/` were last generated before ten repositories existed: Actor, Food, Help, Inventory, MediaHub, Play, Quest, Rent, Work and Zone. They are regenerated from current clones (50 records), and the 37 existing records get their current pins. - `estate.js` now follows a symlinked checkout, so an estate root can be assembled from clones kept elsewhere. - `estate.js --check` reports current. **Also:** the 0.180.0 Sources descriptions and changelog named Sources#49; the implementing PR is Sources#51. **Checks:** the suite passes (20,114 checks). `compat.js v0.180.0` finds no breaking changes. `docs-currency.test.js` adds a retired service with a stale checkout (skipped) and the retired count in the summary.
This commit has no diff to show.