chore(docs): delete two stale copies of the forge schema #24

Merged

peterswimm merged 1 commit from chore/delete-db-schema-doc into main

2026-10-23 04:01:43 +00:00

peterswimm commented

2026-10-23 03:38:30 +00:00

Owner

Scope

Deletes two stale copies of the forge schema and stops the generator writing one back (wish f54927ee, which retires drifted copies of spel's schema across five repos).

docs/db-schema.md (1085 lines): a table-by-table dump of spel's core and compliance schemas, taken from the live DB on 2026-03-09 and never regenerated.
- No reader in spel, ritual-engine, forge-ops or forge-api.
- In this repo, only the generator that wrote it names it.
- forge-registry-auditor names neither file.
docs/DATABASE_SCHEMA 2.md: a Finder duplicate from 2025-10-02. It describes a forge database on PostgreSQL 17 + Citus with 41 tables, none of which matches the forge today.
extract_db_docs.py: drops extract_schema_tables and the schema section, so make extract cannot bring the copy back. Its header points at the spel-schema artifact (.../generic/spel-schema/latest/manifest.json names the current version). The event and intent catalogs are registry rows, not schema, and stay.

Testing

pytest: 18 passed, 1 xfailed.
tools/check_schema_registry.py: OK.

Impact Statement

Existing features: make extract no longer writes docs/db-schema.md.
Public APIs / contracts: No expected impact. The OpenAPI/AsyncAPI specs are untouched.
Schemas: No expected impact.
Data / artifacts: two generated docs removed.
Integrations: No expected impact.
Mappings: No expected impact.
Backward compatibility: anyone reading docs/db-schema.md should read the spel-schema artifact instead.

Docs

extract_db_docs.py's header says where the schema lives now.

Follow-up, not in this PR: 4 core.lore rows (2 still fresh) are sourced from the old ~/.spel/api-spec/docs/{db-schema,DATABASE_SCHEMA 2}.md paths, last synced 2026-04. They should be superseded.

## Scope Deletes two stale copies of the forge schema and stops the generator writing one back (wish f54927ee, which retires drifted copies of spel's schema across five repos). - **`docs/db-schema.md`** (1085 lines): a table-by-table dump of spel's core and compliance schemas, taken from the live DB on 2026-03-09 and never regenerated. - No reader in spel, ritual-engine, forge-ops or forge-api. - In this repo, only the generator that wrote it names it. - `forge-registry-auditor` names neither file. - **`docs/DATABASE_SCHEMA 2.md`**: a Finder duplicate from 2025-10-02. It describes a `forge` database on PostgreSQL 17 + Citus with 41 tables, none of which matches the forge today. - **`extract_db_docs.py`**: drops `extract_schema_tables` and the `schema` section, so `make extract` cannot bring the copy back. Its header points at the `spel-schema` artifact (`.../generic/spel-schema/latest/manifest.json` names the current version). The event and intent catalogs are registry rows, not schema, and stay. ## Testing - `pytest`: 18 passed, 1 xfailed. - `tools/check_schema_registry.py`: OK. ## Impact Statement - Existing features: `make extract` no longer writes `docs/db-schema.md`. - Public APIs / contracts: No expected impact. The OpenAPI/AsyncAPI specs are untouched. - Schemas: No expected impact. - Data / artifacts: two generated docs removed. - Integrations: No expected impact. - Mappings: No expected impact. - Backward compatibility: anyone reading `docs/db-schema.md` should read the `spel-schema` artifact instead. ## Docs `extract_db_docs.py`'s header says where the schema lives now. **Follow-up, not in this PR:** 4 `core.lore` rows (2 still `fresh`) are sourced from the old `~/.spel/api-spec/docs/{db-schema,DATABASE_SCHEMA 2}.md` paths, last synced 2026-04. They should be superseded.

peterswimm added 1 commit

2026-10-23 03:38:30 +00:00

chore(docs): delete two stale copies of the forge schema

PR policy check / policy-gate (pull_request) Successful in 0s

Details

CI / schema-registry (pull_request) Successful in 15s

Details

26fc1983e9

docs/db-schema.md was a table-by-table dump of spel's core and compliance
schemas, taken from the live DB on 2026-03-09 and never regenerated. Nothing
reads it. The other four repos (spel, ritual-engine, forge-ops, forge-api)
never name it. In this repo, only the generator that wrote it does.
forge-registry-auditor names none of these files. Its lore row is sourced from
~/.spel/api-spec/docs/db-schema.md, a path that no longer exists, and was last
synced 2026-04-03. Deleting the file does not change that row.

docs/DATABASE_SCHEMA 2.md is a Finder duplicate from 2025-10-02. It describes a
`forge` database on PostgreSQL 17 + Citus with 41 tables, none of which matches
the forge today. Only docs/DOCS_REVIEW_AND_CLEANUP 2.md mentions it, as prose.

extract_db_docs.py no longer writes the schema section, so `make extract`
cannot bring the copy back. Its header points at the spel-schema artifact,
which spel publishes on every merge that changes schema/schema.sql. The event
and intent catalogs are registry rows, not schema, and stay.

Wish f54927ee.

peterswimm merged commit 6dde43d989 into main

2026-10-23 04:01:43 +00:00

peterswimm referenced this pull request from a commit

2026-10-23 04:01:43 +00:00

Merge pull request 'chore(docs): delete two stale copies of the forge schema' (#24) from chore/delete-db-schema-doc into main

peterswimm deleted branch chore/delete-db-schema-doc

2026-10-23 04:01:43 +00:00