- the config metadata route now serves the official enum vocabularies
read from the documents collection schema (placeholder excluded)
instead of the rule-derived vocabularies (US-31, US-37)
- new superuser-only route POST /api/archivist/fields/{field}/values
registers a value on an enum field's select list, the action behind
the dashboard's add-a-value entry; the template field is refused
- the pipeline and the full correction register new enum values before
the record save validates them
- enum fields become PocketBase select columns created with a single
'-----' placeholder; the special template field starts with the
configured template names (US-03, US-37)
- new enums.go owns the value lists: EnsureEnumValues registers new
values before a record save validates them, CleanupEnumValues runs at
startup and keeps only the values a document uses (placeholder kept
only while alone), template forced to the configuration
- setup_test.go now asserts the select columns and the cleanup
Both collections are created programmatically, so PocketBase's default
created/updated autodate fields were absent and the admin UI showed no
creation/modification dates. Declared explicitly on documents (re-added
each start like the other fixed columns, protected from the config
cleanup) and on document_events at creation. The authoritative history
remains document_events.
US-22: the PocketBase UI edits one field at a time with no preview of
the final name, so a field edit now persists the values with no template
evaluation, no re-filing and no status change; the corrected event carries
the field diff alone. The full correction (all fields, dry-run, re-filing,
validation) moves to the custom dashboard (US-3x).
US-24: deleting a documents record deletes the S3 object at file_key first;
the cascade delete removes the history. Spec, hooks, E2E updated together.
fix(docs): update Garage image version in README and architecture documentation
fix(e2e): change default Garage image version in e2e tests and improve directory handling
fix(s3): skip adding inbox directory markers in S3 listing
fix(main): set HTTP address argument correctly for the application
AppendEvent now reduces the before/after snapshots to the changed keys:
identical values on both sides are omitted, a key on one side only is an
addition or a deletion. The imported, corrected and validated payloads all
follow the same rule (an import is a diff from nothing, a validation keeps
carrying the status alone). arch.md section 4 updated accordingly.