v0.1.100: Introduce the first operational MRWIF source-spec surface

Summary

This release introduces the first operational MRWIF surface in rwif-builder.

MRWIF is no longer just a documented bridge-realm concept. It now has an initial, working source-spec implementation with validation, inspection, and diff support for explicit multimodal correspondence review.

What’s Included

• added a new mrwif package with:
  • source-spec validation
  • source-spec inspection
  • source-spec diff
• added new CLI commands:
  • mrwif-validate-spec
  • mrwif-inspect
  • mrwif-diff
• defined the initial MRWIF document shape around:
  • linked_artifacts
  • intent_mappings
  • interpretation_records
  • revision_traces
• updated realm documentation so MRWIF is now represented as an initial operational bridge surface rather than a draft-only target
• added focused regression coverage for the new MRWIF flow

Why This Release Matters

This is the first release where MRWIF becomes real inside the repo.

Until now, the project had operational semantic, audio, and partial visual reasoning surfaces, but no implemented bridge realm for explicit multimodal correspondence. v0.1.100 closes that gap with a deliberately narrow first slice that is inspectable, testable, and ready to extend.

Validation

• added focused MRWIF regression coverage in tests.test_mrwif
• validated combined regressions with:

PYTHONPATH=src python -m unittest tests.test_vrwif tests.test_arwif tests.test_mrwif

Release Notes v0.1.96

Release Notes v0.1.96

Summary

• added light-color roster deltas to VRWIF diff and batch analysis
• documented and regression-tested the narrower light-color count review signal

Details

• vrwif-diff now reports light_colors_count_delta alongside light_colors_changed
• vrwif-batch-diff-analyze now aggregates recurring light-color roster changes through pairs_with_light_colors_count_delta and total_light_colors_count_delta

Validation

• targeted regression coverage added in tests/test_vrwif.py
• intended validation flow remains PYTHONPATH=src /home/mogir/Desktop/Big_AI_Brain/.venv/bin/python -m unittest tests.test_vrwif tests.test_arwif

v0.1.95

Summary

• Added appearance-class roster deltas to VRWIF diff and batch analysis
• Expanded the VRWIF review surface with a narrower signal for scene taxonomy drift

What Changed

• vrwif-diff now reports appearance_classes_count_delta alongside appearance_classes_changed
• vrwif-batch-diff-analyze now aggregates appearance-class roster drift through:
  • pairs_with_appearance_classes_count_delta
  • total_appearance_classes_count_delta
• Updated VRWIF documentation to reflect appearance-class diversity growth or shrinkage as a first-class review signal

Why This Matters

This keeps VRWIF moving along the same narrow, inspect-backed path as the recent object, group, and light roster work. Instead of only reporting that appearance classes changed, the review layer now captures whether scene appearance-class diversity actually grew or shrank across revisions.

Validation

• Added targeted regression coverage in tests/test_vrwif.py
• Verified the focused VRWIF suite:
  • PYTHONPATH=src /home/mogir/Desktop/Big_AI_Brain/.venv/bin/python -m unittest tests.test_vrwif
• Verified the standard combined release regression:
  • PYTHONPATH=src /home/mogir/Desktop/Big_AI_Brain/.venv/bin/python -m unittest tests.test_vrwif tests.test_arwif

Included Files

• src/rwif_builder/vrwif/diff.py
• src/rwif_builder/vrwif/batch.py
• tests/test_vrwif.py
• docs/VRWIF.md
• pyproject.toml
• src/rwif_builder/__init__.py
• RELEASE_NOTES_v0.1.95.md

v0.1.94

Summary
Added light-id roster deltas to VRWIF diff and batch analysis
Documented and regression-tested the narrower light-id count review signal
Details
vrwif-diff now reports light_ids_count_delta alongside light_ids_changed
vrwif-batch-diff-analyze now aggregates recurring light-id roster changes through pairs_with_light_ids_count_delta and total_light_ids_count_delta
Validation
Added targeted regression coverage in tests/test_vrwif.py
Validated with the full intended regression flow:
PYTHONPATH=src python -m unittest tests.test_vrwif tests.test_arwif
Release packaging succeeded, producing:
dist/rwif_builder-0.1.94.tar.gz
dist/rwif_builder-0.1.94-py3-none-any.whl
Included in this release
ARWIF narrow review-signal expansions accumulated through the 0.1.x line
VRWIF review-signal expansions including object roster, camera trajectory, lighting presence, and light-id count drift
Documentation, checklist, and release-payload cleanup for release readiness

rwif-builder v0.1.17

rwif-builder v0.1.17

Feature release adding ARWIF batch export.

What Changed

• adds rwif arwif-batch-export to export multiple ARWIF artifacts into strict YAML or JSON source specs in one command
• writes exported specs into a target --output-dir using predictable .export.yaml or .export.json filenames and defaults to YAML unless --format json is requested
• reuses the same strict-spec-compatible export path as single-artifact arwif-export and returns aggregated machine-readable totals for exported files, states, and oscillator entries
• extends the ARWIF integration suite with end-to-end batch export coverage across multiple artifacts
• updates the README, CLI reference, ARWIF mini-spec, and examples guide to document batch export as the next collection-scale authoring companion to batch build, diff, and render

Scope

This release extends ARWIF batch workflows into source-spec emission. Teams can now export multiple validated .arwif artifacts into reusable strict source documents in one pass and capture collection-level metadata for CI, migration review, and round-trip authoring flows.

rwif-builder v0.1.16

rwif-builder v0.1.16

Feature release tightening ARWIF batch diff with optional file output.

What Changed

• adds an optional --output path to rwif arwif-batch-diff so aggregated pairwise diff reports can be persisted to disk
• infers report format from the destination suffix and writes .json, .yaml, or .yml using the same machine-readable artifact convention already used by ARWIF normalization and export flows
• returns report_output and report_format fields in the batch diff payload when a persisted report is requested
• extends the ARWIF integration suite to verify the batch diff payload and persisted report document stay aligned
• updates the README, CLI reference, ARWIF mini-spec, and examples guide to document batch diff report output for CI and review pipelines

Scope

This release tightens the existing ARWIF batch diff workflow rather than broadening it. Teams can now keep the same explicit pairwise comparison contract from v0.1.15 while optionally saving the aggregated diff report as a reusable machine-readable artifact for review, automation, and release signoff.

rwif-builder v0.1.15

rwif-builder v0.1.15

Feature release adding ARWIF batch diff.

What Changed

• adds rwif arwif-batch-diff to compare multiple ARWIF artifact pairs in one command
• accepts explicit pairwise --left and --right artifact collections so baseline and candidate comparisons stay aligned without inventing directory conventions
• reuses the same state-level and metadata diff flow as single-artifact arwif-diff and returns aggregated machine-readable totals for changed, unchanged, invalid, and incompatible pairs
• extends the ARWIF integration suite with end-to-end batch diff coverage for both changed and unchanged pairs
• updates the README, CLI reference, ARWIF mini-spec, and examples guide to document batch diff as the next collection-scale comparison step after batch render

Scope

This release extends ARWIF batch workflows into pairwise comparison and review. Teams can now diff multiple baseline and candidate artifact pairs in one pass, capture the full per-pair ARWIF diff payloads, and summarize collection-level change totals for CI, QA, and release signoff.

rwif-builder v0.1.14

rwif-builder v0.1.14

Feature release adding ARWIF batch render.

What Changed

• adds rwif arwif-batch-render to render multiple ARWIF artifacts into .wav outputs in one command
• writes rendered audio into a target --output-dir while reusing the same reference synthesis path as single-artifact arwif-render
• returns an aggregated machine-readable payload with per-artifact render results plus collection-level counts for processed artifacts, successful renders, failures, and total rendered duration
• extends the ARWIF integration suite to verify end-to-end batch render output generation and aggregate payload behavior
• updates the README, CLI reference, ARWIF mini-spec, and examples guide to document batch render as the next batch export step after batch build

Scope

This release extends ARWIF batch workflows from authoring and migration into playback export. Teams can now render multiple validated .arwif artifacts into WAV outputs in one pass and capture both per-artifact render metadata and collection-level totals for automation, QA, and release packaging.

rwif-builder v0.1.13

Feature release adding ARWIF batch build.

What Changed

• adds rwif arwif-batch-build to build multiple strict ARWIF source specs into .arwif artifacts in one command
• writes built artifacts into a target --output-dir while reusing the same strict validation and build path as single-spec arwif-build
• returns an aggregated machine-readable payload with per-spec build results plus collection-level counts for processed specs, successful builds, failures, and total oscillator entries
• extends the ARWIF integration suite to verify end-to-end batch build output generation and aggregate payload behavior
• updates the README, CLI reference, ARWIF mini-spec, and examples guide to document batch build as the next batch authoring step after batch normalization

Scope

This release extends ARWIF batch authoring from migration workflows into direct strict-spec production. Teams can now build multiple validated .arwif artifacts from source specs in one pass and capture the full per-spec build results in a single machine-readable payload for CI and release pipelines.

rwif-builder v0.1.12

Feature release adding ARWIF batch normalization.

What Changed

• adds rwif arwif-batch-normalize to run the existing ARWIF normalization workflow across multiple artifacts in one command
• writes normalized strict source specs into a target --spec-dir and can optionally collect rebuilt strict artifacts, normalization reports, and assumptions manifests into sibling output directories
• reuses the same single-artifact normalization logic so injected defaults, preserved metadata, validation behavior, and assumptions-manifest contents stay consistent between single and batch workflows
• returns an aggregated machine-readable payload with per-artifact results plus collection-level counts for processed artifacts, successful normalizations, failures, and total assumption entries
• extends the ARWIF integration suite to verify end-to-end batch normalization output generation and aggregate payload behavior
• updates the README, CLI reference, ARWIF mini-spec, and examples guide to document batch normalization as the next automation step after assumptions manifests

Scope

This release moves ARWIF normalization from single-file migration into collection-scale operations. Teams can now normalize multiple prototype artifacts in one pass while keeping strict specs, rebuilt artifacts, reports, and assumptions manifests organized into predictable directories for CI and review workflows.