diagnostics-refresh-contract

name	diagnostics-refresh-contract
description	Tier 4 workflow for refreshing diagnostics state and validating parser/type feedback before deeper test cycles.
tier	operational
godot_version	4.6+
doc_anchors	["godot-docs/tutorials/editor/script_editor.rst","godot-docs/tutorials/scripting/debug/overview_of_debugging_tools.rst","godot-docs/tutorials/editor/command_line_tutorial.rst"]
tags	["diagnostics","validation","workflow"]
depends_on	["godot-skills/godot-operational/test-execution-contract/SKILL.md"]

Diagnostics Refresh Contract

Use When

• Any GDScript/resource refactor that can invalidate cached diagnostics.

Outcomes

• Diagnostics state reflects current code/resources after edit batches.
• Blocking parser/type issues are resolved before broader test runs.
• Suspected false positives are documented with evidence.

Required Rules

• Refresh diagnostics once per edit batch before testing.
• Prioritize changed-scope errors before global warning cleanup.
• Block downstream testing on unresolved parse/type failures.
• Log source/tool context when classifying false positives.

Workflow

1. Refresh diagnostics/cache state once after edit batch.
2. Collect diagnostics for changed scope first.
3. Resolve blocking errors before test execution.
4. Classify probable false positives separately with evidence.

Validation

• Re-running diagnostics after fixes removes previously reported blockers.
• Diagnostic report includes file path and first actionable error location.
• False-positive records include reproduction context and tool version.

Failure Modes

• Running tests on stale diagnostics wastes triage effort.
• Global warning churn hides high-priority parse/type failures.
• False positives are assumed without evidence and mask real defects.

Local Doc Anchors

• godot-docs/tutorials/editor/script_editor.rst
• godot-docs/tutorials/scripting/debug/overview_of_debugging_tools.rst
• godot-docs/tutorials/editor/command_line_tutorial.rst