amos 73a5240295 Batches 21 and 18: add 74 calibrated tasks (40 Bos redo, 34 HWE code-gen)
Batch 21 (20261027-A-bos-redo-21) rebuilt 40 of the 53 rejected Bos-qiao
environments: hidden assertions that ran inside the candidate's process
now run in a trusted parent that reads observations from a low-UID
worker; gold bytes are unchanged. 9 were excluded for scope (ROS2,
oversize, security core), 3 are blocked because the source requires an
exec bit the platform does not freeze, 1 lacks requests/bs4 in trace6.

Batch 18 (20261026-C-hwe-codegen-18) adds its last 34 of 134 tasks; the
first 100 landed in 2f32624d.

Claude reviewed 74/74 USABLE against current digests, canonical
families, no ID or source overlap with main, plain public docs. Only the
new task directories are taken; the stale pre-batch-20 copies of
concur-release-capsule and resource-temp-link on the batch 21 branch and
both branches' progress notes stay as main has them. Difficulty is
unmeasured.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 10:23:12 +08:00

4.8 KiB

Contract

  1. This C++17 model is deterministic and uses no hardware, files, clocks, or services. Each live ag::Registry owns independent state. A new registry has no groups, attributes, or generation history. It is used through the declarations in group.hpp; copying a registry is disabled.

  2. All API arguments and numeric return fields use signed 64 bit Number. Parents range from 0 through 3, group IDs from 0 through 7, attribute names from 0 through 15, stored values from -100000 through 100000, and store counts from 0 through 64. publish counts range from 1 through 4, first + count is at most 16, writable is 0 or 1. Validate every argument before checking state. Invalid arguments return RANGE.

  3. publish(parent, group, first, count, writable) publishes the contiguous names beginning at first as one group. A live group ID in that parent returns EXISTS. Otherwise process names in ascending order: an already published name returns EXISTS. On failure withdraw names published by this call and preserve every earlier group, name, value, and generation history. A successful call creates all requested attributes with value 0 and the supplied writable flag. Its generation is one greater than the previous successful publication of that same parent/group, or 1 initially. Groups in different parents may use the same names and IDs.

  4. remove(parent, group) returns ABSENT if the group is not live. Success withdraws every attribute of that group and retains its generation history. It returns the removed generation and attribute count. Other groups remain unchanged. Repeated removal returns ABSENT.

  5. show(parent, name) returns ABSENT for an unpublished name. Success returns generation, owning group, current value, and writable. store(parent, name, value, count) checks for an unpublished name, then checks writable; these return ABSENT and READONLY respectively. A writable attribute with count 0 succeeds without changing the value. A positive count sets the value, including when value is 0. Success returns generation, owning group, resulting value, and accepted=count.

  6. group(parent, group) returns ABSENT for a nonlive group. Success returns generation, first name, count, and writable. list(parent) returns all live attributes in ascending numeric name order; each row has name, group, generation, value, and writable. The returned vector is a value copy and changes to it do not alter the registry.

  7. Code numeric values are OK=0, RANGE=1, EXISTS=2, ABSENT=3, READONLY=4. Successful Change fields are code, generation, published; published is the created or removed attribute count. On a failed Change, generation and published are 0. On a failed Reading, generation=0, group=-1, value=0, writable=0. On a failed Writing, generation=0, group=-1, value=0, accepted=0. On a failed GroupInfo, generation=0, first=-1, count=0, writable=0. A failed Listing has an empty attributes vector. Successful codes are OK; success fields follow clauses 3 through 6. Every unsuccessful API call preserves all public state.

  8. run_cli(input, output, diagnostic) creates a fresh registry on every invocation, including repeated calls in one process. It reads physical lines separated by LF and accepts a final line without LF. Space and tab separate tokens, and leading or trailing space or tab is allowed. Each numeric token is an optional + or - followed by one or more ASCII decimal digits fitting signed 64 bit. Other bytes, unknown verbs, missing or extra tokens, empty lines, and overflow produce ERR SYNTAX for that line without changing state. Numeric output uses ordinary decimal spelling with no leading plus, no redundant zeros, and no negative zero. This format does not depend on the caller's stream flags or locale. All emitted lines end with LF.

  9. CLI verbs and arguments are publish parent group first count writable, remove parent group, show parent name, store parent name value count, group parent group, and list parent. For an API error emit ERR CODE using the name from clause 7. Success outputs are OK publish generation published, OK remove generation published, OK show generation group value writable, OK store generation group value accepted, and OK group generation first count writable. A successful list emits OK list N followed by N lines ATTR name group generation value writable in API order. It accepts at most 128 physical lines, counting successful, syntax-error, and API-error lines alike. If another physical line exists, emit one ERR LIMIT and perform no command from that line or any later line. Empty input emits nothing. Input errors do not terminate earlier accepted processing. The function returns 0 and leaves diagnostic empty for every input. The executable and API observer emit only their specified stdout, keep stderr empty, and exit 0 after processing.