0.1.228

0.1.228 release candidate

Prepared on 2026-10-13 on feature/0.1.228-email-bundles. This is a candidate, not a published release.

Changes

• New EML/MSG imports use one self-contained YYYY-MM-DD - EPOST- Subject folder with a namesake parent PDF, direct attachments and flattened ZIP members. Collisions apply the same suffix to folder and PDF. Existing imports retain their paths; manual ZIP import preserves archive directories.
• Email staging arrival reconciliation handles create, startup and focus through the serialized queue; first-run inventory prevents historical mass import and unchanged failed sources do not cause repeated prompts.
• Archive/parent-link read-back handles bracket-containing member names. Attachment rollback removes only attempt-owned files/records and reports failures.
• Author and Published online metadata fields use a controlled one-time schema upgrade, retain existing identities and disabled states, and preserve deletion after the migration marker is written.
• Factory labels follow UI language while user labels remain unchanged. HTTP(S) URLs are clickable, changed invalid URLs produce localized validation errors and unchanged legacy URLs survive edits to other fields. Register Enter/Escape behavior remains covered.

Verification and scope

Previously completed verification, reported by the owner: 19/19 automated controls passed, 10/10 disk migration scenarios passed, and deterministic build passed. These are prior results, not newly executed by this documentation update.

Practical testing on 2026-10-13: isolated candidate points 1–6 OK, user-confirmed; author and source_url practically approved. Email import, ZIP handling and other approved functions were previously confirmed and are covered by passing automated controls. No additional manual repetition tests are part of this preparation. Practical testing of the entire 0.1.228 candidate is not exhaustive.

Final post-version verification on 2026-10-13: npm.cmd --logs-max=0 run check completed once outside the sandbox with exit code 0, all 19/19 pipeline steps passed, 10/10 disk scenarios passed and deterministicBuild: true. The initial sandbox attempt stopped at runtime writing (EPERM on main.js) before tests started. Generated main.js: 4,589,563 bytes. Expected diagnostics from six injected disk faults were verified successful recovery scenarios. No manual Obsidian tests were run in this preparation.

Compatibility

The schema version remains 1 but accepts the new migrations.author_source_url_v1 extension. Older 0.1.227 contracts reject migrations. Returning to 0.1.227 after schema migration is not guaranteed and may require a compatible schema backup; preserve subsequent schema edits separately. Synthetic compatible-schema restoration passed; whole-plugin downgrade is untested. Process crashes, simultaneous faults and recovery failure are outside the verified scope.

Plugin identity remains pdfium-gate. No existing email folders, metadata UUIDs or record identities are migrated by the EPOST layout change.

Gate before merge

After push, run the mandatory Community Review branch / preview scan against the exact candidate SHA and record date, SHA, complete result and disposition of every finding here. Repeat the scan after relevant candidate changes, as required by RELEASE.md. Scan is pending; merge, tag, archive branch and publication are outside this task.