Flashcards 2.1.1

A maintenance release: one card-content bug, documentation for two card types that were shipped but never written up, and a pass over the plugin against Obsidian's own review guidelines.

Card callouts no longer show their anchor

A card written as a > [!CARD] callout ended up with its own identity anchor in the answer, so ^q-abcd appeared on the back of the card in Anki. The anchor is written on the line below the callout, and Markdown pulls that line into the callout's last paragraph — every other card type stripped it, the callout did not. Existing callout cards correct themselves on the next sync.

Card callouts and atomic notes are documented

Both card types worked already but were missing from the manual. The usage guide now covers them, including the part that is easy to get wrong: with a test: key in the frontmatter, the answer is always the note's first paragraph and everything after it stays out of the card. Several items in the test: list produce several cards that share one answer.

The visual guide at docs/card-types.html shows the multiple-question form, and the reference the AI skill reads has the same rules.

Logging moved to the console's verbose level

Obsidian asks plugins not to use console.log, so debug and info lines now use console.debug. They no longer appear in the developer console unless Verbose is enabled in its level filter. Warnings and errors are unchanged, and the sync.log file still records everything at the configured level.

Themes can restyle the status bar

The status bar items and the masked flashcards property used inline styles and an !important rule, which no theme or CSS snippet could override. They now use ordinary classes: flashcards-status-hidden and flashcards-status-pending.

Under the hood

The editor preview for clozes, separators, anchors and tags now builds its elements directly instead of assembling HTML strings, so note text can no longer be interpreted as markup. Every dependency is pinned to an exact version, the release is built with npm ci from a committed lockfile, and release assets now carry build provenance attestations.

The repository runs Obsidian's own eslint-plugin-obsidianmd as part of its checks, so guideline regressions fail the build rather than showing up on the community plugin page.