Background
Using arscontexta 0.8.0 in a dual-domain vault (Claude Code). My vault uses a body-footer Topics convention (## Topics / Topics: section with - [[MOC]]) rather than a frontmatter topics: array — a frontmatter array felt like upkeep with no engine to consume it unless Bases/Dataview is in play.
Problem
The health skill's Category 1 (Schema Compliance) checks topics with rg -q '^topics:' (frontmatter only) and WARNs if absent. Meanwhile Category 8 (MOC Coherence, ~L452) already counts topics from "footer/field", and reseed refers to "topics-footer". So topics-location handling differs within the same plugin, and a body-footer vault ends up with a WARN on essentially every note.
(Looks related to but distinct from #46 — another Category-1 false positive around BOM handling. Same check, different cause.)
A couple of thoughts (you'll know the design far better than I do)
- The schema-compliance check could perhaps accept the same body-footer Topics form the rest of the plugin already recognizes.
- It might also be handy to support a per-vault topics policy (e.g. an
.arscontexta topics: required | optional), since some vaults treat topics as optional and lean on the MOC→note direction for discovery. Keeping the default as required would leave existing frontmatter-topics vaults untouched.
Happy to test a patch or send a PR if that'd help — whatever fits best.
Background
Using arscontexta 0.8.0 in a dual-domain vault (Claude Code). My vault uses a body-footer Topics convention (
## Topics/Topics:section with- [[MOC]]) rather than a frontmattertopics:array — a frontmatter array felt like upkeep with no engine to consume it unless Bases/Dataview is in play.Problem
The
healthskill's Category 1 (Schema Compliance) checks topics withrg -q '^topics:'(frontmatter only) and WARNs if absent. Meanwhile Category 8 (MOC Coherence, ~L452) already counts topics from "footer/field", andreseedrefers to "topics-footer". So topics-location handling differs within the same plugin, and a body-footer vault ends up with a WARN on essentially every note.(Looks related to but distinct from #46 — another Category-1 false positive around BOM handling. Same check, different cause.)
A couple of thoughts (you'll know the design far better than I do)
.arscontextatopics: required | optional), since some vaults treat topics as optional and lean on the MOC→note direction for discovery. Keeping the default asrequiredwould leave existing frontmatter-topics vaults untouched.Happy to test a patch or send a PR if that'd help — whatever fits best.