pineforge-codegen 1.2.0__tar.gz → 1.3.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.
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/CHANGELOG.md +227 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/CONTRIBUTING.md +11 -5
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/LEGAL.md +5 -5
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/LICENSE +19 -3
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/PKG-INFO +50 -27
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/README.md +30 -23
- pineforge_codegen-1.3.0/VERSION +1 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/docs/PUBLIC_CONTRACT.md +64 -7
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/docs/pine-cap-activation.md +6 -5
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/base.py +10 -1
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/capabilities.py +143 -10
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/checked_settings.py +49 -3
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/emit_top.py +5 -5
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/helpers.py +6 -0
- pineforge_codegen-1.3.0/pineforge_codegen/codegen/order_shapes.py +356 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/security.py +54 -5
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/tables.py +12 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/visit_call.py +61 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/visit_expr.py +8 -2
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/visit_stmt.py +2 -4
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/support_checker.py +19 -10
- pineforge_codegen-1.2.0/VERSION +0 -1
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/.gitignore +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/docs/codegen-coverage-gaps.md +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/__init__.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/analyzer/__init__.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/analyzer/base.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/analyzer/call_handlers.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/analyzer/contracts.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/analyzer/diagnostics.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/analyzer/tables.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/analyzer/types.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/ast_nodes.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/block_locals.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/builtin_keywords.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/__init__.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/collection_history.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/constant_fold.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/drawing.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/helpers_syminfo.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/host_members.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/input.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/session_market.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/ta.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/tv_number_format.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/codegen/types.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/collection_history.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/diagnostic_codes.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/diagnostics_catalog.json +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/errors.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/external_requests.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/finite_ta_length.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/lexer.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/library_inline.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/library_modules.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/library_v5.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/limits.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/method_binding.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/parser.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/pine_libraries.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/pine_spelling.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/pragmas.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/request_discovery.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/security_contexts.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/session_reads.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/signatures.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/symbols.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/tokens.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pineforge_codegen/tv_input_choices.py +0 -0
- {pineforge_codegen-1.2.0 → pineforge_codegen-1.3.0}/pyproject.toml +0 -0
|
@@ -20,6 +20,233 @@ 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.3.0 — 2026-10-06
|
|
24
|
+
|
|
25
|
+
A minor release: generated strategy libraries gain two receipts beside 1.2.0's
|
|
26
|
+
capability receipt, the confirmed-bar receipt, which engine `v1.3.0`'s live
|
|
27
|
+
runner reads, and the order-shapes receipt; a string dropdown that uses a
|
|
28
|
+
built-in constant no longer breaks the checked settings; and the package is
|
|
29
|
+
licensed under the PineForge Source License 1.2. It covers the changes merged
|
|
30
|
+
to `main` since 1.2.0:
|
|
31
|
+
[#173](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/173) and
|
|
32
|
+
[#178](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/178) add
|
|
33
|
+
the receipts to the emitted C++,
|
|
34
|
+
[#179](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/179)
|
|
35
|
+
changes its checked settings metadata,
|
|
36
|
+
[#177](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/177)
|
|
37
|
+
replaces the license, string values derived from a script are validated and
|
|
38
|
+
escaped wherever they are written into generated C++ (see "Hardening"),
|
|
39
|
+
[#174](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/174)
|
|
40
|
+
renders the README's scoreboard, and
|
|
41
|
+
[#175](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/175)
|
|
42
|
+
changes the repository's CI only. Codegen `1.3.0` supports only engine
|
|
43
|
+
`v1.3.0`. Engine `v1.3.0`'s `<pineforge/pineforge.h>` is the same file as
|
|
44
|
+
`v1.2.0`'s: the pair keeps C ABI version 4, `PF_SETTINGS_API_VERSION` and
|
|
45
|
+
`PF_CAPABILITIES_API_VERSION` 1 and the script ABI epoch
|
|
46
|
+
`engine_script_run_v19`, and no engine header declares the new receipt
|
|
47
|
+
functions, which a host looks up in the library by name.
|
|
48
|
+
|
|
49
|
+
### Compatibility and migration
|
|
50
|
+
|
|
51
|
+
- Regenerate C++ with 1.3.0 and relink it against engine `v1.3.0`'s headers
|
|
52
|
+
and `libpineforge.a`. The C++ defines the two new receipts beside the
|
|
53
|
+
capability functions, only when the engine's `pineforge/pineforge.h` defines
|
|
54
|
+
both `PF_SETTINGS_API_VERSION` and `PF_CAPABILITIES_API_VERSION`, as engine
|
|
55
|
+
`v1.3.0`'s does. Engine `v1.2.0`'s header defines both too; that does not
|
|
56
|
+
make 1.3.0 with engine `v1.2.0` a supported pair. C++ generated by 1.2.0 has
|
|
57
|
+
neither receipt, and engine `v1.3.0`'s live runner keeps its original
|
|
58
|
+
receipt policy for it (see "Confirmed-bar receipt").
|
|
59
|
+
- Every generated C++ file changes: it gains the two receipts. Beyond that,
|
|
60
|
+
the C++ does not change for the engine's 325 public corpus sources and this
|
|
61
|
+
repository's 277 gate fixtures: each transpiled in a fresh process, 1.3.0's
|
|
62
|
+
C++ with the confirmed-bar and order-shapes functions removed is 1.2.0's C++
|
|
63
|
+
byte for byte, and the 13 fixtures the gate expects to be refused are
|
|
64
|
+
refused with the same message. Elsewhere, #173 changes the capability
|
|
65
|
+
receipt's request entries and `unresolved` list, and #179 the settings
|
|
66
|
+
metadata of a string input that uses a built-in constant (see below),
|
|
67
|
+
shapes none of those sources has. The trading code is unchanged.
|
|
68
|
+
- The Python and JSON contract does not change: no argument, result key or
|
|
69
|
+
envelope is added, removed or renamed. Since 1.2.0 the package's code
|
|
70
|
+
changed only in the code generator (`pineforge_codegen/codegen/`) and its
|
|
71
|
+
support checker (`pineforge_codegen/support_checker.py`):
|
|
72
|
+
`pineforge_codegen/__init__.py`, `pineforge_codegen/errors.py`,
|
|
73
|
+
`gate/glue.py` and `pineforge_codegen/diagnostics_catalog.json` (628 codes)
|
|
74
|
+
are 1.2.0's files. For the 602 sources above, each in a fresh process,
|
|
75
|
+
`transpile_full()`'s result without `cpp`, the diagnostics' codes and
|
|
76
|
+
arguments included, and the `transpile_json` envelope without `cpp` are
|
|
77
|
+
1.2.0's. The GitHub release attaches the catalog as
|
|
78
|
+
`diagnostics_catalog-v1.3.0.json`.
|
|
79
|
+
- Report keys: the engine's Docker harness (`docker/run_json.py`, which the
|
|
80
|
+
`pineforge-release` image runs) is the same file in engine `v1.3.0` as in
|
|
81
|
+
`v1.2.0`, so no report key is added, removed or renamed;
|
|
82
|
+
`metrics.equity.sharpe_tv` and `sortino_tv` (`EQUITY_REPORT_KEYS`) are
|
|
83
|
+
unchanged, and the engine's ADR-0001 keeps serialized report keys as they
|
|
84
|
+
are. A report's fingerprint still differs between 1.2.0 and 1.3.0, since it
|
|
85
|
+
records the engine and codegen versions and the generated C++'s hash, and
|
|
86
|
+
the engine's Pine adapter changes since `v1.2.0`
|
|
87
|
+
([pineforge-engine#341](https://github.com/pineforge-4pass/pineforge-engine/pull/341),
|
|
88
|
+
[#345](https://github.com/pineforge-4pass/pineforge-engine/pull/345),
|
|
89
|
+
[#347](https://github.com/pineforge-4pass/pineforge-engine/pull/347)) can
|
|
90
|
+
change a run's trades.
|
|
91
|
+
- 1.3.0 is the first release under the PineForge Source License 1.2. 1.2.0
|
|
92
|
+
shipped under the PineForge Source License 1.1, and releases up to and
|
|
93
|
+
including 1.1.0 under "PineForge Codegen — License"; copies of each release
|
|
94
|
+
keep the license it shipped with (see "License").
|
|
95
|
+
|
|
96
|
+
### Confirmed-bar receipt
|
|
97
|
+
|
|
98
|
+
From [#173](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/173):
|
|
99
|
+
|
|
100
|
+
- Built against engine `v1.3.0`, a generated strategy library also defines
|
|
101
|
+
`strategy_confirmed_bar_api_version()`, which returns 1, and
|
|
102
|
+
`strategy_confirmed_bar_receipt(s, json, capacity, required, error,
|
|
103
|
+
error_capacity)`, with the buffer protocol and statuses of
|
|
104
|
+
`strategy_capabilities_receipt`. Its canonical JSON is written into the C++
|
|
105
|
+
when it is generated, as the capability receipt's is, and has the keys
|
|
106
|
+
`version`, `requests` (the capability receipt's request fields and the
|
|
107
|
+
lowered `expression`), `orders` and `intrabar_persistence`. `orders` lists
|
|
108
|
+
the distinct classified shapes of the script's `strategy.*` order calls,
|
|
109
|
+
sorted: `entry:market`, `entry:stop`, `entry:limit`, `exit:short_bracket`
|
|
110
|
+
and `close:market` for the modeled calls and arguments, and the call's name
|
|
111
|
+
marked unproven, such as `strategy.exit (unproven exit terms)`, for any other
|
|
112
|
+
call or argument, risk rules and an order ID that is not a string literal
|
|
113
|
+
included. With `process_orders_on_close=true`, `strategy()` sizing, slippage
|
|
114
|
+
or account settings outside the tested literal profiles add
|
|
115
|
+
`strategy() (unproven POOC sizing, slippage or account settings)`.
|
|
116
|
+
- The capability receipt keeps its version and keys, but its request entries
|
|
117
|
+
now take their timeframe, Heikin-Ashi flag and feed from the request's
|
|
118
|
+
registration, as the confirmed-bar receipt's do. A timeframe held by a
|
|
119
|
+
constant global (`htf = "D"`) or passed as a literal to a helper called once
|
|
120
|
+
(`f("5")`) is that timeframe, where 1.2.0 wrote the name (`htf`) and listed
|
|
121
|
+
`request.security[N].timeframe` in `unresolved`. A Heikin-Ashi request of the
|
|
122
|
+
chart's symbol is `feed: "chart"`, where 1.2.0 wrote `auxiliary` and set
|
|
123
|
+
`requirements.auxiliary_security_feeds`. Symbol `""`, which lowers through
|
|
124
|
+
another symbol's feed, is `feed: "auxiliary"` and sets
|
|
125
|
+
`requirements.auxiliary_security_feeds`, where 1.2.0 wrote `chart`. A request
|
|
126
|
+
of `close`, `close[1]`, `ta.sma(close, 4)` or `ta.ema(close, 3)` in a script
|
|
127
|
+
that declares its own `close` adds
|
|
128
|
+
`request.security.expression (user-bound close)` to `unresolved`. An input,
|
|
129
|
+
reassigned or other run-time timeframe stays unresolved.
|
|
130
|
+
- Engine `v1.3.0`'s live runner, `pineforge-live`, reads both receipts
|
|
131
|
+
([pineforge-engine#342](https://github.com/pineforge-4pass/pineforge-engine/pull/342)),
|
|
132
|
+
checks that they agree and fails closed on a malformed field or a missing
|
|
133
|
+
proof. With the confirmed-bar receipt it admits a same-chart request in the
|
|
134
|
+
proven shapes the engine's `docs/strategy-capabilities.md` lists (such as
|
|
135
|
+
`close` requested at `5`, `60` or `D`, on confirmed one-minute bars) and a
|
|
136
|
+
standalone close-only `varip` on script clock `1`, where engine `v1.2.0`'s
|
|
137
|
+
runner refused every request and every `varip`. Two requests together, a
|
|
138
|
+
request with `varip`, and `process_orders_on_close=true` whatever the order
|
|
139
|
+
shapes stay refused. A library without the confirmed-bar receipt, such as
|
|
140
|
+
one generated by 1.2.0, keeps the original receipt's policy. A batch run
|
|
141
|
+
reads neither receipt, and its computation is unchanged.
|
|
142
|
+
|
|
143
|
+
### Order-shapes receipt
|
|
144
|
+
|
|
145
|
+
From [#178](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/178):
|
|
146
|
+
|
|
147
|
+
- A generated strategy library also defines
|
|
148
|
+
`strategy_order_shapes_api_version()`, which returns 1, and
|
|
149
|
+
`strategy_order_shapes_receipt(s, json, capacity, required, error,
|
|
150
|
+
error_capacity)`, with the same buffer protocol, whether
|
|
151
|
+
`process_orders_on_close` is on or off. Its canonical JSON describes the
|
|
152
|
+
strategy's order calls as they are lowered, for closing-time order
|
|
153
|
+
processing: the keys are `version`, `process_orders_on_close`, `calls`,
|
|
154
|
+
`entry_ids`, `host_reads`, `settings` and `unmodeled`. `calls` has one entry
|
|
155
|
+
per lowered `strategy.entry`, `strategy.order`, `strategy.exit`,
|
|
156
|
+
`strategy.close`, `strategy.close_all`, `strategy.cancel` or
|
|
157
|
+
`strategy.cancel_all` site, in source order, classing each parameter the
|
|
158
|
+
call passes: a number as `absent` (the default), `literal`, `never_na` or
|
|
159
|
+
`maybe_na`, and text, enums, directions and IDs in classes of their own, an
|
|
160
|
+
ID without its string; a site in a loop, a user function or a method is
|
|
161
|
+
marked `repeatable`. `entry_ids` counts the IDs that `strategy.entry` and
|
|
162
|
+
`strategy.order` sites set, by direction, shared and repeated; `host_reads`
|
|
163
|
+
lists the execution members the generated C++ references; `settings` holds
|
|
164
|
+
the compiled `strategy()` order settings (`pyramiding`, `default_qty_type`,
|
|
165
|
+
`initial_capital`, `slippage`, ...), not later overrides; `unmodeled` names
|
|
166
|
+
every other `strategy.*` call that is not read-only, risk rules included.
|
|
167
|
+
- The receipt describes the calls; it is not an admission decision. Engine
|
|
168
|
+
`v1.3.0` does not read it: the runner-side policy that reads it ships in a
|
|
169
|
+
separate engine change. #178 leaves the capability and confirmed-bar
|
|
170
|
+
receipts byte for byte as they were, the confirmed-bar `orders` included
|
|
171
|
+
(`tests/test_order_shapes.py` pins both), and the trading code unchanged.
|
|
172
|
+
The [public contract](docs/PUBLIC_CONTRACT.md#optional-compiled-execution-capabilities)
|
|
173
|
+
describes both new receipts.
|
|
174
|
+
|
|
175
|
+
### Checked settings
|
|
176
|
+
|
|
177
|
+
From [#179](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/179):
|
|
178
|
+
|
|
179
|
+
- A strategy whose `input.string` dropdown uses a built-in constant as its
|
|
180
|
+
default or an option no longer breaks its checked settings. 1.2.0 wrote a
|
|
181
|
+
display constant's integer code, such as `size.tiny`'s or
|
|
182
|
+
`position.top_left`'s, where an option of the settings metadata needs a
|
|
183
|
+
string, so building the metadata made a string from a null pointer and
|
|
184
|
+
`strategy_get_effective_settings` or `strategy_set_input_checked` failed or
|
|
185
|
+
crashed. A constant that the generated code reads as a string
|
|
186
|
+
(`alert.freq_*`, `order.ascending` and `descending`, `session.regular` and
|
|
187
|
+
`extended`, and the `currency.*` and `format.*` members, which publish their
|
|
188
|
+
own names) keeps its exact default and choices. A default or option with no
|
|
189
|
+
faithful string marks the input `"supported": false` in the settings
|
|
190
|
+
receipt, with `"options": []` and, when the default is such a constant,
|
|
191
|
+
`"default": ""`, where 1.2.0 published the input as supported;
|
|
192
|
+
`strategy_set_input_checked` refuses it with `PF_SETTINGS_UNSUPPORTED`. The
|
|
193
|
+
legacy `strategy_set_input`, the input getters and the strategy's execution
|
|
194
|
+
are unchanged.
|
|
195
|
+
|
|
196
|
+
### Hardening
|
|
197
|
+
|
|
198
|
+
- String values derived from a script are validated and escaped wherever
|
|
199
|
+
they are written into generated C++. The generated C++ of the 602 sources
|
|
200
|
+
measured under "Compatibility and migration" does not change.
|
|
201
|
+
|
|
202
|
+
### License
|
|
203
|
+
|
|
204
|
+
From [#177](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/177):
|
|
205
|
+
|
|
206
|
+
- 1.3.0 is the first release under the PineForge Source License 1.2.
|
|
207
|
+
Compared with 1.1 it changes two places and nothing else. In the Personal
|
|
208
|
+
Trading section, an account that a proprietary-trading firm or a
|
|
209
|
+
funded-trader program provides or allocates to the person to trade,
|
|
210
|
+
including a challenge, evaluation or simulated account, whether the capital
|
|
211
|
+
in it is real or simulated, is not the person's own account and is not
|
|
212
|
+
funded by the person's own capital. In the Commercial Use section, the
|
|
213
|
+
capital in such an account is investment capital whether it is real or
|
|
214
|
+
simulated, so trading it, or researching, developing or backtesting
|
|
215
|
+
strategies for it, is Investment Management, which `LICENSE` makes
|
|
216
|
+
Commercial Use for every individual and every organization unless it is
|
|
217
|
+
Personal Trading. 1.2.0 shipped under the PineForge Source License 1.1, and
|
|
218
|
+
releases up to and including 1.1.0 under "PineForge Codegen — License", the
|
|
219
|
+
PolyForm Noncommercial License 1.0.0 with PineForge's supplemental sections;
|
|
220
|
+
copies of those releases keep the license they shipped with. `LICENSE` is the
|
|
221
|
+
controlling text; `LEGAL.md` summarizes it and is not legal advice.
|
|
222
|
+
- Packaging: the PyPI classifier and `@pineforge/codegen-pyodide`'s
|
|
223
|
+
`package.json` license field are 1.2.0's; the `LICENSE` both packages carry
|
|
224
|
+
is version 1.2.
|
|
225
|
+
|
|
226
|
+
### Documentation
|
|
227
|
+
|
|
228
|
+
- The README's scoreboard of `main` renders from the facts tokens of
|
|
229
|
+
`pineforge-release` at 3e39d64
|
|
230
|
+
([#174](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/174)):
|
|
231
|
+
baseline `pineforge-parity-baseline-20261005-input-reanchor-781b8f00`
|
|
232
|
+
(engine 3c414528, this repository at 39545379), 7,975 excellent and 14
|
|
233
|
+
strong of 7,989 graded probes, none below strong.
|
|
234
|
+
Release 1.3.0 is graded on registry baseline <!-- pf:releases[1.3.0].scoreboard.id|code -->`pineforge-parity-baseline-20261006-engine-7a1f01c0`<!-- /pf -->,
|
|
235
|
+
which holds <!-- pf:releases[1.3.0].scoreboard.excellent|int -->7,982<!-- /pf --> excellent and <!-- pf:releases[1.3.0].scoreboard.strong|int -->7<!-- /pf --> strong of <!-- pf:releases[1.3.0].scoreboard.graded|int -->7,989<!-- /pf --> graded probes,
|
|
236
|
+
and <!-- pf:releases[1.3.0].scoreboard.belowStrong|int -->0<!-- /pf --> below strong. It measured engine <!-- pf:releases[1.3.0].scoreboard.engineCommit|short -->7a1f01c0<!-- /pf -->
|
|
237
|
+
([pineforge-engine#347](https://github.com/pineforge-4pass/pineforge-engine/pull/347)'s
|
|
238
|
+
merge), which v1.3.0 equals in behaviour, and this repository at <!-- pf:releases[1.3.0].scoreboard.codegenCommit|short -->3e50082f<!-- /pf -->
|
|
239
|
+
([#177](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/177)'s
|
|
240
|
+
merge). The pr-gates of the later code changes, #178's receipts and the
|
|
241
|
+
hardening of emitted string values, changed no graded probe, and the
|
|
242
|
+
release's other changes are documentation.
|
|
243
|
+
- `docs/PUBLIC_CONTRACT.md` describes the confirmed-bar and order-shapes
|
|
244
|
+
receipts ([#173](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/173),
|
|
245
|
+
[#178](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/178)),
|
|
246
|
+
and the README's License section, `LEGAL.md` and the npm README name the
|
|
247
|
+
PineForge Source License 1.2
|
|
248
|
+
([#177](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/177)).
|
|
249
|
+
|
|
23
250
|
## 1.2.0 — 2026-10-05
|
|
24
251
|
|
|
25
252
|
A minor release: generated strategy libraries gain the compiled execution
|
|
@@ -47,12 +47,13 @@ before treating a run as complete.
|
|
|
47
47
|
|
|
48
48
|
## Engine pairing
|
|
49
49
|
|
|
50
|
-
Codegen `main` is developed and tested against engine `main`. Codegen 1.
|
|
51
|
-
pairs with engine `v1.
|
|
50
|
+
Codegen `main` is developed and tested against engine `main`. Codegen 1.3.0
|
|
51
|
+
pairs with engine `v1.3.0`, the pair the
|
|
52
52
|
[`pineforge-release`](https://github.com/pineforge-4pass/pineforge-release)
|
|
53
|
-
image `1.
|
|
54
|
-
`1.
|
|
55
|
-
|
|
53
|
+
image `1.3.0` ships, codegen 1.2.0 with engine `v1.2.0`, the pair of the image
|
|
54
|
+
`1.2.0`, codegen 1.1.0 with engine `v1.1.0`, the pair of the image `1.1.0`,
|
|
55
|
+
codegen 1.0.1 with engine `v1.0.1`, the pair of the image `1.0.1`, and codegen
|
|
56
|
+
1.0.0 with engine `v1.0.0`, the pair of the image `1.0.0`. On the
|
|
56
57
|
0.x line the two version lineages are independent:
|
|
57
58
|
the last 0.x release, codegen 0.10.4, pairs with engine `v0.13.1`, the pair
|
|
58
59
|
the `pineforge-release` image `0.1.25` ships.
|
|
@@ -117,6 +118,11 @@ publishing is a separate release operation.
|
|
|
117
118
|
engine.
|
|
118
119
|
- Keep [CHANGELOG.md](CHANGELOG.md) current for user-visible changes. Its
|
|
119
120
|
release-note policy applies to both stable and prerelease tags.
|
|
121
|
+
- CI clears a pull request from a fork into `main` only when it changes
|
|
122
|
+
documentation or legal text alone (Markdown, `docs/`, `LICENSE`, `NOTICE`).
|
|
123
|
+
A fork's code change does not run in CI here: its `gate` check fails until a
|
|
124
|
+
maintainer pushes the branch to this repository and opens a pull request
|
|
125
|
+
from it, which runs the full gate.
|
|
120
126
|
- The README describes the latest release and becomes the PyPI page of the
|
|
121
127
|
next release: when a version is tagged, update its "Releases and this
|
|
122
128
|
README" section, its engine-pairing table and its release markers.
|
|
@@ -4,18 +4,18 @@ Summary of licensing, third-party components, and trademarks for `pineforge-code
|
|
|
4
4
|
|
|
5
5
|
## License
|
|
6
6
|
|
|
7
|
-
`pineforge-codegen` is **source-available**, **not** OSI "open source." It is distributed under the **PineForge Source License 1.
|
|
7
|
+
`pineforge-codegen` is **source-available**, **not** OSI "open source." It is distributed under the **PineForge Source License 1.2** — see [LICENSE](LICENSE), which is the controlling text.
|
|
8
8
|
|
|
9
9
|
- **Noncommercial use** — any noncommercial purpose, and use by a charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization or government institution for its teaching, research and other operations, is free.
|
|
10
|
-
- **Personal Trading** — free for a natural person to research, develop or backtest strategies and trade their **own** account with their **own** capital. Household, joint and retirement accounts and ordinary margin count as their own; a company's or fund's account does not, even a company they wholly own.
|
|
11
|
-
- **Investment management** — managing, advising on or trading investment capital, or researching strategies for it (a friend's, clients' or investors' capital, an endowment, a pension fund, a public fund, a foundation's treasury), is **Commercial Use for every individual and every organization**, noncommercial organizations included, except Personal Trading.
|
|
10
|
+
- **Personal Trading** — free for a natural person to research, develop or backtest strategies and trade their **own** account with their **own** capital. Household, joint and retirement accounts and ordinary margin count as their own; a company's or fund's account does not, even a company they wholly own. An account that a proprietary-trading firm or funded-trader program provides or allocates to them, including a challenge, evaluation or simulated account, does not count as their own either.
|
|
11
|
+
- **Investment management** — managing, advising on or trading investment capital, or researching strategies for it (a friend's, clients' or investors' capital, an endowment, a pension fund, a public fund, a foundation's treasury, or an account a proprietary-trading firm or funded-trader program provides or allocates, including challenge, evaluation and simulated accounts), is **Commercial Use for every individual and every organization**, noncommercial organizations included, except Personal Trading.
|
|
12
12
|
- **Commercial Use** — investment management and any other use that is not free, such as use by or for a company or fund, embedding the software or its output in a product or service for others, or operating a hosted/public-facing service with it, requires a **commercial license** (email **enterprise@pineforge.dev**; the commercial-license store is coming soon).
|
|
13
13
|
|
|
14
14
|
Describe this project as **"source-available"** rather than "open source." The runtime it targets, [`pineforge-engine`](https://github.com/pineforge-4pass/pineforge-engine), is separate and **Apache-2.0**.
|
|
15
15
|
|
|
16
|
-
Releases up to and including 1.1.0 were published under the license text that came with them (the PolyForm Noncommercial License 1.0.0 with a PineForge supplement); copies of those releases keep that license. The PineForge Source License
|
|
16
|
+
Releases up to and including 1.1.0 were published under the license text that came with them (the PolyForm Noncommercial License 1.0.0 with a PineForge supplement); copies of those releases keep that license. The PineForge Source License is a separate license and is not a PolyForm license.
|
|
17
17
|
|
|
18
|
-
The PineForge Source License 1.1
|
|
18
|
+
The PineForge Source License 1.1 replaced 1.0, and 1.2 replaces 1.1, for the code on `main` and in releases from 1.3.0 on. Version 1.1 clarified one point, that distributing the software or its output, changed or not, embedded in or bundled with a product or service made available to others is Commercial Use, not free distribution, unless it is for a permitted purpose. Version 1.2 makes two points explicit: an account a proprietary-trading firm or funded-trader program provides or allocates, including a challenge, evaluation or simulated account, is not a person's own account or capital, so trading it is not Personal Trading; and the capital in such an account, real or simulated, is investment capital, so trading it is investment management, which is Commercial Use. It changes nothing else. Release 1.2.0 was published under 1.1 and keeps that text; 1.3.0 is the first release published under 1.2.
|
|
19
19
|
|
|
20
20
|
## Copyright and licensor
|
|
21
21
|
|
|
@@ -1,6 +1,14 @@
|
|
|
1
|
-
PineForge Source License 1.
|
|
1
|
+
PineForge Source License 1.2
|
|
2
2
|
============================
|
|
3
3
|
|
|
4
|
+
Version 1.2, 2026-10-05. Compared with 1.1, two places change. In the
|
|
5
|
+
Personal Trading section, the last bullet now says that an account a
|
|
6
|
+
proprietary-trading firm or funded-trader program provides or allocates,
|
|
7
|
+
including a challenge, evaluation or simulated account, is not the
|
|
8
|
+
person's own account or capital. In the Commercial Use section, the
|
|
9
|
+
definition of investment capital now covers the capital in such an
|
|
10
|
+
account, real or simulated.
|
|
11
|
+
|
|
4
12
|
Copyright 2025-2026 pineforge, LLC
|
|
5
13
|
|
|
6
14
|
Required Notice: Copyright 2025-2026 pineforge, LLC (https://github.com/pineforge-4pass/pineforge-codegen-oss)
|
|
@@ -134,7 +142,12 @@ For Personal Trading:
|
|
|
134
142
|
program or anyone else outside the person's household provides or
|
|
135
143
|
allocates to the person to trade, and that the provider still owns or
|
|
136
144
|
whose losses the provider bears, is not the person's own capital, even
|
|
137
|
-
if the person shares in the profits.
|
|
145
|
+
if the person shares in the profits. An account that a
|
|
146
|
+
proprietary-trading firm or a funded-trader program provides or
|
|
147
|
+
allocates to the person to trade, including a challenge, evaluation or
|
|
148
|
+
simulated account, whether the capital in it is real or simulated, is
|
|
149
|
+
likewise not the person's own account and is not funded by the
|
|
150
|
+
person's own capital.
|
|
138
151
|
|
|
139
152
|
|
|
140
153
|
## Commercial Use
|
|
@@ -149,7 +162,10 @@ in each case whoever the capital belongs to and whether or not for a fee.
|
|
|
149
162
|
trading, including capital belonging to any other person or entity, such as a
|
|
150
163
|
friend or relative, clients or investors, an endowment, a pension or
|
|
151
164
|
retirement fund, a sovereign or other public fund, or the treasury or reserves
|
|
152
|
-
of a foundation or other organization.
|
|
165
|
+
of a foundation or other organization. The capital in an account that a
|
|
166
|
+
proprietary-trading firm or a funded-trader program provides or allocates
|
|
167
|
+
to a person or entity to trade, including a challenge, evaluation or
|
|
168
|
+
simulated account, is investment capital whether it is real or simulated.
|
|
153
169
|
|
|
154
170
|
**Commercial Use** means any use of the software that is not a permitted
|
|
155
171
|
purpose, other than distributing copies under the Distribution License
|
|
@@ -1,15 +1,23 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: pineforge-codegen
|
|
3
|
-
Version: 1.
|
|
3
|
+
Version: 1.3.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
|
|
7
7
|
Project-URL: Changelog, https://github.com/pineforge-4pass/pineforge-codegen-oss/blob/main/CHANGELOG.md
|
|
8
8
|
Project-URL: Engine, https://github.com/pineforge-4pass/pineforge-engine
|
|
9
9
|
Author-email: PineForge <luis@4pass.com.tw>
|
|
10
|
-
License: PineForge Source License 1.
|
|
10
|
+
License: PineForge Source License 1.2
|
|
11
11
|
============================
|
|
12
12
|
|
|
13
|
+
Version 1.2, 2026-10-05. Compared with 1.1, two places change. In the
|
|
14
|
+
Personal Trading section, the last bullet now says that an account a
|
|
15
|
+
proprietary-trading firm or funded-trader program provides or allocates,
|
|
16
|
+
including a challenge, evaluation or simulated account, is not the
|
|
17
|
+
person's own account or capital. In the Commercial Use section, the
|
|
18
|
+
definition of investment capital now covers the capital in such an
|
|
19
|
+
account, real or simulated.
|
|
20
|
+
|
|
13
21
|
Copyright 2025-2026 pineforge, LLC
|
|
14
22
|
|
|
15
23
|
Required Notice: Copyright 2025-2026 pineforge, LLC (https://github.com/pineforge-4pass/pineforge-codegen-oss)
|
|
@@ -143,7 +151,12 @@ License: PineForge Source License 1.1
|
|
|
143
151
|
program or anyone else outside the person's household provides or
|
|
144
152
|
allocates to the person to trade, and that the provider still owns or
|
|
145
153
|
whose losses the provider bears, is not the person's own capital, even
|
|
146
|
-
if the person shares in the profits.
|
|
154
|
+
if the person shares in the profits. An account that a
|
|
155
|
+
proprietary-trading firm or a funded-trader program provides or
|
|
156
|
+
allocates to the person to trade, including a challenge, evaluation or
|
|
157
|
+
simulated account, whether the capital in it is real or simulated, is
|
|
158
|
+
likewise not the person's own account and is not funded by the
|
|
159
|
+
person's own capital.
|
|
147
160
|
|
|
148
161
|
|
|
149
162
|
## Commercial Use
|
|
@@ -158,7 +171,10 @@ License: PineForge Source License 1.1
|
|
|
158
171
|
trading, including capital belonging to any other person or entity, such as a
|
|
159
172
|
friend or relative, clients or investors, an endowment, a pension or
|
|
160
173
|
retirement fund, a sovereign or other public fund, or the treasury or reserves
|
|
161
|
-
of a foundation or other organization.
|
|
174
|
+
of a foundation or other organization. The capital in an account that a
|
|
175
|
+
proprietary-trading firm or a funded-trader program provides or allocates
|
|
176
|
+
to a person or entity to trade, including a challenge, evaluation or
|
|
177
|
+
simulated account, is investment capital whether it is real or simulated.
|
|
162
178
|
|
|
163
179
|
**Commercial Use** means any use of the software that is not a permitted
|
|
164
180
|
purpose, other than distributing copies under the Distribution License
|
|
@@ -273,19 +289,19 @@ Description-Content-Type: text/markdown
|
|
|
273
289
|
|
|
274
290
|
[](https://pypi.org/project/pineforge-codegen/)
|
|
275
291
|
[](https://pypi.org/project/pineforge-codegen/)
|
|
276
|
-
[](https://github.com/pineforge-4pass/pineforge-codegen-oss/blob/main/LICENSE)
|
|
277
293
|
[](#license)
|
|
278
294
|
|
|
279
295
|
A pure-Python library that turns a PineScript v6 strategy into a complete C++
|
|
280
296
|
source file you can compile against the [`pineforge-engine`](https://github.com/pineforge-4pass/pineforge-engine)
|
|
281
297
|
runtime.
|
|
282
298
|
|
|
283
|
-
**Measured <!-- pf:scoreboard.date -->2026-10-
|
|
284
|
-
graded excellent and <!-- pf:scoreboard.strong|int -->
|
|
299
|
+
**Measured <!-- pf:scoreboard.date -->2026-10-06<!-- /pf -->** on main engine <!-- pf:scoreboard.engineCommit|short-code -->`7a1f01c0`<!-- /pf --> with codegen-oss <!-- pf:scoreboard.codegenCommit|short-code -->`3e50082f`<!-- /pf --> (baseline <!-- pf:scoreboard.id|code -->`pineforge-parity-baseline-20261006-engine-7a1f01c0`<!-- /pf -->, snapshot <!-- pf:scoreboard.snapshotSha256|short-code -->`e7921e24`<!-- /pf -->): <!-- pf:scoreboard.excellent|int -->7,982<!-- /pf --> of <!-- pf:scoreboard.graded|int -->7,989<!-- /pf --> TradingView probes
|
|
300
|
+
graded excellent and <!-- pf:scoreboard.strong|int -->7<!-- /pf --> strong, with <!-- pf:scoreboard.belowStrong|int -->0<!-- /pf --> below strong; <!-- pf:scoreboard.anomaliesExcluded|int -->17<!-- /pf --> more probes are held out as TradingView-side anomalies.
|
|
285
301
|
A probe is a strategy exported from TradingView with its trade list and replayed
|
|
286
302
|
trade for trade on the same bars.
|
|
287
303
|
|
|
288
|
-
Release **1.
|
|
304
|
+
Release **1.3.0 grades <!-- pf:releases[1.3.0].scoreboard.excellent|int -->7,982<!-- /pf --> excellent / <!-- pf:releases[1.3.0].scoreboard.strong|int -->7<!-- /pf --> strong until the next release**, on <!-- pf:releases[1.3.0].scoreboard.graded|int -->7,989<!-- /pf --> probes (baseline <!-- pf:releases[1.3.0].scoreboard.id|code -->`pineforge-parity-baseline-20261006-engine-7a1f01c0`<!-- /pf -->, <!-- pf:releases[1.3.0].scoreboard.date -->2026-10-06<!-- /pf -->). A main scoreboard advance does not change release results.
|
|
289
305
|
|
|
290
306
|
The quantities above render from the public [facts tokens](https://github.com/pineforge-4pass/pineforge-release/blob/main/facts/facts.json). Maintain them with `lab facts render --repo . --facts <local facts file or pinned raw URL>`; `lab facts check` with the same inputs reports drift. Grades are registry-derived; the authored-script and closed-trade inventory is explicitly sourced to a historical public README for the identical population, not to registry row or slug totals.
|
|
291
307
|
|
|
@@ -309,7 +325,7 @@ for the changes in each release from 1.0.0 on and the release-note policy.
|
|
|
309
325
|
## Releases and this README
|
|
310
326
|
|
|
311
327
|
<!-- Release lane: before a release is tagged, add it to the Engine pairing
|
|
312
|
-
table and update every line that names `1.
|
|
328
|
+
table and update every line that names `1.3.0` or `v1.3.0` as the current
|
|
313
329
|
release or pair (this section's version and date, the baseline paragraph at
|
|
314
330
|
the top, the engine `src/source/` link, the `@pf-trace` note, the clone
|
|
315
331
|
command and its example output, "This section describes …", the timing note)
|
|
@@ -319,7 +335,7 @@ hosted-server line name no version. -->
|
|
|
319
335
|
|
|
320
336
|
This README ships with each release as its package description on PyPI
|
|
321
337
|
(`pineforge-codegen`); releases from 0.7.0 on are also on npm as
|
|
322
|
-
`@pineforge/codegen-pyodide`. It describes 1.
|
|
338
|
+
`@pineforge/codegen-pyodide`. It describes 1.3.0 (2026-10-06) and what changed
|
|
323
339
|
since 0.10.4. The
|
|
324
340
|
[PyPI release history](https://pypi.org/project/pineforge-codegen/#history)
|
|
325
341
|
lists every release; the
|
|
@@ -359,8 +375,8 @@ It does **not** own execution semantics. Order lifecycle, bracket legs,
|
|
|
359
375
|
fill-price and slippage rules, `process_orders_on_close` / `calc_on_order_fills`,
|
|
360
376
|
margin revival and trail/stop behaviour — everything TradingView parity depends
|
|
361
377
|
on at run time — live in the engine's source-adapter runtime
|
|
362
|
-
([`src/source/`](https://github.com/pineforge-4pass/pineforge-engine/tree/v1.
|
|
363
|
-
in engine `v1.
|
|
378
|
+
([`src/source/`](https://github.com/pineforge-4pass/pineforge-engine/tree/v1.3.0/src/source)
|
|
379
|
+
in engine `v1.3.0`), which maps them onto the engine's Pine-agnostic kernel. See
|
|
364
380
|
the engine's [architecture notes](https://github.com/pineforge-4pass/pineforge-engine#architecture-kernel-vs-parity).
|
|
365
381
|
|
|
366
382
|
---
|
|
@@ -613,7 +629,7 @@ fields, such as `// @pf-trace gap=close - e` or
|
|
|
613
629
|
`// @pf-trace body=math.abs(close - open)`. A `ta.*` call written in the
|
|
614
630
|
pragma itself is not computed: `// @pf-trace rsi=ta.rsi(close, 14)` records
|
|
615
631
|
`na` on every bar, and its C++ carries an `/* unsupported: ta.rsi */` marker.
|
|
616
|
-
0.10.4, 1.0.0, 1.0.1, 1.1.0 and 1.
|
|
632
|
+
0.10.4, 1.0.0, 1.0.1, 1.1.0, 1.2.0 and 1.3.0 all behave this way.
|
|
617
633
|
|
|
618
634
|
### Advanced: run the pipeline stages directly
|
|
619
635
|
|
|
@@ -658,9 +674,9 @@ does not bypass them.
|
|
|
658
674
|
|
|
659
675
|
The last column was measured on 2026-09-29 with 70c2b4a (the same code as
|
|
660
676
|
1.0.0) on CPython 3.14 on an Apple M4 Max, over the engine corpus that engine
|
|
661
|
-
35db01c8 pins (as `v1.0.0`, `v1.0.1`, `v1.1.0` and `v1.
|
|
662
|
-
repository's `tests/gate-corpus`. On 2026-10-
|
|
663
|
-
M4 Max, 1.
|
|
677
|
+
35db01c8 pins (as `v1.0.0`, `v1.0.1`, `v1.1.0`, `v1.2.0` and `v1.3.0` do)
|
|
678
|
+
and this repository's `tests/gate-corpus`. On 2026-10-06, on CPython 3.14 on
|
|
679
|
+
an Apple M4 Max, 1.3.0 transpiled each of those sources in under 0.1 seconds.
|
|
664
680
|
|
|
665
681
|
Nesting counts brackets, indented blocks, prefix operators, `?:` and
|
|
666
682
|
`else if` chains, and the depth of the parsed syntax tree, in which an
|
|
@@ -711,6 +727,7 @@ Generated C++ compiles only against the engine it was generated for:
|
|
|
711
727
|
| 1.0.1 (PyPI, 2026-10-02) | `v1.0.1` | The pair the `pineforge-release` image `1.0.1` ships. Engine `v1.0.1` changes only documentation since `v1.0.0`; regenerate and relink all the same. |
|
|
712
728
|
| 1.1.0 (PyPI, 2026-10-04) | `v1.1.0` | The pair the `pineforge-release` image `1.1.0` ships. Its C++ defines the checked settings functions that engine `v1.1.0` adds to `<pineforge/pineforge.h>`; regenerate and relink. |
|
|
713
729
|
| 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. |
|
|
730
|
+
| 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. |
|
|
714
731
|
| Later `X.Y.Z` releases | `vX.Y.Z` of the same version | See below. |
|
|
715
732
|
|
|
716
733
|
On the 0.x line the engine and codegen versions are independent, and the
|
|
@@ -736,8 +753,8 @@ Pine as `strategy.pine`, write `strategy.generated.cpp` with the
|
|
|
736
753
|
[file example](#transpile-a-file-to-a-cpp) above, then from the same directory:
|
|
737
754
|
|
|
738
755
|
```bash
|
|
739
|
-
# 1.
|
|
740
|
-
git clone --branch v1.
|
|
756
|
+
# 1.3.0 pairs with engine v1.3.0. For 0.10.4 use --branch v0.13.1.
|
|
757
|
+
git clone --branch v1.3.0 https://github.com/pineforge-4pass/pineforge-engine.git
|
|
741
758
|
cd pineforge-engine
|
|
742
759
|
cp ../strategy.generated.cpp tutorial/macd/generated.cpp # the tutorial's strategy slot
|
|
743
760
|
bash tutorial/run.sh # needs cmake, a C++17 compiler and python3
|
|
@@ -746,7 +763,7 @@ bash tutorial/run.sh # needs cmake, a C++17 compiler and python3
|
|
|
746
763
|
`run.sh` configures CMake once, builds `libpineforge.a` and
|
|
747
764
|
`tutorial/macd/strategy.so`, and runs `tutorial/run.py`, which loads the `.so`,
|
|
748
765
|
feeds it the bars and reads back the closed trades. For the quick-start SMA
|
|
749
|
-
cross, 1.
|
|
766
|
+
cross, 1.3.0 with engine `v1.3.0` prints:
|
|
750
767
|
|
|
751
768
|
```
|
|
752
769
|
MACD(12,26,9) on BTCUSDT 15m — 672 bars, 2026-04-29 18:15 → 2026-05-06 18:00 UTC
|
|
@@ -764,7 +781,7 @@ order sizing: 1.0.0 gives an omitted
|
|
|
764
781
|
`initial_capital`, `default_qty_type` and `default_qty_value` TradingView's
|
|
765
782
|
Pine v6 defaults (100,000, `strategy.percent_of_equity`, 100), where 0.10.4
|
|
766
783
|
leaves the engine's own (1,000,000 and 1 contract). Declaring those in
|
|
767
|
-
`strategy()` books the same 13 trades on 1.
|
|
784
|
+
`strategy()` books the same 13 trades on 1.3.0.
|
|
768
785
|
|
|
769
786
|
Since 1.0.0, generated strategies reset persistent Pine state before each new
|
|
770
787
|
batch or stream warmup through the engine's script-run preparation hook. Input
|
|
@@ -801,7 +818,7 @@ use `python -m pytest --collect-only -q` for the current collection count.
|
|
|
801
818
|
|
|
802
819
|
## License
|
|
803
820
|
|
|
804
|
-
Source-available under the [PineForge Source License 1.
|
|
821
|
+
Source-available under the [PineForge Source License 1.2](https://github.com/pineforge-4pass/pineforge-codegen-oss/blob/main/LICENSE);
|
|
805
822
|
the `LICENSE` file is the controlling text. The licensor is pineforge, LLC.
|
|
806
823
|
|
|
807
824
|
- **Free for noncommercial use:** any noncommercial purpose, and use by a
|
|
@@ -816,12 +833,18 @@ the `LICENSE` file is the controlling text. The licensor is pineforge, LLC.
|
|
|
816
833
|
tax-advantaged accounts and a revocable trust for their benefit; their own
|
|
817
834
|
capital includes margin and other ordinary borrowing from a broker or
|
|
818
835
|
lender. A company's or fund's account is not a personal account, even if
|
|
819
|
-
the person wholly owns the company.
|
|
836
|
+
the person wholly owns the company. An account that a proprietary-trading
|
|
837
|
+
firm or funded-trader program provides or allocates to them, including a
|
|
838
|
+
challenge, evaluation or simulated account, is not their own account, and
|
|
839
|
+
its capital, real or simulated, is not their own capital, so trading it is
|
|
840
|
+
investment management, not Personal Trading.
|
|
820
841
|
- **Investment management is never free**, except Personal Trading:
|
|
821
842
|
managing, advising on or trading investment capital, or researching
|
|
822
843
|
strategies for it, whether the capital is a friend's, clients' or
|
|
823
|
-
investors', an endowment, a pension fund, a public fund
|
|
824
|
-
treasury
|
|
844
|
+
investors', an endowment, a pension fund, a public fund, a foundation's
|
|
845
|
+
treasury or an account a proprietary-trading firm or funded-trader program
|
|
846
|
+
provides or allocates (a challenge, evaluation or simulated account
|
|
847
|
+
included), is Commercial Use for every individual and every organization,
|
|
825
848
|
noncommercial organizations included.
|
|
826
849
|
- **Commercial Use needs a commercial license:** besides investment
|
|
827
850
|
management, any other use that is not free, such as use by, for or on
|
|
@@ -844,7 +867,7 @@ quote. The commercial-license store (coming soon) will take orders online.
|
|
|
844
867
|
|
|
845
868
|
## Explicit Pine execution attachment
|
|
846
869
|
|
|
847
|
-
This section describes 1.
|
|
870
|
+
This section describes 1.3.0 and engine `v1.3.0`. The Pine execution adapter is
|
|
848
871
|
the engine's full Pine execution runtime (`PineExecutionAdapter` and
|
|
849
872
|
`PineStrategyHost` in the engine's `src/source/`): order lifecycle, bracket
|
|
850
873
|
legs, fill-price and slippage rules, POOC / `calc_on_order_fills`, margin
|
|
@@ -867,9 +890,9 @@ Regenerate old generated C++ before using a new engine for Pine execution. C++
|
|
|
867
890
|
generated before the source-layer cut
|
|
868
891
|
([#129](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/129)),
|
|
869
892
|
0.10.4's included, derives from `BacktestEngine` and does not compile against
|
|
870
|
-
engine `v1.
|
|
893
|
+
engine `v1.3.0`; old cap-only C++ does not attach the priority rule, and
|
|
871
894
|
metadata cannot silently restore it. Rebuild all modules against the
|
|
872
|
-
new matching C++ layout (`engine_script_run_v19` in engine `v1.
|
|
895
|
+
new matching C++ layout (`engine_script_run_v19` in engine `v1.3.0`); old
|
|
873
896
|
fingerprint versions are not comparable. The extraction preserves Pine policy
|
|
874
897
|
under explicit attachment; it does not implement the generic native
|
|
875
898
|
child-activation scheduler or prove campaign neutrality. Compile-only corpus
|