v0.2.2 - first public 0.2.x cumulative release

PlantSim-Agent v0.2.2 - first public 0.2.x cumulative release

This document records the v0.2.2 release of PlantSim-Agent. The package
reports version 0.2.2, and the release is published with the v0.2.2 tag.

This is the first public 0.2.x release after v0.1.1. It consolidates the
previously unreleased work from the 0.2 development line rather than
representing only the final runtime milestone. The release covers retrieval
and installation safety, the COM compile loop, measurable code-generation
evaluation, bounded runtime evidence, session-evidence handling, and the
release integration gates. The intermediate development milestones were not
published as separate public releases.

Release overview

Area	v0.2.2 outcome
Help retrieval and safety	Focused lookup tools, fullmd navigation, source breadcrumbs, and safer skill loading
COM compile loop	Version-aware connection, compile_simtalk, sandbox validation, retry, and self-correction
Code-generation evaluation	12-task baseline and 36-task expanded Pilot with independent COM replay
Runtime evaluation	Versioned PS2504 fixture, typed assertions, strict admission, and Agent-generated runtime Pilot
Integration and release	VS Code smoke, citation review, cold-install checks, private evidence boundary, and sanitized public export

Help retrieval and installation safety

• Added smart_lookup for the exact-match, suggestion, and FTS fallback
  cascade, reducing the normal retrieval path from 5-10 MCP calls to 1-2.
• Added list_section for chapter, kind, and query filtering when a user needs
  to enumerate Help entries.
• Added chapter-aware fullmd indexing and suggestion fallbacks. Large single
  file Help results now use searchable breadcrumbs instead of broken direct
  links, while multi-file entries continue to use valid Markdown links.
• Reworked the plantsim-kb-qa cascade and aligned its Sources contract with
  citation-reviewer.
• Hardened installation so skills are not globally symlinked into
  ~/.copilot/skills/, preventing direct skill invocation from bypassing the
  orchestrator's citation-review workflow.
• Reworked the KB build and installation documentation, including the
  scripts/convert_help_pdf.py PDF-to-Markdown workflow and the Windows-only
  support boundary.

COM compile loop

• Added a version-aware Plant Simulation COM connection with project-version
  selection, lazy connection reuse, reconnect cleanup, and graceful
  degradation when COM is unavailable.
• Added the compile_simtalk MCP tool and a versioned PS2504 sandbox fixture
  for valid, invalid, and parameterized SimTalk.
• Added a code-author compile gate that feeds compiler errors back into the
  Agent for targeted self-correction, with a three-attempt limit and explicit
  compile status reporting.
• Added stable error codes for configuration, project, sandbox, COM, and
  compile-check failures. A failed COM call reloads the configured sandbox
  before retrying.

Code-generation evaluation

The compile evaluation moved from a qualitative demonstration to a reproducible
Pilot with private JSONL evidence, failure sources, and independent COM replay.

• The 12-task baseline reached a 100.0% final compile pass rate, with a 58.3%
  first-attempt pass rate and 100.0% recovery after retry.
• The expanded 36-task Pilot reached a 100.0% final compile pass rate, a 63.9%
  first-attempt pass rate, and 100.0% retry recovery across all 13 initial
  failures.
• Local COM replay matched all 36 final results. The private run records and
  replay artifacts remain outside the repository.

Bounded runtime evaluation

The runtime layer extends the compile loop to observable behavior, but only on
declared, deterministic fixtures and inputs.

• Added a versioned PS2504 runtime fixture with typed assertions and a clean
  fixture reload before each task.
• Added generate and repair task contracts, isolated serial worker
  execution, hard timeouts, and Behavior Pass Rate reporting with
  infrastructure errors kept separate.
• Added independent COM compile replay for every recorded attempt.
• Added strict capture-package validation for task and fixture inputs, fixture
  identity, Plant Simulation version, duplicate task IDs, complete MCP
  payloads, session association, and independent Agent provenance.
• Added task admission categories and the session-derived collector. Incomplete
  transcript evidence remains candidate-only instead of entering strict
  evaluation records.
• The Agent-generated runtime Pilot covered 6 unique tasks from 7 historical
  sessions. It achieved a 100.0% Behavior Pass Rate, 100.0% final compile pass
  rate, 100.0% retry recovery, and 100.0% compile/runtime replay agreement
  across 7 recorded attempts, including one repair retry.
• The private real-session evidence was re-normalized with the current
  collector and evaluator and reproduced on the local Plant Simulation 25.4
  environment. The source session evidence, capture package, and generated
  runtime results remain outside the repository.

Integration and release gates

• The manual VS Code smoke confirmed that @plantsim-copilot appears in the
  Agent picker, the MCP server starts, a Plant Simulation question returns its
  Sources block, and the orchestrator dispatches citation-reviewer in the
  same Copilot turn. The reviewer returned ok.
• Automated cold-install checks, live session capture/evaluation replay, and
  repeatable local PS2504 COM validation passed.
• Public export rules exclude private Help data, session evidence, caches,
  bytecode, and internal workspace paths.

Evidence boundary

The reported results apply only to the declared PS2504 fixture, task inputs,
trigger conditions, and observable assertions. They do not establish general
semantic correctness for arbitrary Plant Simulation models,
project-wide changes, or long-running stochastic simulations.

AMR routing and scheduling, event-driven or parameterized Method scenarios,
cross-Method project patches, random or long-running simulations, and general
model semantic correctness remain outside the v0.2 release boundary.

Release status

The v0.2 release gates are complete and the cumulative release is published as
v0.2.2. The public release history intentionally moves from v0.1.1 to
v0.2.2; no intermediate 0.2 development milestone was published as a
separate public version.

Full Changelog: v0.2.2...v0.2.2