# Generated Scene Runtime Semantics Offline Validation Bundle Refresh Design

Date: 2026-04-21

## Context

The runtime-semantics hardening rerun has produced a refreshed 102-scene bundle:

- `examples/scene_skill_102_runtime_semantics_rematerialization_2026-04-21`

The validation refresh confirms:

- `materialized = 102 / 102`
- `deterministicReady = 102 / 102`
- `staticPass = 102 / 102`
- `directMockPass = 102 / 102`
- `pseudoProdSelected = 7`

The previous offline validation bundle under `dist/sgclaw_102_pseudoprod_validation_bundle_2026-04-20` is now stale because it was based on the pre-runtime-semantics materialization.

## Problem

Pseudo-production validation must not continue from the stale 2026-04-20 package. The inner-network operator needs a refreshed offline bundle that carries the new canonical 2026-04-21 runtime-semantics skills and the refreshed pseudo-production handoff assets.

## Goal

Create a bounded plan for refreshing a portable offline validation bundle for the 2026-04-21 runtime-semantics skill set.

The bundle must be suitable for copying to an inner-network machine that does not have `cargo`, Rust sources, or repository test infrastructure.

## Target Bundle

Target directory:

- `dist/sgclaw_102_runtime_semantics_validation_bundle_2026-04-21`

Required shape:

```text
dist/sgclaw_102_runtime_semantics_validation_bundle_2026-04-21/
  sg_claw.exe
  skills/
  README.md
  BATCH_001.md
  BUNDLE_MANIFEST.json
  docs/
    SCENE_INDEX.md
    scene_skill_102_index.json
  handoff/
    scene_skill_102_runtime_semantics_pseudoprod_execution_handoff_2026-04-21.json
    scene_skill_102_runtime_semantics_pseudoprod_evidence_checklist_2026-04-21.json
    scene_skill_102_runtime_semantics_pseudoprod_execution_record_template_2026-04-21.json
    scene_skill_102_runtime_semantics_deterministic_invocation_readiness_2026-04-21.json
    scene_skill_102_runtime_semantics_natural_language_parameter_readiness_2026-04-21.json
    scene_skill_102_runtime_semantics_natural_language_invocation_samples_2026-04-21.json
    scene_skill_102_runtime_semantics_full_direct_mock_execution_2026-04-21.json
  resources/
    rules-102-business-targets-candidate.json
    rules-102-business-targets-merged.json
    rules-102-business-targets.patch
  results/
  evidence/
```

## Fixed Inputs

1. `examples/scene_skill_102_runtime_semantics_rematerialization_2026-04-21`
2. `tests/fixtures/generated_scene/generated_scene_runtime_semantics_rematerialization_manifest_2026-04-21.json`
3. `tests/fixtures/generated_scene/generated_scene_runtime_semantics_rematerialization_failures_2026-04-21.json`
4. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_deterministic_invocation_readiness_2026-04-21.json`
5. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_natural_language_parameter_readiness_2026-04-21.json`
6. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_natural_language_invocation_samples_2026-04-21.json`
7. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_pseudoprod_execution_handoff_2026-04-21.json`
8. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_pseudoprod_evidence_checklist_2026-04-21.json`
9. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_pseudoprod_execution_record_template_2026-04-21.json`
10. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_full_direct_mock_execution_2026-04-21.json`
11. Current locally built `sg_claw.exe`
12. Optional rule assets under `resources/`

## Required Bundle Semantics

1. The `skills/` directory must be copied from the 2026-04-21 runtime-semantics rematerialization output.
2. The bundle must not reuse skills from `scene_skill_102_final_materialization_2026-04-19`.
3. The bundle must not reuse the old 2026-04-20 offline package as the source of truth.
4. The first batch must be derived from the refreshed 2026-04-21 pseudo-production handoff.
5. `BATCH_001.md` must show the exact natural-language input and page URL fields expected by `sg_claw_service_console.html`.
6. The README must explain that `skillsDir` must be configured with the exact JSON field name `skillsDir`.
7. The README must state that credentials, cookies, tokens, VPN secrets, and private keys must not be stored in the bundle.

## Scope

Allowed:

1. Create a new bundle directory under `dist/`.
2. Copy the refreshed 102 skill packages into the bundle.
3. Copy refreshed handoff/readiness/mock assets into the bundle.
4. Copy rules candidate assets into the bundle when present.
5. Write bundle README, batch instructions, manifest, and empty evidence/results directories.
6. Write a bundle refresh report.

Forbidden:

1. No `src/` changes.
2. No generated skill edits.
3. No rematerialization rerun.
4. No validation refresh rerun.
5. No pseudo-production execution.
6. No production browser, production network, or credentials.
7. No official board updates.
8. No deletion of the old 2026-04-20 bundle.

## Validation

The bundle refresh execution must verify:

1. `skills/` contains exactly 102 skill directories.
2. Every skill directory contains required package files.
3. Copied `scene.toml` files are parseable enough for structural presence checks.
4. `BUNDLE_MANIFEST.json` is valid JSON.
5. Copied handoff JSON assets are valid JSON.
6. `BATCH_001.md` contains exactly the selected pseudo-production batch entries from the refreshed handoff.

## Stop Statement

Stop after the refreshed offline bundle and bundle refresh report are published.

Do not execute inner-network validation inside this route.