This repository has been archived on 2026-07-08. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
railiance-fabric/workplans/RAIL-FAB-WP-0005-registry-hardening.md

61 lines
1.3 KiB
Markdown

---
id: RAIL-FAB-WP-0005
type: workplan
title: "Registry Hardening"
domain: railiance
repo: railiance-fabric
status: completed
owner: codex
topic_slug: railiance
planning_priority: medium
planning_order: 5
state_hub_workstream_id: "75c64655-9062-46a3-a706-78ad09852cd6"
created: "2026-05-17"
updated: "2026-05-17"
---
# RAIL-FAB-WP-0005 - Registry Hardening
## Goal
Clean up the registry service for continued local use by removing noisy schema
validation warnings, documenting the API contract, and adding a richer
diagnostic endpoint.
## Tasks
### T01 - Schema Resolver Cleanup
```task
id: RAIL-FAB-WP-0005-T01
status: done
priority: high
state_hub_task_id: "178900ba-a2a4-4f93-a1dd-a626c14e8d66"
```
Replace deprecated `jsonschema.RefResolver` usage with the modern referencing
registry API.
### T02 - Registry Status Endpoint
```task
id: RAIL-FAB-WP-0005-T02
status: done
priority: medium
state_hub_task_id: "523f9a35-2285-4b71-915c-9f06698dcc3a"
```
Add a registry `/status` endpoint that reports database path, table counts, and
latest accepted snapshots.
### T03 - API Contract Documentation
```task
id: RAIL-FAB-WP-0005-T03
status: done
priority: medium
state_hub_task_id: "d84ebf13-b90b-4296-8987-fc00ba6183ad"
```
Document the current registry HTTP API surface in one focused reference file.