Weft v0.4.47

Weft 0.4.47

This distribution retains the 0.4.46 compiler implementation and repairs its
release capacity fixture. The 1,000-record, twelve-field request now uses UMF
0.10.0 with coherent source and binding hashes; all five rejection controls and
resource bounds remain unchanged. The original capture remains historical
evidence. This derived compiler fixture does not claim fresh database execution.
The 0.4.46 tag produced no published wheels.

Truss raw reads and related-key reads now consume current UMF 0.10.0 source,
including original Record/Field IDs when authored names are absent. Authored
names retain precedence. Compile-request and logical-plan 0.2.7 schemas now
admit the current core version. Date, binary and export fixtures use current
source documents.

The raw-read profile retains object-valued umf.ddd Record metadata and
hohfeld.view Record/Field metadata without interpreting those payloads.
Unknown selected extensions, malformed payloads and unresolved semantic-type
references still refuse. Original source bytes and model pins are preserved.
This change adds no host authorization or native execution authority.

Current source-exact PostgreSQL/Lakebase reads require core 0.10.0 throughout
the model, ColumnSet and original binding. Mixed or older pins refuse. Selected
Record members, including binary fields and vector leaves outside the scalar
binding, use the existing indexed model admission pass. Held action, search and
Spark profiles retain their separately scoped contracts. Term-filter source
metadata preserves the already-admitted core version, including 0.10.0.

PostgreSQL raw reads and related reads now include compiler-owned dbapiSql
and dbapiParameterOrder; search and raw-bulk programs carry these fields in
their embedded read templates. Their final executable transports retain their
existing contracts. Token spans preserve original
SQL bytes, quoted content, Unicode and literal percent/dollar characters;
bindings follow placeholder occurrence order, including repeats. Related-read
transport is generated after composing source and target parameter inventories.
Both representations are included in the program's structural digest. Hosts
must retain these compiler fields when checking that digest rather than replace
them with a host SQL rewrite. Truss's registered-engine compiler APIs retain their
existing transport.

The preceding DBAPI cohort recorded 183 PostgreSQL library passes and 187
generated-client/native PostgreSQL 18.6 assertions with Psycopg 2/3 and SQLAlchemy sync/async
transports. See the exact source and wheel evidence.
Those native assertions use a bounded fixture executor, not UMF's legacy
reviewed.py production executor. The compatible UMF consumer successor additionally passes 23 actual core 0.10
compilation, production-executor and transport tests against PostgreSQL 18; two
generated-reporting tests were skipped because their fixture was absent. This
consumer check uses the rebuilt compiler CLI, not a published wheel. This profile does not qualify
table admission, mutations, DDL, policy/grant generation or complete Praxis
lifecycle integration.

The candidate Rust workspace passed locally with the candidate Truss and Ashlar
registrations. Focused qualified raw-read and related-key checks also passed.
Publication requires the frozen source's conformance workflow and every exact
platform wheel's existing packaging, compiler, capacity and ABI smoke checks.
Actual installed Truss native qualification and its full stress matrix remain
Truss release gates; this compiler release does not claim those gates passed.