docs(man): say component problems never block a write

comark(7) said a note "is saved either way" after component problems, but
a write can still be refused for other reasons (the note exists, a
revision conflict), and Cloud now reports component problems on refused
writes too. Say what holds in every case: the problems never block the
write. The memory-comark skill had the same "after the save" wording.

Refs #1721

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: phernandez <paul@basicmachines.co>

Author: phernandez

skills/memory-comark/SKILL.md

@@ -165,8 +165,8 @@ as a snapshot in prose and keep them in the chart's row grammar.
 
 A broken component renders a coded problem and a fix inside its own frame; the
 rest of the note still renders. In Basic Memory Cloud, `write_note` and
-`edit_note` list these problems under **Component problems** after the save, so
-fix them right away with `edit_note`. `comark(7)` in the manual
+`edit_note` list these problems under **Component problems** in their result
+(they never block the write), so fix them right away with `edit_note`. `comark(7)` in the manual
 (`memory://man/comark(7)`) is a quick reference to the syntax and codes. The
 codes you will meet most:
 

src/basic_memory/man/man7/comark(7).md

@@ -124,7 +124,7 @@ In Basic Memory Cloud:
 
 - `write_note` and `edit_note` list the components that will render as errors,
   under **Component problems** (a `component_problems` field in JSON output).
-  The note is saved either way; fix the problems with `edit_note`.
+  The problems never block the write; fix them in the note's Markdown.
 - `read_note(view="text")` returns the note as a reader sees it: each component
   as plain Markdown, with live queries run now. Use it to confirm a live view
   has rows before you quote its numbers. Edit from the default view, which is