1.6.1

Rolls up 1.6.0 and 1.6.1, which were developed back to back.

Opening a note no longer marks it edited

Foldable Frontmatter Groups rewrites notes on its own initiative: reconciling groups on open and leave, applying create-time defaults, inserting body templates, running Cleanup scrubs, migrating fields. To Obsidian, every one of those looks exactly like you editing the note.

It now announces those writes. Immediately before each one, the plugin fires the recent-edits:plugin-write workspace event. Recent Edits 1.6.0 and later listens for it and leaves its ledger untouched for the matching write, so simply opening a note no longer pushes it to the top of your recent list.

Two writes are deliberately not announced, because they are yours rather than housekeeping: the context-menu Remove property, which you asked for on that specific note, and the migration conflict checklist, which is a deliverable you will want to find. Fast paths that end up writing nothing never announce at all, and if Recent Edits is not installed the event has no listeners and nothing happens.

Cleanup guard for template-defaulted fields

Remove null and Remove ALL on a field that a matching template lists as a default now open a confirmation first. The dialog names the owning template with an Open template jump, tells you how many of the affected notes would get the field straight back on their next open, and offers Proceed anyway or Cancel.

This closes a real trap: a vault-wide Remove null on a scaffold field appears to work, then reconcile quietly re-inserts the field on every note as you open it. Ownership is computed by the same logic reconcile uses, so the guard and the reconcile pass cannot disagree.

Group fill indicator on folded headers

A folded group header showed a property count and nothing else, so a scaffold group holding nothing looked identical to one full of real values.

Folded headers now carry a dot between the group name and the count: solid and accent-colored when at least one property in the group holds a value, a hollow faint ring when they are all empty. An unchecked checkbox and a numeric 0 read as empty for this purpose, since the question is whether the group is worth unfolding.

Folded headers only. Unfolding shows you the values themselves.

Show fill indicator in settings is the master switch, on by default, and each group card carries its own opt-out.

Also

• The settings tab can now reveal a template card that has no group attached.

1.5.4

1.5.4: fix ENOENT race on note create

1.5.3

v1.5.3: clear store-validator lint warnings (type safety + CSS)

- main.ts: type processFrontMatter callbacks and metadata reads to drop
  no-unsafe-assignment/member-access/argument warnings; use closest<HTMLElement>()
  instead of redundant type assertions
- styles.css: replace all !important flags with higher-specificity selectors;
  swap :has() for a marker class applied in ensureSettingsGear
- no functional or visual change

1.5.2

Maintenance release. No user-facing behavior changes and no code changes from 1.5.1.

• Adjusted the release asset so it no longer references a stale build attestation flagged by the plugin validator.

Install/update via BRAT: cwagner223355/obsidian-foldable-frontmatter-groups

1.5.1

Community-store readiness hardening. No user-facing behavior changes.

• Replaced direct element.style assignments with Obsidian's setCssStyles.
• Switched DOM creation to the createEl/createDiv/createSpan helpers.
• Wrapped async suggester callbacks to satisfy the plugin linter.
• Removed dead code and tightened event-handler typing.
• Simplified the release workflow.

Install/update via BRAT: cwagner223355/obsidian-foldable-frontmatter-groups

1.5.0

docs: add ko-fi funding link (README Support section + manifest fundi…