wtf-p 0.7.2 → 0.7.3

package/vendors/gemini/commands/wtfp/create-slides.toml

@@ -1,7 +1,6 @@
 description = "Transform the paper's argument, evidence, and findings into an audience-appropriate presentation."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/create-slides; do not edit. -->
 # Create presentation slides
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -175,7 +174,7 @@ Contract: [protocol/actions/create-slides.json](../../../actions/create-slides.j
 1. Require project identity and enough manuscript or verified results to support a presentation.
 2. Ask for duration, expected slide count, audience, occasion, delivery format, visual style, and desired emphasis.
 3. Derive a timed narrative: audience problem, thesis, minimum background, method, strongest evidence, limitations, implications, and closing takeaway. Allocate time and slides before writing.
-4. Use verified project claims and cite source or manuscript locations in speaker notes or a references slide. Do not introduce novel results to make the story cleaner.
+4. Use verified project claims and cite source or manuscript locations in speaker notes or a references slide. Do not introduce novel results to make the story cleaner. Refuse any claim without a ledger row, never invent speaker or venue metadata, and derive diagrams only from named source files or documents with stated paths.
 5. Prefer one communicative purpose per slide. Use concise text, readable type, high contrast, descriptive titles, accessible color, and alt text or equivalent descriptions for meaningful visuals.
 6. Use existing figures only when provenance and interpretation are known. Mark placeholders and data needs explicitly; never fabricate a chart.
 7. Generate editable slide source and a delivery manifest under `project://deliverables/slides/{artifact}`.
@@ -188,11 +187,11 @@ Completion requires an audience-appropriate editable deck with an honest render
 
 Contract: [protocol/actions/create-poster.json](../../../actions/create-poster.json)
 
-1. Require project identity and verified manuscript findings. Ask for dimensions, orientation, venue rules, audience viewing distance, title, authors, affiliations, contact details, output format, and available visuals.
+1. Require project identity and verified manuscript findings. Ask for dimensions, orientation, venue rules, audience viewing distance, title, authors, affiliations, contact details, output format, and available visuals. Never invent missing metadata; leave a visible placeholder and report it.
 2. Define a non-linear reading hierarchy: one-sentence takeaway, motivation, minimal method, principal evidence, limitations, conclusion, and contact or artifact link.
 3. Budget physical space before writing. Prioritize the title, takeaway, and strongest figure; avoid shrinking prose to preserve excess content.
-4. Use verified claims, values, citations, and figures. Record provenance and include accessible descriptions. Mark missing visuals as placeholders rather than generating false evidence.
-5. Generate editable poster source and a delivery manifest under `project://deliverables/poster/{artifact}`.
+4. Use verified claims, values, citations, and figures, recorded in the claim ledger from `protocol://templates/poster.md`; refuse any statement without a source record, manuscript passage, or named project file. Derive diagrams only from named source files or documents and state their paths. Record provenance and include accessible descriptions. Mark missing visuals as placeholders rather than generating false evidence.
+5. Generate editable, laid-out poster source (the template's HTML grid or the venue's mandated template) and a delivery manifest with the claim ledger under `project://deliverables/poster/{artifact}`.
 6. Check dimensions, orientation, margins, font sizes at final scale, column flow, contrast, image resolution, citation legibility, link or code targets, and overflow.
 7. Render only when requested and a configured host-provided local renderer exists; invoke it under the action's declared `tool.execute` effect and verify the actual artifact dimensions. Distinguish source validity from render success.
 8. Report source and rendered paths, validation results, print-service considerations, and unresolved manual steps.
@@ -211,9 +210,9 @@ Manuscript prose and supporting context, research, plan, review, summary, handof
 
 ## Procedure
 
-1. Confirm audience, duration, format, and speaking goal, following the confirmation list in `protocol://templates/slides.md`.
+1. Confirm audience, duration, format, speaking goal, and the exact speaker, affiliation, and venue metadata, following the confirmation list in `protocol://templates/slides.md`. Never invent missing metadata; leave a visible placeholder.
 1a. Derive the slide count from the confirmed duration using the budget table in `protocol://templates/slides.md`, not from the manuscript's section count.
-2. Build a narrative arc from supported manuscript claims and include citations or attribution where needed.
+2. Build a narrative arc from supported manuscript claims only, running the evidence gate in `protocol://templates/slides.md`: refuse every statement, comparison, or figure without a cited source record, manuscript passage, or named project file, and derive each diagram from named source files or documents with their paths stated on the slide.
 3. Write slide source and assets under the declared deliverable URI; preview before replacing an existing deliverable. This action produces slide source, not a rendered deck: WTF-P declares no rendering effect and runs no renderer. If the author asks for a rendered artifact, return a labeled handoff naming the exact command they can run in their own toolchain.
 
 ## Safety and completion
@@ -590,7 +589,11 @@ Copy the body below, replace every bracketed placeholder from the manuscript and
 
 ## Confirm before writing
 
-Talk length, audience, venue format, whether questions are inside or outside the slot, and the single thing the audience should remember.
+Talk length, audience, venue format, whether questions are inside or outside the slot, the single thing the audience should remember, and the exact speaker name, affiliation, and venue line. Ask for any of these the manifest does not record.
+
+## Evidence gate
+
+Before writing, build a claim ledger with one row per claim, number, comparison, or figure, each naming its support as a manuscript passage, a `project://sources/{source}` record, a `project://evidence/{evidence}` record, or a named project file path. Cut any row without support; statements about other systems or prior work need a cited source record, never general knowledge. Never invent speaker names, affiliations, emails, funding, venue, or dates; leave a visible placeholder such as `[AFFILIATION NEEDED]` and report it as unresolved. When the subject is software, derive every diagram from named source files or documentation, state those paths on the slide, and leave a labeled placeholder rather than an invented architecture.
 
 ## Budgets
 
@@ -609,7 +612,7 @@ Backup slides sit after the closing slide and answer the questions the work invi
 
 ## [Title slide]
 
-[Title] · [Speaker] · [Affiliation] · [Venue and date]
+[Title] · [Speaker or SPEAKER NEEDED] · [Affiliation or AFFILIATION NEEDED] · [Venue and date or VENUE NEEDED]
 
 ## [The problem, in one image or one sentence]
 
@@ -626,7 +629,7 @@ Backup slides sit after the closing slide and answer the questions the work invi
 
 ## [Approach]
 
-[One diagram. Speaker note: walk it left to right; do not read the labels aloud.]
+[One diagram derived from named source files or documents. Source: [paths]. Speaker note: walk it left to right; do not read the labels aloud.]
 
 ## [Key design decision]
 
@@ -664,7 +667,7 @@ Backup slides sit after the closing slide and answer the questions the work invi
 
 ## Attribution rules
 
-Every number and figure must trace to a manuscript passage or an evidence record. Reused figures carry their original attribution on the slide. Speaker notes are part of the deliverable and follow the same evidence rule as the slides: do not put a claim in a note that the records do not support.
+Every number, figure, and claim must trace to a row in the claim ledger. Reused figures carry their original attribution on the slide. Speaker notes are part of the deliverable and follow the same evidence rule as the slides: do not put a claim in a note that the records do not support.
 
 </details>
 
@@ -675,4 +678,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/create-slides; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/discuss-section.toml

@@ -1,7 +1,6 @@
 description = "Capture the researcher's intended purpose, essential content, voice, and boundaries before planning."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/discuss-section; do not edit. -->
 # Discuss a section
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -996,4 +995,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/discuss-section; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/execute-outline.toml

@@ -1,7 +1,6 @@
 description = "Draft independent section waves in parallel and verify cross-section coherence."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/execute-outline; do not edit. -->
 # Execute the outline
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -1482,4 +1481,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/execute-outline; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/export-latex.toml

@@ -1,7 +1,6 @@
 description = "Export the manuscript and bibliography to portable LaTeX source with declared formatting."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/export-latex; do not edit. -->
 WTFP_ACTION_UNAVAILABLE
 
 Action: `export-latex`
@@ -11,4 +10,5 @@ Unavailable effects: `tool.execute`
 
 No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran.
 Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/export-latex; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/help.toml

@@ -1,7 +1,6 @@
 description = "Render the stable WTF-P action reference from the canonical catalog."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/help; do not edit. -->
 # Show WTF-P help
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -274,4 +273,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/help; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/insert-section.toml

@@ -1,7 +1,6 @@
 description = "Insert a newly discovered section while preserving established numbering and dependencies."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/insert-section; do not edit. -->
 # Insert a section
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -716,4 +715,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/insert-section; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/list-assumptions.toml

@@ -1,7 +1,6 @@
 description = "Preview the intended approach and assumptions for a section without changing project files."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/list-assumptions; do not edit. -->
 # List section assumptions
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -818,4 +817,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/list-assumptions; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/map-project.toml

@@ -1,7 +1,6 @@
 description = "Index existing drafts, data, figures, and references into portable project state."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/map-project; do not edit. -->
 # Map an existing project
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -760,4 +759,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/map-project; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/new-paper.toml

@@ -1,7 +1,6 @@
 description = "Interview the researcher and initialize a portable WTF-P project."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/new-paper; do not edit. -->
 # Start a new paper
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -982,4 +981,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/new-paper; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/pause-writing.toml

@@ -1,7 +1,6 @@
 description = "Record an exact context handoff so another session can resume without reconstructing intent."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/pause-writing; do not edit. -->
 # Pause writing
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -1031,4 +1030,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/pause-writing; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/plan-milestone-gaps.toml

@@ -1,7 +1,6 @@
 description = "Convert milestone audit failures into targeted, verifiable fix plans."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/plan-milestone-gaps; do not edit. -->
 # Plan milestone gap fixes
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -856,4 +855,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/plan-milestone-gaps; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/plan-revision.toml

@@ -1,7 +1,6 @@
 description = "Turn prioritized review findings into a bounded, testable revision plan."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/plan-revision; do not edit. -->
 # Plan a revision
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -842,4 +841,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/plan-revision; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/plan-section.toml

@@ -1,7 +1,6 @@
 description = "Create and independently check a detailed writing plan for one section."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/plan-section; do not edit. -->
 # Plan a section
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -1517,4 +1516,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/plan-section; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/polish-prose.toml

@@ -1,7 +1,6 @@
 description = "Improve clarity, flow, precision, and academic voice without changing supported claims."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/polish-prose; do not edit. -->
 # Polish prose
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -807,4 +806,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/polish-prose; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/progress.toml

@@ -1,7 +1,6 @@
 description = "Summarize writing progress, surface blockers, and recommend the next compatible action."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/progress; do not edit. -->
 # Show project progress
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -1442,4 +1441,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/progress; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/quick.toml

@@ -1,7 +1,6 @@
 description = "Apply a small, bounded writing fix with minimal planning overhead and state tracking."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/quick; do not edit. -->
 # Make a quick writing change
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -779,4 +778,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/quick; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/remove-section.toml

@@ -1,7 +1,6 @@
 description = "Remove an unwritten future section and repair numbering and dependencies."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/remove-section; do not edit. -->
 WTFP_ACTION_UNAVAILABLE
 
 Action: `remove-section`
@@ -11,4 +10,5 @@ Unavailable effects: `filesystem.delete`
 
 No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran.
 Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/remove-section; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/report-bug.toml

@@ -1,7 +1,6 @@
 description = "Collect a reproducible bug report and publish it only after explicit user approval."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/report-bug; do not edit. -->
 WTFP_ACTION_UNAVAILABLE
 
 Action: `report-bug`
@@ -11,4 +10,5 @@ Unavailable effects: `external.issue`
 
 No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran.
 Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/report-bug; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/request-feature.toml

@@ -1,7 +1,6 @@
 description = "Shape a concrete feature request and publish it only after explicit user approval."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/request-feature; do not edit. -->
 WTFP_ACTION_UNAVAILABLE
 
 Action: `request-feature`
@@ -11,4 +10,5 @@ Unavailable effects: `external.issue`
 
 No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran.
 Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/request-feature; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/research-gap.toml

@@ -1,7 +1,6 @@
 description = "Synthesize literature, domain conventions, open gaps, and defensible positioning for a section."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/research-gap; do not edit. -->
 WTFP_ACTION_UNAVAILABLE
 
 Action: `research-gap`
@@ -11,4 +10,5 @@ Unavailable effects: `tool.execute`
 
 No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran.
 Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/research-gap; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/resume-writing.toml

@@ -1,7 +1,6 @@
 description = "Restore the latest portable handoff and route the researcher to the next safe action."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/resume-writing; do not edit. -->
 # Resume writing
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -1279,4 +1278,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/resume-writing; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/review-section.toml

@@ -1,7 +1,6 @@
 description = "Review a drafted section for evidence, citations, coherence, requirements, and reader expectations."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/review-section; do not edit. -->
 # Review a section
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -1040,4 +1039,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/review-section; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/settings.toml

@@ -1,7 +1,6 @@
 description = "View and update portable project settings after presenting the exact proposed diff."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/settings; do not edit. -->
 # Manage project settings
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -446,4 +445,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/settings; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/submit-milestone.toml

@@ -1,7 +1,6 @@
 description = "Archive a completed draft or submission round with its reproducible project state and statistics."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/submit-milestone; do not edit. -->
 # Archive a milestone
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -175,7 +174,7 @@ Contract: [protocol/actions/create-slides.json](../../../actions/create-slides.j
 1. Require project identity and enough manuscript or verified results to support a presentation.
 2. Ask for duration, expected slide count, audience, occasion, delivery format, visual style, and desired emphasis.
 3. Derive a timed narrative: audience problem, thesis, minimum background, method, strongest evidence, limitations, implications, and closing takeaway. Allocate time and slides before writing.
-4. Use verified project claims and cite source or manuscript locations in speaker notes or a references slide. Do not introduce novel results to make the story cleaner.
+4. Use verified project claims and cite source or manuscript locations in speaker notes or a references slide. Do not introduce novel results to make the story cleaner. Refuse any claim without a ledger row, never invent speaker or venue metadata, and derive diagrams only from named source files or documents with stated paths.
 5. Prefer one communicative purpose per slide. Use concise text, readable type, high contrast, descriptive titles, accessible color, and alt text or equivalent descriptions for meaningful visuals.
 6. Use existing figures only when provenance and interpretation are known. Mark placeholders and data needs explicitly; never fabricate a chart.
 7. Generate editable slide source and a delivery manifest under `project://deliverables/slides/{artifact}`.
@@ -188,11 +187,11 @@ Completion requires an audience-appropriate editable deck with an honest render
 
 Contract: [protocol/actions/create-poster.json](../../../actions/create-poster.json)
 
-1. Require project identity and verified manuscript findings. Ask for dimensions, orientation, venue rules, audience viewing distance, title, authors, affiliations, contact details, output format, and available visuals.
+1. Require project identity and verified manuscript findings. Ask for dimensions, orientation, venue rules, audience viewing distance, title, authors, affiliations, contact details, output format, and available visuals. Never invent missing metadata; leave a visible placeholder and report it.
 2. Define a non-linear reading hierarchy: one-sentence takeaway, motivation, minimal method, principal evidence, limitations, conclusion, and contact or artifact link.
 3. Budget physical space before writing. Prioritize the title, takeaway, and strongest figure; avoid shrinking prose to preserve excess content.
-4. Use verified claims, values, citations, and figures. Record provenance and include accessible descriptions. Mark missing visuals as placeholders rather than generating false evidence.
-5. Generate editable poster source and a delivery manifest under `project://deliverables/poster/{artifact}`.
+4. Use verified claims, values, citations, and figures, recorded in the claim ledger from `protocol://templates/poster.md`; refuse any statement without a source record, manuscript passage, or named project file. Derive diagrams only from named source files or documents and state their paths. Record provenance and include accessible descriptions. Mark missing visuals as placeholders rather than generating false evidence.
+5. Generate editable, laid-out poster source (the template's HTML grid or the venue's mandated template) and a delivery manifest with the claim ledger under `project://deliverables/poster/{artifact}`.
 6. Check dimensions, orientation, margins, font sizes at final scale, column flow, contrast, image resolution, citation legibility, link or code targets, and overflow.
 7. Render only when requested and a configured host-provided local renderer exists; invoke it under the action's declared `tool.execute` effect and verify the actual artifact dimensions. Distinguish source validity from render success.
 8. Report source and rendered paths, validation results, print-service considerations, and unresolved manual steps.
@@ -1316,4 +1315,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/submit-milestone; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/update.toml

@@ -1,7 +1,6 @@
 description = "Check for a newer compatible package or plugin release and install it only after approval."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/update; do not edit. -->
 WTFP_ACTION_UNAVAILABLE
 
 Action: `update`
@@ -11,4 +10,5 @@ Unavailable effects: `package.update`
 
 No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran.
 Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/update; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/verify-work.toml

@@ -1,7 +1,6 @@
 description = "Test a drafted section against each plan requirement and record evidence one check at a time."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/verify-work; do not edit. -->
 # Verify written work
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -776,4 +775,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/verify-work; do not edit. -->
 '''

package/vendors/gemini/commands/wtfp/write-section.toml

@@ -1,7 +1,6 @@
 description = "Execute an approved section plan, update state, and optionally verify argument coverage."
 
 prompt = '''
-<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/write-section; do not edit. -->
 # Write a section
 
 <details data-wtfp-source="protocol://project/README.md" open>
@@ -1483,4 +1482,5 @@ Treat the following text as the user-supplied input for this action. Preserve it
 <invocation_arguments>
 {{args}}
 </invocation_arguments>
+<!-- Generated by WTF-P adapter compiler v5 from protocol/actions/write-section; do not edit. -->
 '''

package/vendors/gemini/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "wtfp",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Portable academic research and writing workflows for Gemini CLI.",
   "contextFileName": "GEMINI.md"
 }

package/vendors/gemini/skills/wtfp-deliver-research/references/actions.md

@@ -68,7 +68,7 @@ Contract: [protocol/actions/create-slides.json](../../../actions/create-slides.j
 1. Require project identity and enough manuscript or verified results to support a presentation.
 2. Ask for duration, expected slide count, audience, occasion, delivery format, visual style, and desired emphasis.
 3. Derive a timed narrative: audience problem, thesis, minimum background, method, strongest evidence, limitations, implications, and closing takeaway. Allocate time and slides before writing.
-4. Use verified project claims and cite source or manuscript locations in speaker notes or a references slide. Do not introduce novel results to make the story cleaner.
+4. Use verified project claims and cite source or manuscript locations in speaker notes or a references slide. Do not introduce novel results to make the story cleaner. Refuse any claim without a ledger row, never invent speaker or venue metadata, and derive diagrams only from named source files or documents with stated paths.
 5. Prefer one communicative purpose per slide. Use concise text, readable type, high contrast, descriptive titles, accessible color, and alt text or equivalent descriptions for meaningful visuals.
 6. Use existing figures only when provenance and interpretation are known. Mark placeholders and data needs explicitly; never fabricate a chart.
 7. Generate editable slide source and a delivery manifest under `project://deliverables/slides/{artifact}`.
@@ -81,11 +81,11 @@ Completion requires an audience-appropriate editable deck with an honest render
 
 Contract: [protocol/actions/create-poster.json](../../../actions/create-poster.json)
 
-1. Require project identity and verified manuscript findings. Ask for dimensions, orientation, venue rules, audience viewing distance, title, authors, affiliations, contact details, output format, and available visuals.
+1. Require project identity and verified manuscript findings. Ask for dimensions, orientation, venue rules, audience viewing distance, title, authors, affiliations, contact details, output format, and available visuals. Never invent missing metadata; leave a visible placeholder and report it.
 2. Define a non-linear reading hierarchy: one-sentence takeaway, motivation, minimal method, principal evidence, limitations, conclusion, and contact or artifact link.
 3. Budget physical space before writing. Prioritize the title, takeaway, and strongest figure; avoid shrinking prose to preserve excess content.
-4. Use verified claims, values, citations, and figures. Record provenance and include accessible descriptions. Mark missing visuals as placeholders rather than generating false evidence.
-5. Generate editable poster source and a delivery manifest under `project://deliverables/poster/{artifact}`.
+4. Use verified claims, values, citations, and figures, recorded in the claim ledger from `protocol://templates/poster.md`; refuse any statement without a source record, manuscript passage, or named project file. Derive diagrams only from named source files or documents and state their paths. Record provenance and include accessible descriptions. Mark missing visuals as placeholders rather than generating false evidence.
+5. Generate editable, laid-out poster source (the template's HTML grid or the venue's mandated template) and a delivery manifest with the claim ledger under `project://deliverables/poster/{artifact}`.
 6. Check dimensions, orientation, margins, font sizes at final scale, column flow, contrast, image resolution, citation legibility, link or code targets, and overflow.
 7. Render only when requested and a configured host-provided local renderer exists; invoke it under the action's declared `tool.execute` effect and verify the actual artifact dimensions. Distinguish source validity from render success.
 8. Report source and rendered paths, validation results, print-service considerations, and unresolved manual steps.