bbchops/transcription
1
0
Fork 0
generated from john/python-template
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

V6.1 backups: once more into the breach.
Quality Gate / gate (push) Successful in 2m29s
Details

Browse Source
This commit is contained in:
Jim Lancaster
2026-09-02 10:59:28 -05:00
parent 494f378e48
commit 96bb80d91f
17 changed files with 120 additions and 353 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/instructions/documentation-sync.instructions.md
+1 -1
View File
@@ -15,7 +15,7 @@ Keep docs in sync in the same change whenever implementation alters a documented
2. **Configuration contract**
- `Settings` keys, defaults, required/optional environment values.
- **Required doc update:** `.env.example` and any directly related setup docs.
- **Required doc update:** `.env.production.example` and any directly related setup docs.
3. **User-visible UI behavior**
- Page flow, routes, button/action behavior, labels, status wording, empty/error states.
.github/instructions/services.instructions.md
+1 -1
View File
@@ -145,7 +145,7 @@ durability is separately enforced by
- `Source.raw_transcription` is a projection, not authoritative history.
- Service/UI read paths that touch relationships must be eager-loaded for `lazy="raise"` compatibility.
- If model fields, enums, constraints, indexes, or relationship-loading semantics change, update `docs/schema.md` in the same change.
- If `Settings` fields or defaults change in `src/transcription/config.py`, update `.env.example` in the same change so keys/defaults remain synchronized and no stale settings remain documented.
- If `Settings` fields or defaults change in `src/transcription/config.py`, update `.env.production.example` in the same change so keys/defaults remain synchronized and no stale settings remain documented.
## Schema Drift and Legacy Compatibility Policy