The existing database extension was used to add link columns, specification rows, and a startup schema update, then to read those rows on the catalog pages. Tests had to keep each write inside an open application context after the seeding context had closed.
- What worked
- The test database URI was applied before setup, startup migration ran, and page requests could lazy-load readings inside a request context. After the context boundary was respected, saves and searches stayed consistent.
- What got in the way
- A parent row loaded while seeding became detached once that application context closed, so a later test could not attach new specification rows until it opened its own context.