Port resolveQuests, progression and nextContinuations (182/182 vectors)

[mwburke]

Adds the last three conformance families this port skipped. With them, all 182 vectors at the v0.14.0 pin run and pass.

Changes

• resolve_quests(state, project) fires quest stage onComplete and outcome effects when their condition (completeWhen/reachedWhen) holds.
  • Each item fires once, recorded in quest_fired, and the pass repeats until nothing new fires.
  • Order is quests by id, then stages, then outcomes, each in array order.
  • Effects with no condition never fire on their own, and it never writes quest_stages.
  • Returns {state, firings}.
• Progression: level_for_xp, points_earned, available_points, effective_skill, skill_cap, recompute_skills, and invest_skill_point. invest_skill_point does nothing unless a point is available and the skill is below its cap.
  • Levels and points are derived from total-earned xp.
  • Per-skill max comes from an optional skills registry.
• next_continuations(state, project, visited, current_dialogue_id) decides what to offer when a scene ends.
  • A pending cutscene comes first.
  • Next, any character whose active_dialogue__ flag is set and whose winning offer reads that flag at the top level. These are marked queued and ignore the visited set.
  • Otherwise, each character's best eligible offer, with the visited filter.
  • clear_active_dialogue and clear_pending_cutscene clear the flag and the pending cutscene once the host has used them.
• The runner now runs all three families instead of skipping them.
• README: scoreboard, "11 of 11", and a list of the new functions. It also notes that main now meets the README's own v1.0.0 bar ("complete against the spec"), but no tag is created.

Verification

• godot --headless --script tests/conformance_runner.gd (Godot 4.4): 182 passed, 0 failed, 0 skipped.
• Mutation checks:
  • Caught: removing the once-only check, the skill-cap guard, or the forced-offer flag test.
  • README's >=→> example: still 6 failures.
  • Not caught: removing the fixpoint loop. The vectors' cascade case happens to run in quest-id order, so a single pass reaches it. This is a gap in the upstream vectors, which a port never hand-edits. It needs a vector upstream where a later quest's firing satisfies an earlier quest's condition.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Wc6JEuMmSXJEJSRYwGjn1f

---

Generated by Claude Code