Merge pull request #23 from ScienceLiveHub/fix/quote-comment-500-standalone

Quote comment: 500-char cap and standalone (not replication-framed)

Author: annefou

.claude/agents/nanopub-drafter.md

@@ -59,7 +59,7 @@ Steps 3–6 below are this rule applied in order. If you ever catch yourself typ
 
 | Step | Critical content rule |
 |---|---|
-| 01 Quote | Verbatim from PDF. **Quoted Text ≤ 500 chars (hard). Comment ≤ 800 chars (hard); aim well under** — concise interpretation, not a paragraph essay. |
+| 01 Quote | Verbatim from PDF. **Quoted Text ≤ 500 chars. Comment ≤ 500 chars** (live-form limit). The comment is a **standalone** interpretation of why the quotation matters, **true independently of any replication** — do NOT mention the replication or what it tests. Concise, not a paragraph essay. |
 | 01 PICO | Discipline-level concepts only. NO methodology. NO numbers. See `docs/pico-study-outcome-levels.md`. |
 | 01 PCC | Same — descriptive scoping, no methodology. |
 | 02 AIDA | Atomic. One empirical finding. Ends with full stop. **States what is true *in the world*, not what is true *in the model*.** See AIDA pre-write checklist below. |
@@ -113,7 +113,7 @@ Example: drafting the FORRT Replication Study's *Methodology* field for a bumble
 - **Don't ship a draft with only the headline content.** Every field, every time, in form order.
 - **Don't paraphrase quotes** or reconstruct numbers from memory.
 - **Don't write `<replace-with-X>` placeholders** in the draft. Look up the value (see No-placeholders rule above) or stop and ask. Drafts get shipped; placeholders don't get re-checked.
-- **Mind the Quote caps: Quoted Text ≤ 500, Comment ≤ 800** (both are template `nt:hasRegex` hard caps — see `docs/forrt-form-fields.md` § Quote-with-comment). Keep the comment well under its ceiling anyway; long comments dilute the *why this quote matters* point.
+- **Mind the Quote caps: Quoted Text ≤ 500, Comment ≤ 500** (the live form enforces 500 on the comment — see `docs/forrt-form-fields.md` § Quote-with-comment). The comment is a **standalone** annotation of the quotation, **true independently of any replication** — do not describe the replication or what it tests. Keep it well under the cap; long comments read as marketing.
 - **Don't ship an AIDA without running the pre-write checklist above.** Mixed-layer AIDAs are the most common drafting failure; the checklist is non-negotiable.
 - **Don't mix domain-specific abbreviations** (e.g. "pp") into nanopub prose — see `DOMAIN.md`.
 - **Don't invent a typed value from memory** — a Wikidata topic, a QID, an ORCID, a DOI, or a restricted-choice option. Resolve it against its declared source (step 4) or stop and ask. The wizard publishes the draft's values without a human dropdown to catch a wrong one.

docs/forrt-form-fields.md

@@ -34,15 +34,15 @@ This checklist exists because it is unreasonably easy to ship a partial draft th
 
 Form heading: *"Annotate a paper quotation — Annotating a paper quotation with personal interpretation"*
 
-> ⚠️ **Quoted Text caps at 500 characters; Comment caps at 800.** Both are hard limits enforced by the template (`nt:hasRegex` `{5,500}` on the quotation, `{5,800}` on the comment). Brevity is still the discipline for the comment — a tight *why this quote matters* beats an 800-char essay — but 500 is not its ceiling; 800 is. If your verbatim quote is longer than 500 chars, switch the radio button to **Quote start/end** mode and use start-phrase + end-phrase to mark a longer span instead of pasting the whole text.
+> ⚠️ **Both the Quoted Text and the Comment cap at 500 characters on the live platform.** The Quoted Text limit is `{5,500}`. The **Comment is enforced at 500 by the live form too**, even though the vendored snapshot regex still reads `{5,800}` — treat **500 as the ceiling** (the snapshot is stale here; re-vendor it with `check_template_drift.py --update`). Brevity is the discipline regardless — a tight *why this quote matters* beats a padded comment. If your verbatim quote is longer than 500 chars, switch the radio button to **Quote start/end** mode and use start-phrase + end-phrase to mark a longer span instead of pasting the whole text.
 
 | Field label | Field type | Notes |
 |---|---|---|
 | Cited DOI | text input | Format: starts with `10.` — placeholder reads "DOI, starting with 10." So enter `10.3389/fmars.2025.1699781`, **NOT** `https://doi.org/10.3389/...` |
 | Quote whole text (less than 500 characters) | radio button (default selected) | Mode for quoting a single short passage. The Quoted Text field below must be ≤ 500 chars. |
 | Quote start/end | radio button (alternative) | Alternative mode — two short text inputs for start phrase + end phrase, marking a longer span. Use when the quote is too long for whole-text mode. |
 | Quoted Text | textarea, **required** | The verbatim sentence(s) from the paper. ≤ 500 chars in "Quote whole text" mode. **Must be character-for-character verbatim — see `docs/verify-before-drafting.md`.** |
-| Comment | textarea, **required** | Subtitle: *"Our interpretation or explanation of why this quotation is relevant."* Use this to explain why the quote matters and what the replication tests. **Hard cap 800 chars** (template regex `{5,800}`); aim well under it — long comments dilute the *why this quote matters* point and read as marketing rather than interpretation. |
+| Comment | textarea, **required** | Subtitle: *"Our interpretation or explanation of why this quotation is relevant."* Explain **why the quotation matters on its own terms** — a standalone interpretation that must be **true independently of any replication**. Do **not** describe the replication, its design, or what it tests: the annotation stands alone and is reused by anyone citing the quote. **Cap 500 chars** (the live form enforces 500, even though the vendored regex reads `{5,800}`); aim well under it — long comments dilute the *why this quote matters* point and read as marketing rather than interpretation. |
 
 Use this template for **paper-rooted chains** where you are testing or extending a sentence from someone else's paper. See `docs/chain-decision-tree.md`.