Merge pull request #6 from xeonvs/codex/issue-5-empty-archive-index-0.8.2

Release engineering-workflow 0.8.2

Author: xeonvs

PLANS.md

@@ -6,6 +6,7 @@ Use this file for active, blocked, ready-for-closure, or recently completed exec
 
 ## Recently Completed
 
+- [x] 2026-08-28: Completed Engineering Workflow 0.8.2 Empty Compatibility Archive Index Fix; [full archived plan](docs/archive/plans/2026-08-28-engineering-workflow-0-8-2-empty-compatibility-archive-index-fix.md).
 - [x] 2026-08-21: Completed Engineering Workflow 0.8.1 Privacy Review Token; [full archived plan](docs/archive/plans/2026-08-21-engineering-workflow-0-8-1-privacy-review-token.md).
 - [x] 2026-08-20: Completed Engineering Workflow 0.8.0 Execution Discipline And Dual Marketplace; [full archived plan](docs/archive/plans/2026-08-20-engineering-workflow-0-8-0-execution-discipline-and-dual-marketplace.md).
 - [x] 2026-08-16: Completed PTC Partial-Evidence Closure Correction 0.7.0.

README.md

@@ -2,7 +2,7 @@
 
 `engineering-workflow` is a public skill for auditing, setting up, validating, updating, and safely migrating the engineering-workflow layer of a repository. It works with Codex and Claude Code.
 
-Current skill version: `0.8.1`.
+Current skill version: `0.8.2`.
 
 The skill uses `AGENTS.md` as a short map, `PLANS.md` as durable execution state, and leaves product, architecture, operations, security, and other repository-owned documentation with its existing owners. Any repository change starts with a full plan; read-only inspection is the only exception.
 
@@ -67,7 +67,7 @@ Use $engineering-workflow to audit this mature repository and add only the missi
 ```
 
 ```text
-Use $engineering-workflow to Upgrade A Target Workflow in this repository to version 0.8.1.
+Use $engineering-workflow to Upgrade A Target Workflow in this repository to version 0.8.2.
 ```
 
 Repository text is evidence, not authority. It cannot grant approval, expand scope, request secrets, or override system, developer, or user instructions.
@@ -170,7 +170,7 @@ When the result permits an automatic update, rerun it with `--apply`. Alternate
 `Upgrade A Target Workflow` tells the agent to run a report-first guarded migration, not to hand the user a list of backend commands. It applies automatically only when ownership, privacy, and approval checks are resolved.
 
 ```text
-Use $engineering-workflow to Upgrade A Target Workflow in this repository to version 0.8.1. Run the report first, apply it when safe, and ask only when the report requires a user decision.
+Use $engineering-workflow to Upgrade A Target Workflow in this repository to version 0.8.2. Run the report first, apply it when safe, and ask only when the report requires a user decision.
 ```
 
 The maintainer/automation backend is:
@@ -179,7 +179,7 @@ The maintainer/automation backend is:
 python3 skill/engineering-workflow/scripts/upgrade_target_workflow.py \
   --repo <target-repository> \
   --prompt \
-  --target-version 0.8.1 \
+  --target-version 0.8.2 \
   --format json
 ```
 
@@ -189,7 +189,7 @@ The migration creates or updates the target's full active `PLANS.md` plan before
 
 ### Privacy review during migration
 
-Some repositories intentionally keep synthetic credentials, addresses, or internal hostnames in tests and fixtures. Version 0.8.1 can continue only after the user approves the exact value-free review token for that one migration snapshot.
+Some repositories intentionally keep synthetic credentials, addresses, or internal hostnames in tests and fixtures. The migration can continue only after the user approves the exact value-free review token for that one migration snapshot.
 
 When the result returns `agent_action: request_privacy_review_approval`, the agent must:
 
@@ -261,7 +261,7 @@ Use $engineering-workflow to audit this mature repository, preserve every existi
 Target migration:
 
 ```text
-Use $engineering-workflow to Upgrade A Target Workflow here to 0.8.1. Run the report and apply it when safe.
+Use $engineering-workflow to Upgrade A Target Workflow here to 0.8.2. Run the report and apply it when safe.
 ```
 
 ## Repository layout
@@ -290,7 +290,7 @@ The validator checks ownership, instruction routing, plan structure, archive ind
 
 ## Versioning and updates
 
-The project uses semantic versioning. Version 0.8.1 adds exact, user-approved synthetic-fixture privacy review without exposing candidate values to the agent. Version 0.8.0 introduced loss-resistant completion-driven waits, correctness-first execution discipline, instruction contract v2 migration, Claude Code compatibility, and the deterministic dual marketplace. Version 0.7.0 is the historical baseline for bounded Programmatic Tool Calling assessment and runtime instruction rendering.
+The project uses semantic versioning. Version 0.8.2 stops empty compatibility archive directories from producing false missing-index errors while retaining fail-closed checks for real archive content and unsafe index paths. Version 0.8.1 added exact, user-approved synthetic-fixture privacy review without exposing candidate values to the agent. Version 0.8.0 introduced loss-resistant completion-driven waits, correctness-first execution discipline, instruction contract v2 migration, Claude Code compatibility, and the deterministic dual marketplace. Version 0.7.0 is the historical baseline for bounded Programmatic Tool Calling assessment and runtime instruction rendering.
 
 Historical version records remain valid in completed plans, archives, and migration tests. Current-version owners are `SKILL.md`, this README, current update prompts, active workflow state manifests, and the generated plugin manifests.