pineforge-codegen 1.5.0rc1__tar.gz → 1.6.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (74) hide show
  1. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/CHANGELOG.md +43 -9
  2. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/PKG-INFO +17 -16
  3. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/README.md +16 -15
  4. pineforge_codegen-1.6.0/VERSION +1 -0
  5. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/docs/PUBLIC_CONTRACT.md +4 -11
  6. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/analyzer/call_handlers.py +3 -3
  7. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/session_market.py +1 -1
  8. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/ta.py +36 -33
  9. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/types.py +2 -2
  10. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/visit_expr.py +2 -2
  11. pineforge_codegen-1.5.0rc1/VERSION +0 -1
  12. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/.gitignore +0 -0
  13. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/CONTRIBUTING.md +0 -0
  14. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/LEGAL.md +0 -0
  15. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/LICENSE +0 -0
  16. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/docs/codegen-coverage-gaps.md +0 -0
  17. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/docs/pine-cap-activation.md +0 -0
  18. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/__init__.py +0 -0
  19. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/analyzer/__init__.py +0 -0
  20. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/analyzer/base.py +0 -0
  21. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/analyzer/contracts.py +0 -0
  22. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/analyzer/diagnostics.py +0 -0
  23. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/analyzer/tables.py +0 -0
  24. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/analyzer/types.py +0 -0
  25. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/ast_nodes.py +0 -0
  26. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/block_locals.py +0 -0
  27. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/builtin_keywords.py +0 -0
  28. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/__init__.py +0 -0
  29. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/base.py +0 -0
  30. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/capabilities.py +0 -0
  31. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/checked_settings.py +0 -0
  32. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/collection_history.py +0 -0
  33. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/constant_fold.py +0 -0
  34. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/drawing.py +0 -0
  35. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/emit_top.py +0 -0
  36. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/helpers.py +0 -0
  37. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/helpers_syminfo.py +0 -0
  38. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/host_members.py +0 -0
  39. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/input.py +0 -0
  40. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/order_shapes.py +0 -0
  41. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/run_stops.py +0 -0
  42. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/security.py +0 -0
  43. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/tables.py +0 -0
  44. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/tv_number_format.py +0 -0
  45. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/visit_call.py +0 -0
  46. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/codegen/visit_stmt.py +0 -0
  47. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/collection_history.py +0 -0
  48. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/diagnostic_codes.py +0 -0
  49. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/diagnostics_catalog.json +0 -0
  50. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/errors.py +0 -0
  51. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/external_requests.py +0 -0
  52. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/finite_ta_length.py +0 -0
  53. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/lexer.py +0 -0
  54. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/library_inline.py +0 -0
  55. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/library_modules.py +0 -0
  56. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/library_v5.py +0 -0
  57. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/limits.py +0 -0
  58. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/matrix_overloads.py +0 -0
  59. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/method_binding.py +0 -0
  60. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/parser.py +0 -0
  61. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/pine_libraries.py +0 -0
  62. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/pine_spelling.py +0 -0
  63. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/pragmas.py +0 -0
  64. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/request_discovery.py +0 -0
  65. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/request_feed_inventory.py +0 -0
  66. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/security_contexts.py +0 -0
  67. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/session_reads.py +0 -0
  68. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/signatures.py +0 -0
  69. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/support_checker.py +0 -0
  70. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/symbols.py +0 -0
  71. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/timeframe_token_cli.py +0 -0
  72. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/tokens.py +0 -0
  73. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pineforge_codegen/tv_input_choices.py +0 -0
  74. {pineforge_codegen-1.5.0rc1 → pineforge_codegen-1.6.0}/pyproject.toml +0 -0
@@ -20,15 +20,49 @@ supported as exact pairs; on the 0.x line they are independent. See the
20
20
  the release commit. A prerelease note describes changes since the preceding
21
21
  prerelease or stable tag; the final stable note consolidates the series.
22
22
 
23
- ## 1.5.0 — Unreleased
24
-
25
- The planned number of the next release; it stays **Unreleased** until its tag
26
- exists, and the package version is unchanged. This entry records the diagnostic
27
- additions below and the report-contract documentation for the paired engine
28
- fix, and nothing else: the engine pairing, the rest of the content and the date
29
- of 1.5.0 are set when the release is prepared. The codegen change is
30
- diagnostics only; the report documentation adds no Python, JSON, diagnostic or
31
- emitted-C++ change of its own, and no analyzer or code-generation file differs.
23
+ ## 1.6.0 — 2026-10-17
24
+
25
+ A minor release of the exact engine/codegen pair, paired with engine `v1.6.0`
26
+ and dated 2026-10-17; the prerelease `1.6.0-rc.1` pairs with engine
27
+ `v1.6.0-rc.1`. This entry records what changed in this repository since 1.5.0,
28
+ and nothing else: after
29
+ [#203](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/203) added
30
+ the 1.6.0 changelog entry for `v1.6.0-rc.1`, only the final release-note and
31
+ pairing documentation updates landed before `1.6.0`.
32
+
33
+ ### Compatibility and migration
34
+
35
+ - The analyzer and the code generator do not change behavior: the only edits
36
+ under `pineforge_codegen/` since 1.5.0 are comments and docstrings in five
37
+ files (#202), so the C++ the transpiler emits for a script and the Python
38
+ and JSON contract are unchanged. No diagnostic code, severity or catalog
39
+ schema changes.
40
+ - The [release note policy](#release-note-policy) still applies: "A pair
41
+ change requires regenerated C++ and relinked strategy libraries, even
42
+ when the C ABI number is unchanged." Regenerate and relink against the
43
+ new engine's headers and static library.
44
+ - Engine behavior changes, including failure codes and the report contract,
45
+ are described in the paired engine's own release notes; this entry does
46
+ not summarize them.
47
+
48
+ ### Changes since 1.5.0
49
+
50
+ - Remove the 11 gate-corpus pines that copy probes leaving the engine corpus
51
+ ([#200](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/200)).
52
+ - Remove the subprocess time limits of CI tests and checks
53
+ ([#201](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/201)).
54
+ - Move the recorded US-listed, futures, forex and metal tapes of the tests to
55
+ the private fixtures, and reword the comments and docstrings that cited them
56
+ ([#202](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/202)).
57
+
58
+ ## 1.5.0 — 2026-10-12
59
+
60
+ A minor release of the exact engine/codegen pair, paired with engine `v1.5.0`
61
+ and dated 2026-10-12. This entry records the diagnostic additions below and the
62
+ report-contract documentation for the paired engine fix, and nothing else: the
63
+ codegen change is diagnostics only; the report documentation adds no Python,
64
+ JSON, diagnostic or emitted-C++ change of its own, and no analyzer or
65
+ code-generation file differs.
32
66
 
33
67
  ### Compatibility and migration
34
68
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: pineforge-codegen
3
- Version: 1.5.0-rc.1
3
+ Version: 1.6.0
4
4
  Summary: PineScript v6 to C++ transpiler that targets the pineforge-engine runtime.
5
5
  Project-URL: Homepage, https://github.com/pineforge-4pass/pineforge-codegen-oss
6
6
  Project-URL: Issues, https://github.com/pineforge-4pass/pineforge-codegen-oss/issues
@@ -327,7 +327,7 @@ for the changes in each release from 1.0.0 on and the release-note policy.
327
327
  ## Releases and this README
328
328
 
329
329
  <!-- Release lane: before a release is tagged, add it to the Engine pairing
330
- table and update every line that names `1.4.0` or `v1.4.0` as the current
330
+ table and update every line that names `1.6.0` or `v1.6.0` as the current
331
331
  release or pair (this section's version and date, the baseline paragraph at
332
332
  the top, the engine `src/source/` link, the `@pf-trace` note, the clone
333
333
  command and its example output, "This section describes …", the timing note)
@@ -337,10 +337,10 @@ hosted-server line name no version. -->
337
337
 
338
338
  This README ships with each release as its package description on PyPI
339
339
  (`pineforge-codegen`); releases from 0.7.0 on are also on npm as
340
- `@pineforge/codegen-pyodide`. It describes 1.4.0 (2026-10-08)
341
- and what changed since 0.10.4. The release's behavior was validated before
342
- tagging on codegen `bfc4ddce` with engine `b3192bfc`, excluding engine
343
- request #356. Those validation builds reported `1.3.0`; historical measurements
340
+ `@pineforge/codegen-pyodide`. It describes 1.6.0 (2026-10-17)
341
+ and what changed since 0.10.4. The 1.4.0 release's behavior was validated
342
+ before tagging on codegen `bfc4ddce` with engine `b3192bfc`, excluding engine
343
+ request #356; those validation builds reported `1.3.0`. Historical measurements
344
344
  below retain the versions on which they were run. The
345
345
  [PyPI release history](https://pypi.org/project/pineforge-codegen/#history)
346
346
  lists every release; the
@@ -349,9 +349,8 @@ covers 1.0.0 on and links the notes of earlier releases. A source install
349
349
  reports the version in `VERSION`, which the release workflow sets when it tags
350
350
  a release.
351
351
 
352
- Text that says "since 1.5.0" describes the source tree on `main`, not a
353
- published package: 1.5.0 is the planned number of the next release, and the
354
- statements about 1.4.0 keep their historical meaning.
352
+ Text that says "since 1.5.0" describes the 1.5.0 release and later versions;
353
+ the statements about 1.4.0 keep their historical meaning.
355
354
 
356
355
  ### Upgrading from 1.3.0
357
356
 
@@ -411,8 +410,8 @@ It does **not** own execution semantics. Order lifecycle, bracket legs,
411
410
  fill-price and slippage rules, `process_orders_on_close` / `calc_on_order_fills`,
412
411
  margin revival and trail/stop behaviour — everything TradingView parity depends
413
412
  on at run time — live in the engine's source-adapter runtime
414
- ([`src/source/`](https://github.com/pineforge-4pass/pineforge-engine/tree/v1.4.0/src/source)
415
- in engine `v1.4.0`), which maps them onto the engine's Pine-agnostic kernel.
413
+ ([`src/source/`](https://github.com/pineforge-4pass/pineforge-engine/tree/v1.6.0/src/source)
414
+ in engine `v1.6.0`), which maps them onto the engine's Pine-agnostic kernel.
416
415
  See
417
416
  the engine's [architecture notes](https://github.com/pineforge-4pass/pineforge-engine#architecture-kernel-vs-parity).
418
417
 
@@ -825,6 +824,8 @@ Generated C++ compiles only against the engine it was generated for:
825
824
  | 1.2.0 (PyPI, 2026-10-05) | `v1.2.0` | The pair the `pineforge-release` image `1.2.0` ships. Its C++ defines the compiled execution capability functions that engine `v1.2.0` adds to `<pineforge/pineforge.h>`; regenerate and relink. |
826
825
  | 1.3.0 (PyPI, 2026-10-06) | `v1.3.0` | The pair the `pineforge-release` image `1.3.0` ships. Its C++ adds the confirmed-bar receipt, which engine `v1.3.0`'s live runner reads, and the order-shapes receipt; engine `v1.3.0`'s `<pineforge/pineforge.h>` is `v1.2.0`'s. Regenerate and relink. |
827
826
  | 1.4.0 (PyPI, 2026-10-08) | `v1.4.0` | Adds paired coded failures, corrected input manifests and collection lowering. C ABI 4 does not authorize a mixed pair. Regenerate and relink. |
827
+ | 1.5.0 (PyPI, 2026-10-12) | `v1.5.0` | Adds the nonfatal `note` diagnostic severity and diagnostic `user_message` templates. Regenerate and relink. |
828
+ | 1.6.0 (PyPI, 2026-10-17) | `v1.6.0` | Emitted C++ and the Python, JSON and diagnostic contract are unchanged since 1.5.0; test and comment cleanup only (#200, #201, #202). Regenerate and relink. |
828
829
  | Later `X.Y.Z` releases | `vX.Y.Z` of the same version | See below. |
829
830
 
830
831
  On the 0.x line the engine and codegen versions are independent, and the
@@ -850,8 +851,8 @@ Pine as `strategy.pine`, write `strategy.generated.cpp` with the
850
851
  [file example](#transpile-a-file-to-a-cpp) above, then from the same directory:
851
852
 
852
853
  ```bash
853
- # 1.4.0 pairs with engine v1.4.0. For 0.10.4 use v0.13.1.
854
- git clone --branch v1.4.0 https://github.com/pineforge-4pass/pineforge-engine.git
854
+ # 1.6.0 pairs with engine v1.6.0. For 0.10.4 use v0.13.1.
855
+ git clone --branch v1.6.0 https://github.com/pineforge-4pass/pineforge-engine.git
855
856
  cd pineforge-engine
856
857
  cp ../strategy.generated.cpp tutorial/macd/generated.cpp # the tutorial's strategy slot
857
858
  bash tutorial/run.sh # needs cmake, a C++17 compiler and python3
@@ -977,7 +978,7 @@ quote. The commercial-license store (coming soon) will take orders online.
977
978
 
978
979
  ## Explicit Pine execution attachment
979
980
 
980
- This section describes the 1.4.0 and engine `v1.4.0` pair. The Pine execution adapter is
981
+ This section describes the 1.6.0 and engine `v1.6.0` pair. The Pine execution adapter is
981
982
  the engine's full Pine execution runtime (`PineExecutionAdapter` and
982
983
  `PineStrategyHost` in the engine's `src/source/`): order lifecycle, bracket
983
984
  legs, fill-price and slippage rules, POOC / `calc_on_order_fills`, margin
@@ -1000,9 +1001,9 @@ Regenerate old generated C++ before using a new engine for Pine execution. C++
1000
1001
  generated before the source-layer cut
1001
1002
  ([#129](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/129)),
1002
1003
  0.10.4's included, derives from `BacktestEngine` and does not compile against
1003
- engine `v1.4.0`; old cap-only C++ does not attach the priority rule, and
1004
+ engine `v1.6.0`; old cap-only C++ does not attach the priority rule, and
1004
1005
  metadata cannot silently restore it. Rebuild all modules against the
1005
- new matching C++ layout (`engine_script_run_v19` in engine `v1.4.0`). Retaining
1006
+ new matching C++ layout (`engine_script_run_v19` in engine `v1.6.0`). Retaining
1006
1007
  that epoch does not promise equal fingerprints, state hashes or trades across
1007
1008
  releases. The extraction preserves Pine policy
1008
1009
  under explicit attachment; it does not implement the generic native
@@ -42,7 +42,7 @@ for the changes in each release from 1.0.0 on and the release-note policy.
42
42
  ## Releases and this README
43
43
 
44
44
  <!-- Release lane: before a release is tagged, add it to the Engine pairing
45
- table and update every line that names `1.4.0` or `v1.4.0` as the current
45
+ table and update every line that names `1.6.0` or `v1.6.0` as the current
46
46
  release or pair (this section's version and date, the baseline paragraph at
47
47
  the top, the engine `src/source/` link, the `@pf-trace` note, the clone
48
48
  command and its example output, "This section describes …", the timing note)
@@ -52,10 +52,10 @@ hosted-server line name no version. -->
52
52
 
53
53
  This README ships with each release as its package description on PyPI
54
54
  (`pineforge-codegen`); releases from 0.7.0 on are also on npm as
55
- `@pineforge/codegen-pyodide`. It describes 1.4.0 (2026-10-08)
56
- and what changed since 0.10.4. The release's behavior was validated before
57
- tagging on codegen `bfc4ddce` with engine `b3192bfc`, excluding engine
58
- request #356. Those validation builds reported `1.3.0`; historical measurements
55
+ `@pineforge/codegen-pyodide`. It describes 1.6.0 (2026-10-17)
56
+ and what changed since 0.10.4. The 1.4.0 release's behavior was validated
57
+ before tagging on codegen `bfc4ddce` with engine `b3192bfc`, excluding engine
58
+ request #356; those validation builds reported `1.3.0`. Historical measurements
59
59
  below retain the versions on which they were run. The
60
60
  [PyPI release history](https://pypi.org/project/pineforge-codegen/#history)
61
61
  lists every release; the
@@ -64,9 +64,8 @@ covers 1.0.0 on and links the notes of earlier releases. A source install
64
64
  reports the version in `VERSION`, which the release workflow sets when it tags
65
65
  a release.
66
66
 
67
- Text that says "since 1.5.0" describes the source tree on `main`, not a
68
- published package: 1.5.0 is the planned number of the next release, and the
69
- statements about 1.4.0 keep their historical meaning.
67
+ Text that says "since 1.5.0" describes the 1.5.0 release and later versions;
68
+ the statements about 1.4.0 keep their historical meaning.
70
69
 
71
70
  ### Upgrading from 1.3.0
72
71
 
@@ -126,8 +125,8 @@ It does **not** own execution semantics. Order lifecycle, bracket legs,
126
125
  fill-price and slippage rules, `process_orders_on_close` / `calc_on_order_fills`,
127
126
  margin revival and trail/stop behaviour — everything TradingView parity depends
128
127
  on at run time — live in the engine's source-adapter runtime
129
- ([`src/source/`](https://github.com/pineforge-4pass/pineforge-engine/tree/v1.4.0/src/source)
130
- in engine `v1.4.0`), which maps them onto the engine's Pine-agnostic kernel.
128
+ ([`src/source/`](https://github.com/pineforge-4pass/pineforge-engine/tree/v1.6.0/src/source)
129
+ in engine `v1.6.0`), which maps them onto the engine's Pine-agnostic kernel.
131
130
  See
132
131
  the engine's [architecture notes](https://github.com/pineforge-4pass/pineforge-engine#architecture-kernel-vs-parity).
133
132
 
@@ -540,6 +539,8 @@ Generated C++ compiles only against the engine it was generated for:
540
539
  | 1.2.0 (PyPI, 2026-10-05) | `v1.2.0` | The pair the `pineforge-release` image `1.2.0` ships. Its C++ defines the compiled execution capability functions that engine `v1.2.0` adds to `<pineforge/pineforge.h>`; regenerate and relink. |
541
540
  | 1.3.0 (PyPI, 2026-10-06) | `v1.3.0` | The pair the `pineforge-release` image `1.3.0` ships. Its C++ adds the confirmed-bar receipt, which engine `v1.3.0`'s live runner reads, and the order-shapes receipt; engine `v1.3.0`'s `<pineforge/pineforge.h>` is `v1.2.0`'s. Regenerate and relink. |
542
541
  | 1.4.0 (PyPI, 2026-10-08) | `v1.4.0` | Adds paired coded failures, corrected input manifests and collection lowering. C ABI 4 does not authorize a mixed pair. Regenerate and relink. |
542
+ | 1.5.0 (PyPI, 2026-10-12) | `v1.5.0` | Adds the nonfatal `note` diagnostic severity and diagnostic `user_message` templates. Regenerate and relink. |
543
+ | 1.6.0 (PyPI, 2026-10-17) | `v1.6.0` | Emitted C++ and the Python, JSON and diagnostic contract are unchanged since 1.5.0; test and comment cleanup only (#200, #201, #202). Regenerate and relink. |
543
544
  | Later `X.Y.Z` releases | `vX.Y.Z` of the same version | See below. |
544
545
 
545
546
  On the 0.x line the engine and codegen versions are independent, and the
@@ -565,8 +566,8 @@ Pine as `strategy.pine`, write `strategy.generated.cpp` with the
565
566
  [file example](#transpile-a-file-to-a-cpp) above, then from the same directory:
566
567
 
567
568
  ```bash
568
- # 1.4.0 pairs with engine v1.4.0. For 0.10.4 use v0.13.1.
569
- git clone --branch v1.4.0 https://github.com/pineforge-4pass/pineforge-engine.git
569
+ # 1.6.0 pairs with engine v1.6.0. For 0.10.4 use v0.13.1.
570
+ git clone --branch v1.6.0 https://github.com/pineforge-4pass/pineforge-engine.git
570
571
  cd pineforge-engine
571
572
  cp ../strategy.generated.cpp tutorial/macd/generated.cpp # the tutorial's strategy slot
572
573
  bash tutorial/run.sh # needs cmake, a C++17 compiler and python3
@@ -692,7 +693,7 @@ quote. The commercial-license store (coming soon) will take orders online.
692
693
 
693
694
  ## Explicit Pine execution attachment
694
695
 
695
- This section describes the 1.4.0 and engine `v1.4.0` pair. The Pine execution adapter is
696
+ This section describes the 1.6.0 and engine `v1.6.0` pair. The Pine execution adapter is
696
697
  the engine's full Pine execution runtime (`PineExecutionAdapter` and
697
698
  `PineStrategyHost` in the engine's `src/source/`): order lifecycle, bracket
698
699
  legs, fill-price and slippage rules, POOC / `calc_on_order_fills`, margin
@@ -715,9 +716,9 @@ Regenerate old generated C++ before using a new engine for Pine execution. C++
715
716
  generated before the source-layer cut
716
717
  ([#129](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/129)),
717
718
  0.10.4's included, derives from `BacktestEngine` and does not compile against
718
- engine `v1.4.0`; old cap-only C++ does not attach the priority rule, and
719
+ engine `v1.6.0`; old cap-only C++ does not attach the priority rule, and
719
720
  metadata cannot silently restore it. Rebuild all modules against the
720
- new matching C++ layout (`engine_script_run_v19` in engine `v1.4.0`). Retaining
721
+ new matching C++ layout (`engine_script_run_v19` in engine `v1.6.0`). Retaining
721
722
  that epoch does not promise equal fingerprints, state hashes or trades across
722
723
  releases. The extraction preserves Pine policy
723
724
  under explicit attachment; it does not implement the generic native
@@ -0,0 +1 @@
1
+ 1.6.0
@@ -1,17 +1,11 @@
1
1
  # Public contract for 1.0
2
2
 
3
3
  The supported Python/JSON contract began in 1.0.0; the sections below identify
4
- later additions. This revision includes the 1.4.0 pair (2026-10-08).
5
- Pre-tag validation used codegen `bfc4ddce` and engine `b3192bfc`, whose
6
- version files at that point read `1.3.0`. One section,
7
- [A report belongs to the call that returned it](#a-report-belongs-to-the-call-that-returned-it),
8
- describes a paired engine fix that is not yet released.
4
+ later additions. This revision includes the 1.6.0 pair (2026-10-17).
9
5
 
10
6
  Text marked **since 1.5.0** describes diagnostic additions that 1.4.0 and
11
7
  earlier releases do not have: the `note` severity, the `user_message` template
12
- and the eleven codes that became notes. 1.5.0 is the planned number of the
13
- release that carries them; until that tag exists, this text describes the
14
- source tree, not a published package.
8
+ and the eleven codes that became notes.
15
9
 
16
10
  ## Optional compiled execution capabilities
17
11
 
@@ -176,9 +170,8 @@ three codes: exit 4 alone does not select a billing or refund decision.
176
170
 
177
171
  ## A report belongs to the call that returned it
178
172
 
179
- Availability: **not yet released.** This is the contract of a report fix in the
180
- paired engine that is in preparation. Engine `v1.4.0` and earlier do not carry
181
- it; this section applies to the first engine release that does. The report fix
173
+ Availability: **since 1.5.0**, with engine `v1.5.0`. This is the contract of a
174
+ report fix in the paired engine. The report fix
182
175
  itself changes neither the generated C++ nor the transpiler's Python and JSON
183
176
  contract: the wrappers still run the strategy and then ask the engine for its
184
177
  report.
@@ -511,9 +511,9 @@ class CallHandlers:
511
511
  if func_name == "vwap" and not all_args:
512
512
  # The bare ``ta.vwap`` property is the VWAP of hlc3 (Pine v6
513
513
  # reference: "It uses hlc3 as its source series"); TradingView's
514
- # own read equals hlc3 on a daily bar (lab tv
515
- # notrade-session-vwap-f1d, NYSE:F 1D 2025-07-01..08-31, 42/42,
516
- # 2026-09-05), where the engine used to read the bar's close.
514
+ # own read equals hlc3 on a daily bar (a daily US-stock probe,
515
+ # tapes kept outside this repository), where the engine used to
516
+ # read the bar's close.
517
517
  default_src = Identifier(name="hlc3")
518
518
  self._visit(default_src)
519
519
  for field in ("high", "low", "close"):
@@ -2,7 +2,7 @@
2
2
  timeframe.
3
3
 
4
4
  TradingView flags a bar by its own open time: on an extended-hours
5
- NASDAQ:AAPL 60 chart the 09:00 bar, which holds the 09:30 open, is
5
+ US-listed stock's 60-minute chart the 09:00 bar, which holds the 09:30 open, is
6
6
  pre-market and the 16:00 bar post-market. It reads a session's day mask per
7
7
  session day, so an overnight session's Sunday-evening open belongs to
8
8
  Monday's, and a ``0000-2400`` day is in market throughout; a D/W/M bar holds
@@ -407,34 +407,36 @@ class TaSiteHelper:
407
407
  # TradingView's per-family clocks below a top-level lazy edge
408
408
  # ------------------------------------------------------------------
409
409
  #
410
- # Pinned 2026-09-03 with ``lab tv`` on NYSE:F 1D (range 2025-04-01 ..
411
- # 2026-05-01; cadence-7 ternary probes ``v = bar_index % 7 == 3 ? <call> :
410
+ # Pinned on a daily US-stock probe (tapes kept outside this repository;
411
+ # cadence-7 ternary probes ``v = bar_index % 7 == 3 ? <call> :
412
412
  # na`` exposing the value through the entry size, plus lazy-``and``
413
413
  # probes), each scored per call against three models:
414
414
  #
415
- # every-bar natives highest 9/9, sma 25/25, ema 23/23 -- the runtime
415
+ # every-bar natives highest, sma, ema (every trade matched) -- the runtime
416
416
  # advances the built-in on every chart bar; only the
417
417
  # value is gated (``_lazy_edge_ta_hoist_plan``).
418
- # hold-last source roc 38/38 (+39/39 entries), change 39/39, mom
419
- # 39/39 -- TradingView computes these from the CALL'S
418
+ # hold-last source roc, change, mom (every trade matched) --
419
+ # TradingView computes these from the CALL'S
420
420
  # OWN ``source[length]`` history: the source is
421
421
  # written only on bars where the call executes, the
422
422
  # last executed value is held on skipped bars, and
423
423
  # the history is na before the first execution
424
424
  # (call 1 of every value probe has no TV entry).
425
- # every-bar 0/38..0/39, ring-of-executions 0..1/39.
426
- # per-execution cum, barssince, valuewhen, cross, crossover 39/39,
427
- # rising 39/39 (strictly monotonic over its executed
428
- # samples) and math.sum 39/39 (na until three
429
- # executed samples) -- the native only ever sees the
430
- # samples of bars where the call executes, which is
431
- # exactly the reached-only inline ``compute`` lowering
432
- # (every-bar 0..31/39).
425
+ # the every-bar clock matched almost no trade and the
426
+ # ring-of-executions clock at most one.
427
+ # per-execution cum, barssince, valuewhen, cross, crossover,
428
+ # rising (strictly monotonic over its executed
429
+ # samples) and math.sum (na until three
430
+ # executed samples), every trade matched -- the native
431
+ # only ever sees the samples of bars where the call
432
+ # executes, which is exactly the reached-only inline
433
+ # ``compute`` lowering (the every-bar clock matched
434
+ # fewer than all of them).
433
435
  #
434
436
  # The hoist is an ALLOW-LIST and requires a direct ``[k]`` read. A broad
435
437
  # every-bar hoist of every stateful family measured on Cloud Run against
436
- # the full population (2026-09-04, like-for-like vs the same lab bundle)
437
- # fixed the pinned shapes but cost 170 tiers / 30 hard-lane regressions,
438
+ # the full population (like-for-like vs the same lab bundle)
439
+ # fixed the pinned shapes but cost many tiers and hard-lane regressions,
438
440
  # and hoisting allow-listed families WITHOUT a history read still broke
439
441
  # four ETH hard-lane probes that main matched at 100%: ``adxVal > 30 and
440
442
  # adxVal > ta.sma(adxVal, 7)`` (louislapis9), ``volume < ta.sma(volume,
@@ -444,12 +446,12 @@ class TaSiteHelper:
444
446
  # ``ta.highest(high, n) / entry > 1.05`` under ``and`` (miemomo3). Every
445
447
  # every-bar tape (highest/sma/ema ``[1]`` under ``and``, the ternary
446
448
  # ``ta.highest(high, 5)[1]``, robmagnaye) reads ``[k]`` on the call, and
447
- # the bare twins of those tapes (2026-09-04, same cadence-7 probes) are
448
- # per-execution: ``close > ta.sma(close, 5)`` ring 39/39 (every-bar 23),
449
- # ``close > ta.ema(close, 5)`` ring 39/39 (26), ``? ta.sma(close, 5) : na``
450
- # ring 39/39 (2, na until five executed samples), ``? ta.highest(high, 5)
451
- # : na`` ring 38/39 (11; TV is na with one executed sample, then the
452
- # partial maximum). So: TradingView keeps a lazily executed call on the
449
+ # the bare twins of those tapes (same cadence-7 probes) are
450
+ # per-execution: ``close > ta.sma(close, 5)`` ring matched every trade
451
+ # (every-bar did not), likewise ``close > ta.ema(close, 5)``,
452
+ # ``? ta.sma(close, 5) : na`` (na until five executed samples) and
453
+ # ``? ta.highest(high, 5) : na`` (ring matched all but one trade; TV is na
454
+ # with one executed sample, then the partial maximum). So: TradingView keeps a lazily executed call on the
453
455
  # reached-only clock unless the call's own history is referenced (``[k]``),
454
456
  # in which case it materialises a continuous series and the call is
455
457
  # evaluated on every bar. Only ``LAZY_EVERY_BAR_TA`` families
@@ -670,12 +672,13 @@ class TaSiteHelper:
670
672
  per-execution inline compute (cum/barssince/valuewhen/cross*/rising/...)
671
673
  must never precalc.
672
674
 
673
- Re-pinned 2026-09-03: the old opt-out for a chart ``ta.sma`` under an
675
+ Re-pinned: the old opt-out for a chart ``ta.sma`` under an
674
676
  ``and`` RHS (pf-probe-oliver-dual-vol-sma, "eager precalc is
675
677
  TV-incorrect") and the matching recursive ``ta.ema`` rule encoded a
676
- per-call clock that ``lab tv`` refuted for top-level shapes (NYSE:F 1D,
677
- ``... and close > ta.sma(close,5)[1]``: every-bar 25/25 vs per-call 28;
678
- ``ta.ema``: 23/23 vs 27). The analyzer never marks a site inside an
678
+ per-call clock that TradingView refuted for top-level shapes (a daily
679
+ US-stock probe, ``... and close > ta.sma(close,5)[1]``: the every-bar
680
+ clock matched every trade and the per-call clock did not; ``ta.ema``
681
+ likewise). The analyzer never marks a site inside an
679
682
  ``if``/loop/function scope static, so after hoisting the opt-outs
680
683
  only reach a static lazy-edge ``ta.sma``/``ta.ema`` that is not a
681
684
  top-level statement operand -- in practice a UDT field default
@@ -717,21 +720,21 @@ class TaSiteHelper:
717
720
  # Every-bar hoisting of stateful ``ta.*`` sites below top-level lazy edges
718
721
  # ------------------------------------------------------------------
719
722
  #
720
- # TradingView rule, pinned 2026-09-03 with ``lab tv`` on NYSE:F 1D (tapes
721
- # out-pin-ring-lazyand / lazyand-sma / lazyand-ema / ring-ternary): a
723
+ # TradingView rule, pinned on a daily US-stock probe (tapes kept outside
724
+ # this repository; out-pin-ring-lazyand / lazyand-sma / lazyand-ema / ring-ternary): a
722
725
  # stateful ``ta.*`` call inside ANY expression operand of a top-level
723
726
  # statement -- the RHS of a Pine-v6 lazy ``and``/``or``, either branch of a
724
727
  # ternary, nested comparisons -- is evaluated on EVERY bar. Short-circuiting
725
728
  # and branch selection gate only the *value*, never the built-in's state,
726
729
  # and ``[1]`` on such a call is the previous BAR's value:
727
730
  #
728
- # c = bar_index % 7 == 3 and close > ta.highest(high,5)[1] 9/9 entries
729
- # c = bar_index % 7 == 3 and close > ta.sma(close,5)[1] 25/25
730
- # c = bar_index % 7 == 3 and close > ta.ema(close,5)[1] 23/23
731
- # v = bar_index % 7 == 3 ? ta.highest(high,5)[1] : na 38/39
731
+ # c = bar_index % 7 == 3 and close > ta.highest(high,5)[1]
732
+ # c = bar_index % 7 == 3 and close > ta.sma(close,5)[1]
733
+ # c = bar_index % 7 == 3 and close > ta.ema(close,5)[1]
734
+ # v = bar_index % 7 == 3 ? ta.highest(high,5)[1] : na
732
735
  #
733
- # (the per-call / "previous evaluation" model predicts 8/9, 28, 27 and
734
- # 2/39). Production instance: robmagnaye14 ``bullMSS = setupAlive and
736
+ # (the per-call / "previous evaluation" model mispredicts these).
737
+ # Production instance: robmagnaye14 ``bullMSS = setupAlive and
735
738
  # dir == 1 and close > ta.highest(high, 10)[1]``.
736
739
  #
737
740
  # A stateful call INSIDE an ``if``/local-block/function body that does not
@@ -563,8 +563,8 @@ class TypeInferer:
563
563
  milliseconds) is 7 776 000 000 on TradingView. Emitted as C++ ``int``
564
564
  literal arithmetic the same product overflows (wraps to -813 934 592),
565
565
  so a ``(time - t0) > threeMonths`` expiry fires on every bar (round 8
566
- family U: latibonit15 execution-signals-confluence, six lanes; lab tv
567
- u-lati-levels-nq15 vs the engine, 2026-09-05). ``400 * MS`` over
566
+ family U: latibonit15 execution-signals-confluence, six lanes; a recorded
567
+ probe tape vs the engine). ``400 * MS`` over
568
568
  ``const int MS = 7200000`` is 2 880 000 000 too (lab tv
569
569
  pf-cgs-int64-const, 2026-09-28): the constant is emitted as its
570
570
  literal, so the product was the same C++ ``int`` overflow. Folding
@@ -865,8 +865,8 @@ class ExprVisitor:
865
865
  # Same implicit tail as TA_IMPLICIT_APPEND["vwap"]:
866
866
  # the symbol clock keys the Daily anchor reset.
867
867
  # The bare property is the VWAP of hlc3 (Pine
868
- # v6 reference; lab tv notrade-session-vwap-f1d,
869
- # 2026-09-05: TradingView's read equals hlc3 on
868
+ # v6 reference; a recorded daily US-stock probe:
869
+ # TradingView's read equals hlc3 on
870
870
  # a daily bar), never of the close.
871
871
  _hlc3 = "((current_bar_.high + current_bar_.low + current_bar_.close) / 3.0)"
872
872
  return (
@@ -1 +0,0 @@
1
- 1.5.0-rc.1