docs: render the active scoreboard from the facts tokens at pineforge-release 3e39d64 - #174

* docs: changelog and version scoping for 1.3.0

1.3.0 pairs only with engine v1.3.0. The changelog section takes in the
Unreleased note and covers #173, #178, #179, #177, #174 and #175: the
confirmed-bar receipt and what engine v1.3.0's live runner does with it,
the capability receipt's request entries now read from the lowering, the
order-shapes receipt, which no engine reads yet, the checked settings fix
for string dropdowns with built-in constants (now supported=false where
1.2.0 wrote an integer code or published the input as supported), the
PineForge Source License 1.2, and the pairing and migration steps. The
Python and JSON contract is unchanged; the engine's report harness is the
same file as in v1.2.0, so no report key changes.

The README, AGENTS.md / CLAUDE.md, CONTRIBUTING.md, LEGAL.md,
docs/PUBLIC_CONTRACT.md, docs/pine-cap-activation.md and npm/README.md
name 1.3.0 where they named 1.2.0 as the current release or pair, the
pairing table gets a 1.3.0 row, the "unreleased (after 1.2.0)" markers
name 1.3.0, and the license badge reads 1.2. The release scoreboard
sentence and the pf markers are left to the release lane.

Measured for 1.3.0: the engine's 325 corpus sources and the 277 gate
fixtures, each in a fresh process, transpile to 1.2.0's C++ byte for byte
once the confirmed-bar and order-shapes functions are removed (13
refusals, same messages), with transpile_full results and transpile_json
envelopes without cpp equal to 1.2.0's, each in under 0.1 s on CPython
3.14.6 on an Apple M4 Max. The tutorial run of the quick-start C++
against engine main 7a1f01c0 (Linux x86_64, GCC 13) prints 9 trades and
+738.20, and 13 trades with the old sizing declared, as 1.2.0 with engine
v1.2.0 does.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* docs: release 1.3.0's grades in the README and the changelog, from the facts tokens

The README's release sentence moves to the releases[1.3.0] tokens and its
main-scoreboard lines re-render, and the 1.3.0 changelog says which registry
baseline grades the release and why that baseline is the release's code,
all rendered from pineforge-release facts/facts.json at ff21de0 (#32).

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

---------

Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>