Make reviewer own journal-grounded workflow

README.md

@@ -180,31 +180,33 @@ Team-style requests route through panel. Explicit debate-language requests
 write panel debate records under `.longtable/panel/`. LongTable team execution
 is disabled for new work, and `.longtable/team/` is historical state only.
 
-## Journal Editor and Venue Fit
+## Journal-Grounded Reviewer and Venue Fit
 
-`longtable-editor` is intentionally a thin role adapter. It foregrounds the
-Journal Editor perspective and must disclose `LongTable consulted: Journal
-Editor`, but it is not allowed to invent knowledge about a named target journal.
+`longtable-reviewer` is the compact surface for peer-review and editor-style
+feedback. It keeps reviewer objections, Journal Editor fit judgment, Venue
+Strategist tradeoffs, and scholar-research evidence in one evidence-backed
+workflow instead of splitting journal feedback into a separate visible skill.
 
-If a target journal is named, LongTable should not claim journal fit from role
-intuition alone. A fit judgment needs a journal profile: aims/scope, author
-guidance, recent article patterns, and article type expectations. Without that
-profile, the editor judgment should either ask whether to run scholarly/venue
-search or label fit as provisional.
+If a target journal is named, LongTable should ground reviewer feedback in a
+Journal Profile: aims/scope, author guidance, recent article patterns, and
+article type expectations. If reference papers are available or recoverable,
+LongTable should build a Reference Pattern Matrix covering decision structure,
+paper flow, standardized terminology, Figure/Table conventions, and APA 7
+style expectations.
 
 Useful command surfaces:
 
 ```bash
-longtable review --role editor --prompt "Evaluate this manuscript positioning."
-longtable panel --role editor,reviewer --prompt "Compare journal fit and reviewer risk."
+longtable review --role reviewer --prompt "Evaluate this manuscript positioning for the target journal."
+longtable panel --role reviewer,measurement_auditor --prompt "Compare journal fit, reviewer risk, and measurement evidence."
 longtable search --intent venue --query "<journal or venue context>"
 longtable scholar-research scaffold --cwd "<project-path>" --json
 ```
 
 Treat journal fit as a risk rubric, not an acceptance prediction. A useful
-editor pass separates scope fit, contribution fit, method/evidence norm fit,
-editorial salience, and citation/evidence risk, and marks unsupported claims as
-provisional.
+reviewer pass separates editor-facing contribution claim, reviewer objection,
+venue-strategy tradeoff, evidence gap, revision action, and any Researcher
+Checkpoint needed before changing venue positioning.
 
 ## Researcher Checkpoints
 

docs/LONGTABLE-COMMAND-SURFACE.md

@@ -124,6 +124,21 @@ to panel debate records under `.longtable/panel/`. `longtable team` is not a
 public command surface. Historical `.longtable/team/` records remain readable
 only as older workspace state.
 
+### `longtable review --role reviewer`
+
+Journal-grounded review:
+
+- keeps peer-review objections, Journal Editor fit judgment, Venue Strategist
+  tradeoffs, and scholar-research evidence under the reviewer surface
+- uses `Journal Profile` before target-journal fit claims
+- uses `Reference Pattern Matrix` when reference papers are available or
+  recoverable
+- compares decision structure, paper flow, standardized terminology,
+  Figure/Table conventions, and APA 7 style expectations
+- returns editor-facing contribution claim, reviewer objection,
+  venue-strategy tradeoff, evidence gap, revision action, and any needed
+  Researcher Checkpoint
+
 ### `longtable handoff`
 
 Continuation work packet:

docs/release-notes-0.1.72.md

@@ -0,0 +1,32 @@
+# LongTable 0.1.72
+
+LongTable 0.1.72 makes `longtable-reviewer` the compact evidence-backed
+journal review surface. The reviewer role now carries peer-review objections,
+Journal Editor fit judgment, Venue Strategist tradeoffs, and scholar-research
+evidence workflow without adding a separate visible editor skill to the compact
+surface.
+
+## Changes
+
+- Expands the Reviewer role to cover journal-grounded fit risks and missing
+  evidence, not only peer-review objections.
+- Adds a Journal-grounded reviewer workflow to generated Codex and Claude
+  `longtable-reviewer` skills.
+- Adds the same workflow to `longtable review --role reviewer --print` and the
+  legacy `longtable-reviewer` prompt alias.
+- Requires reviewer feedback to use a `Journal Profile` and, when reference
+  papers are available or recoverable, a `Reference Pattern Matrix`.
+- Documents checks for decision structure, paper flow, standardized
+  terminology, Figure/Table conventions, and APA 7 style expectations.
+
+## Migration
+
+Use `longtable-reviewer` or `longtable review --role reviewer` for journal-fit,
+editor-style, and peer-review feedback. `--role editor` remains available as an
+explicit role lens, but the compact reviewer surface now owns the evidence-backed
+journal review workflow.
+
+## Verification
+
+- `npm run smoke:role-audit`
+- `npm run release:check`

package.json

@@ -1,6 +1,6 @@
 {
   "name": "longtable-monorepo",
-  "version": "0.1.71",
+  "version": "0.1.72",
   "private": true,
   "description": "Monorepo for the LongTable product surface and provider-neutral runtime packages",
   "workspaces": [

packages/longtable-checkpoints/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/checkpoints",
-  "version": "0.1.71",
+  "version": "0.1.72",
   "private": false,
   "description": "Checkpoint policy engine for LongTable",
   "type": "module",
@@ -21,7 +21,7 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@longtable/core": "0.1.71"
+    "@longtable/core": "0.1.72"
   },
   "devDependencies": {
     "typescript": "^5.6.0"

packages/longtable-core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/core",
-  "version": "0.1.71",
+  "version": "0.1.72",
   "private": false,
   "description": "Provider-neutral domain models and contracts for LongTable",
   "type": "module",

packages/longtable-mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/mcp",
-  "version": "0.1.71",
+  "version": "0.1.72",
   "private": false,
   "description": "LongTable MCP transport for workspace state and Researcher Checkpoints",
   "type": "module",
@@ -26,12 +26,12 @@
     "self-test": "node ./dist/server.js --self-test"
   },
   "dependencies": {
-    "@longtable/checkpoints": "0.1.71",
-    "@longtable/cli": "0.1.71",
-    "@longtable/core": "0.1.71",
-    "@longtable/provider-claude": "0.1.71",
-    "@longtable/provider-codex": "0.1.71",
-    "@longtable/setup": "0.1.71",
+    "@longtable/checkpoints": "0.1.72",
+    "@longtable/cli": "0.1.72",
+    "@longtable/core": "0.1.72",
+    "@longtable/provider-claude": "0.1.72",
+    "@longtable/provider-codex": "0.1.72",
+    "@longtable/setup": "0.1.72",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.0.0"
   },

packages/longtable-memory/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/memory",
-  "version": "0.1.71",
+  "version": "0.1.72",
   "private": false,
   "description": "Memory contracts for LongTable explicit state, inferred hypotheses, and open tensions",
   "type": "module",
@@ -21,7 +21,7 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@longtable/core": "0.1.71"
+    "@longtable/core": "0.1.72"
   },
   "devDependencies": {
     "typescript": "^5.6.0"

packages/longtable-provider-claude/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/provider-claude",
-  "version": "0.1.71",
+  "version": "0.1.72",
   "private": false,
   "description": "Claude adapter surface for LongTable",
   "type": "module",
@@ -21,9 +21,9 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@longtable/checkpoints": "0.1.71",
-    "@longtable/core": "0.1.71",
-    "@longtable/setup": "0.1.71"
+    "@longtable/checkpoints": "0.1.72",
+    "@longtable/core": "0.1.72",
+    "@longtable/setup": "0.1.72"
   },
   "devDependencies": {
     "typescript": "^5.6.0"

packages/longtable-provider-claude/src/skills.ts

@@ -399,7 +399,8 @@ function mustAskQuestionsForRole(role: RoleDefinition): string[] {
       "What is the strongest venue-facing contribution claim, and what would make it overreach?"
     ],
     reviewer: [
-      "What objection would a skeptical reviewer raise first, and what missing evidence would answer it?"
+      "What objection would a skeptical reviewer raise first, and what missing evidence would answer it?",
+      "Which journal or venue expectation is the draft trying to satisfy, and what reference-paper pattern proves that expectation?"
     ],
     theory_critic: [
       "Which construct boundary or theoretical assumption must stay explicit before the claim is revised?"
@@ -431,6 +432,16 @@ function roleSkillSpec(role: RoleDefinition, surface: LongTableSkillSurface = "c
         "- Require a journal profile before fit judgment: aims/scope, author guidance, recent article pattern, and article type expectations.",
         "- If the journal profile is missing, ask whether to run scholarly/venue search or label the fit as provisional."
       ]
+    : role.key === "reviewer"
+      ? [
+          "## Journal-grounded reviewer workflow",
+          "",
+          "- Keep `longtable-reviewer` as the visible compact surface; use Journal Editor and Venue Strategist as internal lenses.",
+          "- When a target journal, submission venue, reference paper set, or journal-ready claim is named, ground feedback in a `Journal Profile`: aims/scope, author guidance, recent article pattern, and article type expectations.",
+          "- Use `scholar-research` or `longtable search --intent venue` to build or refresh a `Reference Pattern Matrix` before making source-backed journal-fit claims.",
+          "- Read available reference papers and compare decision structure, paper flow, standardized terminology, Figure/Table conventions, and APA 7 style expectations.",
+          "- Return reviewer feedback as: editor-facing contribution claim, reviewer objection, Venue Strategist tradeoff, evidence gap, revision action, and Researcher Checkpoint when the recommendation changes venue positioning."
+        ]
     : [];
   return {
     name: skillNameForRole(role, surface),