Repository navigation
PowerBridge 0.12.0
Highlights:
- Strategy
Printoutput is shown: on stderr, in a file with--print FILE, or asprintsfromrun_el/run_oracle, the same on both engines. - Each GitHub Release carries a
SHA256SUMSfile and a build provenance attestation per file, and the release workflow tests the built wheels before attaching them. pl_examplesalso writes the example configs andhand_written.py, so the documented commands work after a wheel install.- When the native kernel cannot run a program, the fallback note is one line saying the Python engine ran and why.
Added
- Each GitHub Release now carries a
SHA256SUMSfile over every sdist and wheel and a build provenance attestation for each file, so a download can be checked withsha256sum -candgh attestation verify; see SECURITY.md (#251). Printoutput is shown:pl_runandpl_oraclewrite a strategy'sPrintlines to stderr, or to a file with the new--print FILE, andrun_el/run_oraclereturn them asprints. The native kernel prints the same lines as the Python engine. Fills, digests and stdout are unchanged. Generated Python callspl_print(...)instead ofprint(...)(#254).pl_examplesalso writesexamples/configs/ES.json,examples/configs/NQ.jsonandexamples/hand_written.py, so the USAGE.md and PYTHON_STRATEGIES.md commands work after a wheel install; CI now runs the documented commands from an empty directory against the built wheel, and the docs mark unreleased features new in the next release (#N), checked against this section (#258).
Changed
- When the native kernel is installed but cannot run a program, the note on stderr is now one line saying the Python engine ran and why (
[pl_oracle] note: ran on the Python engine because the native kernel does not support bar_ref series yet; ...);-vadds the kernel's own refusal text (#254). - The release workflow now tests the built wheels before anything is attached or published: the
powerbridgewheel runs the public tier from a clean venv, and eachpowerbridge-accelwheel runs a native-vs-Python digest check on the examples on its own platform runner (#246). run_elno longer takes the private_python_path_notifykeyword;pl_runuses an internal helper instead (#242).- The maintainer-only capture reader
analyze_capture.pymoved frompl_transpiler/tools/to the repository'stools/, so the wheel no longer ships it; the unusedtools/measure_audit_packet.pyis gone, andground_truth/captures/MANIFEST.mdis now a short data card (#248). - Internal: strict mode and the unimplemented-call counts are kept per run, and the EL emitter's comment maps per call, so two
run_el/run_oracleruns with different strictness no longer interfere. (Emits in threads could still mix up comments until #256.) The engine's trade-stat trace hook isFillEngine(capture_stats=...)/set_capture_stats()instead of a fixture-named private flag. Output and digests are unchanged (#244).
Fixed
- Mirror-dialect output (
pl_transpile --dialect mirror) no longer reads_statewhen a Variable is passed toCrossesAbove/CrossesBelowor another series function; it passes the bare variable, as the docs say.el_emitgives the same EasyLanguage as before, and runnable output is unchanged (#242). pl_run/pl_oracle --helpno longer point atexamples/configs/ES.jsonorcsv_to_pbar, which a wheel install does not have (#242).- docs/API.md shows the full
run_el/run_oraclesignatures (drawings,drawing_case_id,drawing_tape,use_native), says whyseed_warmupdefaults toTrueinrun_elandFalseinrun_oracle, and a test now fails when a documented signature drifts from the code. USAGE.md and PYTHON_STRATEGIES.md use--dialect mirrorand drop the redundant--max-bars-back auto(#242). - LIMITATIONS.md and USAGE.md no longer call MaxBarsBack opt-in or say the default stays 0: they describe
autoas the default and0as the opt-out, and the USAGE.md section is shorter. ACCEL.md no longer listsPrintas refused by the native kernel. A test now fails if those stale phrases return (#250). emit_el,parseandtranspilecalled from several threads at once no longer mix up comments between sources: the lexer returns comments with its tokens (tokenise_with_comments) instead of through the module-levellexer.last_commentslist, which is gone, and the parser's shared lex/parse cache is locked. Output is unchanged (#256).