Skip to content

codegen: input.color metadata reports a color type with a packed integer default (#231) - #251

Merged
luisleo526 merged 3 commits into
mainfrom
cx/iss-231
Oct 25, 2026
Merged

luisleo526 merged 3 commits into
mainfrom
cx/iss-231

Conversation

@luisleo526

Copy link
Copy Markdown
Contributor

Fixes #231. The input metadata for an input.color now reports a color type and the default as the packed 0xAARRGGBB integer the input setter accepts, so reported defaults round-trip through the setter (before: type string, default color.red).

Downstream: pineforge-hpo accepts color inputs as of hpo #80 (merged), so hpo keeps validating sweeps for color inputs after this change.

Tests: tests/test_input_color_manifest.py + updated manifest/receipt tests. Lab proof on engine main: 10505 passed, 221 skipped, 0 failures. Reviewed (REV-CX GO). Docs: README, PUBLIC_CONTRACT, CHANGELOG.

🤖 Generated with Claude Code

luisleo526 and others added 3 commits October 25, 2026 20:08
Brings the branch up to date with codegen main, which now holds the
strategy.account_currency fix (#227, #250). CHANGELOG.md conflicted in the
Unreleased section only; both bullets are kept (the input.color metadata fix
of this branch first, then the account_currency fix from main). No other file
conflicted.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
@luisleo526
luisleo526 merged commit f8a31b7 into main Oct 25, 2026
16 checks passed
luisleo526 added a commit that referenced this pull request Oct 26, 2026
## What

Replaces the three-bullet `## Unreleased` block of `CHANGELOG.md` with the full planned-1.8.0 entry and its migration notes. `CHANGELOG.md` is the only file changed (+54/-10). Documentation only.

## Why

The release workflow creates the GitHub release with a fixed install line and no migration notes; the notes users read are this file. They must be on main before the release dispatch. The heading stays `## Unreleased` until the `v1.8.0` tag exists, as the file's own release note policy says; a separate docs-only commit dates it after the tag.

## Content

- Compatibility and migration: exact pairing with engine `v1.8.0`; regenerate strategy C++ and relink; the new `color` input type with its unsigned packed `0xAARRGGBB` default that hosts must preserve; the `strategy.account_currency` emitted-C++ change (intended to change only for scripts that read it; not a byte comparison against 1.7.0); CRLF and lone CR line endings accepted.
- The four pull requests merged after `v1.7.0`: #251 (#231), #250 (#227), #252 (#230), #248 (CHANGELOG backfill, no behaviour change).
- One sentence about pineforge-hpo accepting color inputs from its 1.8.0 release; true of hpo main today, re-checked against hpo's 1.8.0 entry before the release.

## Checks

- Read as a committed diff by an independent reviewer: GO. The four commits since `v1.7.0` are the four bullets.
- The `color.red` value `4294063685` (`0xFFF23645`) was recomputed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Supersedes #256 (same change; the commit message no longer carries an internal tracking id).
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.

input.color metadata says type string, default color.red, but the engine setter wants a packed 0xAARRGGBB integer

1 participant