Skip to content

Handle explicit pre-1 package home without HOME - #144

Merged
RobLe3 merged 1 commit into
mainfrom
fix/pre1-prepared-home-without-home
Oct 9, 2026
Merged

RobLe3 merged 1 commit into
mainfrom
fix/pre1-prepared-home-without-home

Conversation

@RobLe3

@RobLe3 RobLe3 commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • resolve the pre-1 preparation owner without eagerly evaluating the legacy HOME fallback
  • cover the native Windows environment where IICP_PRE1_PREPARED_PACKAGE_HOME is explicit and HOME is intentionally absent

Qualification evidence

The current successor-bound Windows shard-zero sentinel reached the Python package execution boundary and failed before case execution because dict.get(key, os.environ["HOME"]) evaluates the default eagerly. The root harness already propagates the explicit preparation boundary; this is the remaining owning-source correction.

This changes qualification tooling only. It does not change SDK product behavior, the frozen candidate, protocol semantics, or qualification credit. The failed AWS attempt remains diagnostic and a clean successor-bound retry is required.

Validation

  • python3 -m unittest discover -s scripts -p 'test_pre1*.py' — 90 passed
  • ruff check scripts/test_pre1_prepared_home.py — passed
  • the supported SDK test matrix executed by run_sdk_quality.py — three supported Python lanes each completed with 1,345 passed, 3 skipped, and 44 subtests passed

run_sdk_quality.py remains red because the repository currently reports 42 pre-existing Ruff findings in qualification scripts, including an existing B023 in pre1_package_execution.py; this change does not add to that debt.

Closes no issue; advances #119.

@RobLe3
RobLe3 merged commit 0cf46aa into main Oct 9, 2026
1 check passed
@RobLe3
RobLe3 deleted the fix/pre1-prepared-home-without-home branch October 9, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant