Repository navigation
0.1.230 — Document Register cleanup
Resulting behavior
The PDFium Gate Document Register keeps its schema-aware Choose columns
control, including empty and alternative status views. The unrelated native
Obsidian Properties chooser is hidden only for the current
pdfium-document-register instance. Other Bases views retain it.
The native control is in a sibling .bases-header, outside .bases-view.
Ownership is checked through the enclosing Bases .view-content. Local
observation reconciles delayed/replaced chrome and view switching; unload
disconnects observation, invalidates queued work and removes owned markers.
Ambiguous or unsupported DOM shapes leave the native control visible.
Temporary UI reporting, the copy button, its report generator, clipboard
handling and all 21 associated translation entries have been removed.
Permanent DOM/lifecycle and column-picker regressions remain in the check pipeline.
Example installation creates PDF Dokumentregister.base only at the Vault
root when missing. It no longer installs or restores a second real register in
the example folder. The duplicate repository example snapshot is removed;
the canonical root-register generator remains. Two pedagogical native Bases,
six synthetic records and the example README remain. Existing root registers,
historical copies, legacy Bases, PDFs and metadata are not automatically
overwritten, moved or deleted.
New register view names use the selected UI language. Existing user-owned Base
files and labels remain untouched. Stored visibility, sorting, filtering,
inline editing, permanent metadata identifiers and values are preserved.
Evidence and scope
Final local 0.1.230 practical confirmation — 19 October 2026
The user confirmed all seven practical tests passed for the final local
0.1.230 candidate:
- Obsidian displays PDFium Gate 0.1.230.
- The Vault-root Document Register opens normally.
- Obsidian's general Properties (Egenskaper) chooser is hidden in the register.
- PDFium Gate's Choose columns (Velg Kolonner) works.
- Copy UI diagnostics (Kopier UI-diagnose) has been removed.
- Other Bases views retain their Properties button.
- The register works after switching between Bases views.
This is user-reported practical confirmation of the final local candidate;
Codex did not access the Vault or repeat these tests.
Earlier 0.1.229 evidence (historical)
The user had separately reported all six practical Obsidian checks passed on
2026-10-19 for the earlier local 0.1.229 register-cleanup build, including correct
native-control identification/marking, local observer ownership and unaffected
other Bases views. Those six checks remain historical evidence for 0.1.229;
they are not the seven final 0.1.230 results above. The confirmed functional
synchronizer is retained unchanged.
The observed DOM, the wrong-container failure and the schema/identity boundary
are permanently documented in
Document Register architecture.
The regression contract
covers future changes and Obsidian upgrades; synthetic DOM tests do not replace
practical testing in Obsidian.
The aggregate local diff was reviewed before versioning. It contains the register,
column/localization and example-installation work described above, its tests and
documentation. Existing AGENTS.md edits and the unrelated temporary patch script
pdfium-gate-register-ryddig-ui-bevar-agents.cjs are preserved locally.
Both are excluded from the proposed release commit; including AGENTS.md
requires separate approval. Neither belongs in the three-file plugin ZIP.
Later staging must use an explicit file selection, not git add -A.
Manifest/package/lockfile, versions.json and the renderer version are aligned on
0.1.230. Plugin ID remains pdfium-gate, minimum Obsidian remains 1.13.7.
There are no new dependencies or metadata/storage migrations beyond the existing
0.1.228 contract. Its older downgrade/restore limitations remain unchanged.
Verification and release status
Required local verification is npm.cmd --logs-max=0 run check and
git diff --check, including deterministic build, native Properties/column
regression, example installation, existing metadata/runtime checks and complete
coverage of all seven official locales.
Previously reported local verification on 2026-10-19: 21/21 pipeline stages
passed with exit 0,
including nine native Properties/column groups, ten retained disk-migration
scenarios, example-installation preservation, existing register editing and
730 keys at 100% coverage in each of the seven locales. Runtime verification
reported deterministicBuild: true and rootOnlyLoad: true; generated
main.js is 4,597,612 bytes. The initial sandbox run stopped at main.js
writing with EPERM; the complete scoped run passed outside the sandbox.
A final targeted search found no temporary register-report code, key/button
labels or old test references in production source, generated runtime, tests
or active documentation. Existing non-target files and AGENTS.md retained
their protected local preparation hashes.
This documentation follow-up changes no production code or version files and
does not rerun the build or project tests. The 21/21 result above belongs to the
reported local candidate. No GitHub Actions verification for 0.1.230 has been
performed or claimed at this point.
This is a local candidate, not a published release. No commit, push, merge, tag,
archive or GitHub Release is created by this preparation. Subsequent GitHub runtime,
immutable archive and publication verification follows RELEASE.md;
Community preview remains optional. Historical release notes and archives are
not rewritten.