Skip to content

Releases

v0.10.0

Choose a tag to compare

@github-actions github-actions released this 09 Aug 10:10
e4151b9

Risk-normalized and return-decomposition analytics across pinerun and
pinetop, backed by the @heyphat/piner 0.12.0 engine.

Added

  • R-multiple expectancy — trade quality normalized by planned risk. The
    backtest and portfolio tearsheets (CLI and pinetop) gain an
    R-multiple expectancy row with n/N coverage, showing the mean net trade
    P&L per unit of immutable initial risk — the risk frozen at the first
    protective stop covering each entry, never derived from hindsight values
    like MAE or max drawdown. Trade ledgers (--trades, CSV, JSON) carry
    per-row initialRisk/rMultiple (null when no valid protective stop
    applied). Scans can rank with strategy.rMultipleExpectancy (runs without
    stop coverage rank as NaN and are dropped). Requires a piner engine that
    emits ClosedTrade.initialRisk (≥ 0.12.0); older engines report na with
    0/N coverage rather than a guess.
  • Annualized return decomposition — the tearsheets gain
    arithmetic return, geometric return, and volatility drag rows, and
    both compare surfaces (CLI compare, pinetop) show them side by side. The
    two means are computed by the engine over the same per-bar return sample as
    Sharpe and both are linearly annualized, so the drag is their exact AM-GM
    gap; a return below −100% (equity crossing zero) reports na for geometric
    and drag. All three are rankable in scans/sweeps
    (strategy.arithmeticReturnPercent, strategy.geometricReturnPercent,
    strategy.volatilityDragPercent).

Changed

  • @heyphat/piner 0.11.1 → 0.12.0 — the engine release carrying
    ClosedTrade.initialRisk/rMultiple and the annualized return
    decomposition that the analytics above surface.

v0.9.4

Choose a tag to compare

@github-actions github-actions released this 05 Aug 13:27
bd9f238

Added

  • pinetop BACKTEST tearsheet: drawdown, distribution, and trade-quality
    analysis.
    The TEARSHEET pane now reads as scalar metrics first, then
    full-width diagnostics. RETURNS and RISK form the left metric track and
    TRADES the right; below them, each diagnostic owns the complete pane width in
    a fixed order:
    • TOP DRAWDOWNS — the CLI's peak → trough → recovery episode table,
      now rendered in the TUI whenever the width and height allow.
    • OUTCOMES & STREAKS — the chronological closed-trade W/L/E strip
      (newest kept visible, the omitted older count stated) above a
      shared-scale streak histogram: loss runs extend left, win runs right,
      streak length down the axis, with long tails aggregated into one N+ row.
    • TRADE P/L DISTRIBUTION — the closed-trade profit histogram, colored
      green/red per bucket, sized to the available width.
    • RETURN BY HOLD — closed trades grouped into holding-duration
      quantile buckets (longest at top, shortest at bottom), each row showing
      median return, a magnitude bar, win rate, and sample count. Buckets never
      split an equal duration, and the longest bucket is open-ended so a single
      outlier trade cannot distort the scale.
    • MFE / MAE DENSITY — a density heatmap of each trade's maximum
      favorable/adverse excursion, clipped at the 95th percentile per axis and
      colored by each cell's majority realized outcome. Every MFE row carries a
      numeric label, the MAE baseline carries 0 / midpoint / p95 values, and a
      two-line legend names the axis directions, the percent-of-entry-notional
      unit, the p95 clipping, the ░▒▓█ log-density ramp, and the exact color
      rule (green wins > losses, red losses > wins, plain a tie).
    • ROLLING SHARPE — an annualized risk-adjusted equity-return chart that
      shares the third CHARTS slot with DRAWDOWN; focus CHARTS and use j/k to
      switch views. The window targets one empirical year of returns using the
      report's annualization factor, capped at one fifth of the longest
      contiguous history so the chart keeps enough rolling points; without a
      usable factor it falls back to a compact 14–30 bars. Deriving it from the
      timeframe is what keeps intraday runs meaningful — a fixed 30-bar window on
      5-minute data annualizes 150 minutes of returns and swings the axis by
      hundreds of Sharpe units.
      All six are read from the existing pinerun backtest --json payload; no
      output-contract change. They degrade by omission (never by clipping a date,
      duration, or axis) on narrower or shorter terminals, and a pane too short
      for both metric tracks falls back to the flattened rail paged with j/k
      so no metric becomes unreachable.
  • pinerun gains reusable trade-diagnostic and rolling-risk renderers. New pure,
    width/height-bounded durationReturnAscii, maeMfeAscii,
    tradeOutcomeSequenceAscii, and rollingSharpeAscii builders are exported
    alongside the existing topDrawdownsAscii and profitHistogramAscii,
    together with TradeDiagnosticOptions, TradeOutcomeSequenceOptions,
    RollingSharpeChartOptions, and the adaptive window helper
    (adaptiveRollingSharpeWindow, which now accepts the annualization factor).
    They back the new pinetop panels above and are usable directly from
    @heyphat/pinerun by anything building on the library.

v0.9.3

Choose a tag to compare

@github-actions github-actions released this 04 Aug 09:12
96c2c11

pinetop only — no pinerun, pinery, or pinelive behaviour changes, and no
--json contract moves.

Added

  • The shell column's width is adjustable. In ctrl-t mode, > and < grow
    and shrink the pane four columns at a time and = returns it to the
    responsive default. The choice lasts for the pinetop session, and growth is
    clamped so the source buffer never drops below the 45 columns it would have
    had when the pane first fit.

  • EDITOR's FILES pane now includes a project tree, Markdown, and Git state.
    Lowercase .pine and .md files are grouped into expandable folder rows;
    j/k moves through visible rows, ↵ toggles folders or opens files, and
    ←/→ navigates parents and children. Markdown is rendered as plain text and
    remains excluded from runnable strategy and input() discovery. In a Git
    worktree, FILES shows a changed count plus per-path M / A / D / R / ?
    / U badges; a collapsed folder retains a dot and hidden-change count, while
    the existing final + continues to mean an unwritten in-memory buffer. Git
    detection is asynchronous, bounded, and disappears cleanly outside
    repositories; full hunks remain available in the adjacent shell via
    git diff.

  • FILES and every command-page STRATEGIES picker are searchable in place. An
    always-visible row accepts /, live case-insensitive file-name or relative-path
    filtering, ctrl-u to clear, ↵ to keep the filter, and esc to remove it.
    Matching FILES ancestors open temporarily without changing collapsed-folder
    state, while the Pine-only STRATEGIES query follows the user across all six
    command pages. STRATEGIES is one row taller so the new field does not reduce
    the useful script list.

Removed

  • The unused Ask drawer and global a binding are gone. The packaged CLI
    never configured an Ask provider, so the drawer could only open a dead prompt.
    Interactive assistants now run in the editor's shell pane instead; shared
    pending config edits and ctrl-x rollback remain available.

Fixed

  • The shell pane can no longer trap focus inside a full-screen CLI. Claude,
    Codex, Kiro, vim and similar programs keep their own esc and plain tab,
    while ctrl-t then tab now moves to the next Pinetop pane and ctrl-t then
    shift-tab moves to the previous one. The border, hint strip and help now show
    the complete sequence instead of implying that ctrl-t or plain tab leaves.

  • Scrolling a full-screen program in the shell pane now scrolls the program.
    The alternate screen keeps no terminal history, so SCROLL mode's keys used to
    do nothing under claude, vim or htop. When the child negotiated SGR
    mouse tracking, k/j/u/d in ctrl-t mode are now delivered as the
    wheel gestures it asked for, and the program moves through the history it
    owns — the border reads APP SCROLL and the hint strip swaps to app line /
    app page. A full-screen child without mouse tracking shows CONTROL
    instead: the width keys and the exits still work, and everything else resumes
    the child.

  • A program in the shell pane no longer shares pinetop's controlling
    terminal.
    The child is now spawned into its own session, so a nested
    ctrl-c can no longer trip job control on the outer terminal and stop both
    the shell and the program it was running.

v0.9.2

Choose a tag to compare

@github-actions github-actions released this 03 Aug 23:58
556c9eb

[0.9.2] - 2026-08-04

pinetop only — no pinerun, pinery, or pinelive behaviour changes, and no
--json contract moves.

Added

  • A shell in the editor page. t (or ctrl-t, which also reaches it from
    inside the vim buffer) opens your $SHELL as a third column beside the source:
    sidebar, buffer, terminal. It is a real terminal — git diff, a pinerun
    invocation typed by hand, vim, htop and claude all run in it with the
    script still on screen. Every keystroke goes to the child, ctrl-c included;
    esc leaves at a shell prompt, and ctrl-t then tab always leaves whatever
    the child is doing. ctrl-d or exit closes the column. It needs 108 columns
    of width and is dropped below that rather than crushing the buffer.

    No native module is involved, so the single-binary install is unchanged: the pty
    comes from the libc the OS already ships (reached through bun:ffi) and the VT
    parsing is @xterm/headless, which is pure JavaScript and bundles into the
    compiled binary.

  • Scrollback in the shell pane. ctrl-t enters a sticky SCROLL mode —
    k/j by line, u/d by page, g/G for top and back to live — over 1000
    lines of history. The border reads SCROLL ↑ 47 for as long as the mode lasts
    and the hint strip swaps to its keys. esc or ctrl-t resumes the child; any
    other key resumes it too and still reaches it, so picking up typing costs
    nothing. The alternate screen keeps no history, so the keys do nothing there,
    as in any terminal.

  • t on the hint strip, next to e, r and a, on every page.

Changed

  • The editor buffer now follows the file on disk. Change the open .pine
    from the shell — sed -i, git checkout, a formatter — and the pane reloads
    it, keeping the cursor where it was. An unwritten buffer is never
    overwritten: it reports changed on disk — :e! to reload, :w to overwrite and
    leaves your edits alone. A file deleted underneath you keeps its buffer, marked
    new, so :w puts it back.

  • The EDITOR buffer hands ctrl-t back to the frame, alongside tab,
    shift-tab, space and ctrl-p, so the shell column is reachable from inside
    the buffer where a bare t is vim's till motion.

  • TERMINAL's pane accelerator is [T], shifted because t is now a global
    binding — the same rule that makes RANKED [R].

  • Removed packages/pinetop/design.md. The document had fallen behind the
    implementation, and one of its decisions (that an in-pane terminal was
    impossible without a native module) was no longer true.

Fixed

  • Quitting no longer waits on the shell pane. q now exits the way a signal
    already did, instead of returning and waiting for the event loop to drain. The
    emulator schedules timers of its own and a program run in the pane can leave a
    child behind; waiting for those made quitting hang for as long as they lived,
    after the frame had already gone.

  • Closing a shell pane no longer takes the program inside it down by luck.
    Teardown now enumerates the child's descendants and signals each, escalating to
    SIGKILL. Signalling a process group was not enough: that needs the child to
    be a group leader, and without setsid it is not, so kill(-pid) named no group
    and claude or vim kept running behind a closed pane.

v0.9.1

Choose a tag to compare

@github-actions github-actions released this 03 Aug 13:35
9669078

pinetop only — no change to pinerun, pinery, or any research output contract.
Two keybindings are removed: s and w no longer switch page, and the
letters they held now belong to the panes. pinelive's armed-production work is
not in this release; it stays under Unreleased above, even though the other three
packages bump in lockstep with the tag.

Added

  • Every pane has a key of its own, printed on its border. tab still walks
    the focus ring, but reaching the sixth pane no longer costs five presses:
    STRATEGIES is [s], HISTORY [h], CHARTS [ch]. The keys are derived per page
    from the pane's name — the first letter, one letter more when two panes on the
    page want the same one ([co] CONFIG vs [ch] CHARTS, [le] LEDGER vs [lo]
    ENGINE LOG, [st] [sl] [su] on PORTFOLIO), and shifted when the app already
    claims that letter, so r still opens the run dialog (RANKED is [R]) and e
    still hands off to $EDITOR (the buffer pane is [E]). A half-typed key lights
    up the panes it could still reach and esc abandons it; the focused pane hides
    its badge so the columns go to its legend; ? lists the set for the page you are
    on. Inside the EDITOR buffer the badges disappear, because there the buffer owns
    the keyboard. Nothing is hand-assigned, so a new pane gets a working key and
    cannot collide with an existing one (§4.2.h).

Changed

  • No letter switches page any more — a page is its ordinal (§4.2.i). s (open
    SWEEP with its run dialog) and w (open WALKFORWARD) are removed. They were
    the only letters that changed page, which left the keymap answering the same
    question two ways and BACKTEST — the page you come back to most — with no letter
    at all. 3 then r is what s was, in the two keystrokes every other command
    page already costs, and the freed letters go to the pane keys above. w also
    carried the sweep grid into walkforward, which is an edit rather than a
    navigation, so it moved to the command palette as carry the sweep grid into
    walkforward
    (: or ctrl-p); SWEEP's config pane now points at the palette
    instead of advertising WF w. ? is generated from the keymap table, so the
    overlay dropped both rows with them.

Fixed

  • BACKTEST's MONTHLY TRADES no longer reads as a pane you cannot reach. On a
    terminal wide enough for both 99-column grids the strip draws two boxes for one
    pane, and only the left one carried the focus marker — so the trades grid looked
    like a pane no key could land on. Both halves now show the same pane key and both
    mark focus. (Narrower than that, the strip still shows one grid with j/k
    swapping which, as its legend says.)

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 01 Aug 12:06
84305d4

Added

  • Pine alert() delivery in pinelive. A strategy's alert() calls now reach
    registered notification channels, with the same host semantics as the fractal
    web app's TradingView-style alerting: warmup/replay alerts stay data, only
    fresh authoritative bar closes dispatch (forming revisions and recovered
    replays never do), a pure sample-time frequency gate (all /
    once_per_bar / once_per_bar_close, default close) keys per message, and
    every gated alert lands in the ledger with per-channel outcomes (new v1
    alert record and schema-v3 alert event, recovery-validated). Delivery is
    fail-open and bounded — per-alert send deadline, transient-only retries with
    linear backoff, and a per-bar cap journaled as suppressed — and can never
    delay a reconcile: trading always completes first. Ships with a webhook
    channel (fractal's delivery contract: coarse non-PII failure reasons, URL and
    headers never journaled or thrown) and a telegram channel (Bot API
    sendMessage; plain-text messages truncated to the 4096-char limit; honors
    retry_after on 429 rate limits; the bot token and chat id are construction
    secrets), configured via a new strict alerts config section shared by v1
    and v2, an AlertChannel protocol for custom channels, and
    runAlertChannelConformance in @heyphat/pinelive/testing.
    See docs/pinelive-alerts.md.

  • A standalone pinelive binary. Releases now carry pinelive for the same
    five targets as pinerun/pinetop, stamped by build-bin.ts so
    pinelive --version self-reports, and self-updating via pinelive upgrade
    (the shared checksum-verified pinerun implementation). The curl | sh
    installer does not fetch it by default — opt in with
    PINESTACK_BINS="pinerun pinetop pinelive" — because the forward runner is
    the binary that can place orders: Paper remains its default broker and the
    Tiger adapters are offline-tested only, not sandbox- or production-approved.

  • Limit-order execution in pinelive. OrderRequest now requires limitPrice for limit orders, and PositionMirror accepts an explicit market/limit policy with a side-aware tick offset from each closed-bar price. Market remains the default. Deterministic client ids now frame every identity component by length to prevent sanitizer and delimiter-boundary collisions; limit type/price are included in identity and schema-v2 cycle ledgers. Deploy the new ID format only with no unresolved old-format orders.

    • PaperBroker fills only immediately marketable limits and never violates the requested price or invents a resting order.
    • TigerTradingTransport gains a backward-compatible optional submitLimit; the official Tiger SDK adapter submits native futures LMT orders. Tiger limit mode requires cancellation support plus cancelStuckOrders, polls cancellation to terminal state, and blocks a second correction while any transmitted order remains unresolved. Flattening remains market-only.
    • CLI config adds order.type, order.limitOffsetTicks, and Tiger orderPollIntervalMs, maxOrderPolls, and cancelStuckOrders controls.
  • request.security in live forward runs. The pinelive forward runner now
    resolves static dependencies and runtime inputs fixed for the life of the run,
    including cross-symbol, same-symbol other-timeframe, plain lower-timeframe, and
    request.security_lower_tf series. Call sites are deduplicated, fetched through
    the same pinery provider before warmup, and refreshed with explicit overlap and
    catch-up ranges before every closed chart tick. Self-references reuse the chart's
    exact resolved instrument.

    • Safety is fail-closed: resolution, timeout, insufficient warmup, truncated
      catch-up, history-cap, and refresh failures stop before reconciliation by
      default. Refresh failures and per-cycle health are ledgered; an explicit
      maxSecurityStaleRefreshes allows bounded tolerance.
    • Runtime dependencies that change after startup are detected after evaluation
      and stop before broker reconciliation instead of silently trading on na.
    • Provider work is bounded by feed count, concurrency, request timeout, and a
      non-truncating history ceiling. Timed-out operations retain their real slots
      until settlement; shutdown interrupts the provider and then either drains all
      such operations or reports a bounded cleanup failure. Existing timestamps are
      revision-aware and missed bars are repaired from an inclusive cursor.
    • New config/options: resolveSecurity, securityWarmupBars,
      maxSecurityBars, maxSecurityFeeds, securityConcurrency,
      securityRequestTimeoutMs, and maxSecurityStaleRefreshes.
    • Shared timeframe helpers live in @heyphat/pinery; pinerun and pinelive use
      the same finest-base planning rule for plain cross-symbol lower timeframes.
  • @heyphat/pinelive offline core — a broker-SDK-free forward runner, Broker
    protocol, position mirror, deterministic CSV replay, idempotent PaperBroker with
    PnL accounting, append-only JSONL ledger, dry-run CLI, adapter conformance tools,
    and live-vs-backtest target parity utility. Official Tiger quote/trade adapters
    have injected offline SDK-facade coverage only; credentialed venue, demo-order,
    cancellation, and fill validation remain intentionally pending.

Changed

  • pinetop page 8 renamed TRADES → LOGS. The tab shows the engine log plus
    the fill ledger for the loaded run, and the old name misread as a trading
    surface. Keyboard ordinal (8), behavior, and panes are unchanged;
    --page trades remains an accepted alias for --page logs.

Fixed

  • Pinelive safety-audit remediation. An earlier pass fixed 17 findings across exact Tiger account/order identity, unresolved-order serialization, runtime order validation, Paper quantity handling, tiny quantity grids, futures roots/expiry, replay catch-up, primary and secondary warmup coverage, shutdown drainage, cache partitioning, strict timeframe identity, finer security-history ranges, truthful capabilities, and injective client ids.

  • Pinelive execution-safety fixes. A later full-branch logic audit found and fixed one critical and two major defects plus hardening items:

    • Journal-only skipped evaluations (forming revisions, compute-only decisions) no longer consume the per-bar admission budget, so an every-update bar's authoritative close can no longer be starved by its own forming revisions and silently dropped. Refusing an authoritative final by target-limit now latches the execution breaker (new durable breaker reason target-limit) instead of passing silently. Ledger targetOrdinal semantics are unchanged; recovery additionally tracks the admitted count.
    • TargetScheduler and the compute-only journal prune finalized per-bar decision state to a bounded retention window (default 512 bars per binding; retainBars option), so multi-day forward runs no longer grow memory without bound. Durable rows are never pruned; bars with unresolved orders or unreset position uncertainty are always retained, and stale duplicates of pruned decisions are rejected fail-closed by the chart-update gate.
    • Live aggregation and duplicate-final dedupe compare volume with a relative 1e-9 tolerance (OHLC stays exact), so float-summation noise on fractional-volume venues can no longer spuriously abort a run as a data conflict.
    • Fallback decision/event identity hashing widened from 32-bit to 64-bit FNV-1a; canonical identity serialization now sorts by codepoint instead of locale; target-attainment checks use the same tolerant comparison as recovery, removing a redundant broker round trip per fractional fill; an unconfigured TargetScheduler now defaults to the shared fail-closed execution limits instead of unlimited; the instrument binding attests broker-supplied pointValue when the data provider reports none; and Paper's non-marketable-limit rejection names the limit and mark prices (calling out off-grid reference data).
    • A follow-up hardening pass extended the retention bound through degraded and restart paths: a protected bar (unresolved order or unreset position uncertainty) is now a bounded exception instead of blocking all pruning behind it, scheduler and compute-only recovery compact to the retention window immediately on restart and release the recovered ledger from memory, the compute journal fail-closes on decisions older than its retained dedupe horizon rather than ever reusing a durable identity, and a broker-only pointValue must be positive and finite before it is attested into the instrument binding.

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 01 Aug 01:50
eb1d118

No change to pinery or to any output contract.

Changed (breaking)

  • pinetop's pages are renumbered. EDITOR is page 1, so every command page
    shifts by one: BACKTEST is now 2, SWEEP 3, WALKFORWARD 4, SCAN 5,
    PORTFOLIO 6, COMPARE 7, TRADES 8. EDITOR goes first because the tabs are
    in workflow order and the source is where the workflow starts. --page editor
    is accepted alongside the existing names.

Added

  • A Pine editor on page 1. A vim-modal buffer for the .pine itself, so a
    stop that is wrong in the script no longer sends you to another window and
    back to a stale report. The sidebar lists the project's scripts and the open
    one's input() titles; the buffer has a line-number gutter, Pine syntax
    colouring from your terminal's palette, and a vim status line.
    • Modes, motions and operators: i I a A o O, h j k l w b e W B E, 0 ^ $,
      gg G, { }, f F t T, d c y > < over any motion plus dd cc yy,
      D C Y x X s p P J r, visual and visual-line, u / ctrl-r, counts
      (3dd, 42G, d3w), / ? n N, and :w :wq :q :q! :e :42 :set nu.
    • The buffer owns the keyboard while it has focus, with two ways out that
      never move: tab leaves the pane and ctrl-c quits pinetop. q inside the
      buffer explains itself instead of quitting, and elsewhere warns once before
      discarding an unwritten buffer.
    • The INPUTS outline reads the buffer rather than the file, so a renamed
      input() title shows up before you save — and that is the same list
      --input NAME is validated against.
  • e hands the script to your real $EDITOR. From any page: the frame
    suspends, $VISUAL/$EDITOR/vim opens the page's script at your cursor
    line, and the file is reloaded when it exits. Refuses when the in-frame buffer
    has unwritten changes to that same file.
  • space then a page number switches page, everywhere including inside the
    editor buffer, where a bare digit is a vim count. 1–8 still work directly
    anywhere else.
  • A STRATEGIES pane on every command page, not just BACKTEST — all six take a
    .pine as their first argument, and ↵ loads the selection into that page's
    command. COMPARE takes two, so it marks them A and B and fills the first
    free slot.
  • An INPUTS pane on SWEEP and WALKFORWARD listing every input() the loaded
    script declares, with the swept ones marked and carrying their grid. ↵ opens
    one axis for typing, prefilled; clearing it drops that axis and leaves the rest
    alone. --input is repeatable, so the config pane could only show it as a
    single space-joined field — adding a second axis meant retyping the first.
  • A HISTORY pane on every command page listing that page's runs from the
    session, newest first. ↵ puts one back on screen with the flags that produced
    it, so the config pane and the $ pinerun … line agree with the numbers and
    r repeats it. Twenty runs per command are kept.
  • A failed run gets a drawer with every error line the engine printed, the
    exit code and the elapsed time, instead of one truncated line in the status
    bar. A run that exits zero but lost symbols — scan, portfolio, sweep
    reporting and continuing past a fetch failure — gets the same drawer in warn
    colour, because the report beside it was computed over what was left.

Fixed

  • pinerun scan / sweep / walkforward could hang forever at startup
    (#12): a worker thread was
    occasionally created whose entry module never executed — no error, no exit,
    no output, ever. The pool now holds each job until its worker proves it is
    listening; a worker that misses that deadline (default 5 s, tunable via
    PINERUN_WORKER_BOOT_TIMEOUT_MS) is replaced and the job re-dispatched to a
    fresh thread, so a startup miss costs seconds instead of hanging. Repeated
    misses fail loudly with the reason instead of silently.
  • pinetop's ? overlay silently dropped bindings once the table outgrew
    its fixed-height box. It now sizes itself from the keymap and splits into two
    columns on a short terminal.
  • Keys typed before the UI was ready were replayed as commands when the
    alternate screen opened.
  • The narrow-terminal warning claimed the right rail had been dropped on
    pages that have no right rail; it now names what the page actually loses.
  • pinetop's tab bar no longer overprints the run status on terminals too
    narrow for eight titles — below about 105 columns it names only the active page.

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 31 Jul 09:08
1066aa5

Added

  • pinetop — a terminal UI over the pinerun CLI. A new workspace package
    (@heyphat/pinetop) that keeps a strategy's report resident on screen and makes
    the command's own flags the thing you edit, so the edit → rerun → reread loop
    happens in place instead of through repeated shell invocations and scrollback.
    It adds no analytics: every number comes from pinerun --json, and the braille
    charts and monthly grids are the CLI's own renderers, imported — so the screen
    and the printed command cannot disagree.

    • Seven pages in workflow order, 1–7: BACKTEST, SWEEP, WALKFORWARD, SCAN,
      PORTFOLIO, COMPARE, and TRADES (the ledger + engine log for the loaded run).
    • Flags are editable in place: tab to the config pane, ↵ to edit a row,
      . to reveal the advanced ones. r then ↵ runs. Nothing runs, and nothing
      changes the config, without a keypress.
    • Flags a choice makes mandatory surface with it — --provider csv reveals
      --data-dir and the --csv-* assertions, and a csv run without a directory
      is refused before the spawn rather than failing on its first fetch.
    • The BACKTEST rail mirrors the CLI tearsheet's three sections (RETURNS, RISK,
      TRADES) row for row, with the CLI's labels and formatters; the monthly grids
      carry its green/red grading.
    • Workflow hand-offs: w carries a sweep grid into WALKFORWARD, ↵ on a
      ranked combo, a scanned symbol, or a portfolio sleeve deep-dives it in
      BACKTEST.
    • An opt-in Ask drawer (a) answers questions grounded in the loaded report and
      returns any recommended change as a reviewable parameter diff — ↵ applies,
      ctrl-x rejects, and an applied edit raises a "not yet re-run" banner until
      you re-run. It sends derived metrics only: never OHLCV bars, never script
      source, never credentials.
    • Per-project state in .pinetop/: saved flags, so reopening resumes where you
      were, plus a session log of every invocation with its exit code and duration.
    • pinetop --check-flags diffs its flag schema against pinerun <cmd> --help
      and exits non-zero on drift.
    • pinetop --version (also -v / version, matching the CLI) reports both its
      own version + commit and the pinerun it spawns — every number on screen
      came out of that binary, so a stale one on PATH explains a stale number. The
      same pair heads the ? overlay.
    • pinetop upgrade (--check to just look) self-updates the installed binary
      in place, resolving the latest release, verifying the download's sha256
      against the release's checksums.txt, and swapping the executable
      atomically — the same implementation pinerun upgrade uses, asked to operate
      on the pinetop asset.

    See packages/pinetop/README.md.

Changed

  • Releases now ship both binaries. A release carries 10 assets (pinerun-*
    and pinetop-*, 5 targets each) under one checksums.txt, and the workflow
    executes the built linux-x64 assets to assert each self-reports the tag before
    publishing. scripts/build-bin.ts grew --product pinerun|pinetop (defaulting
    to whichever package you run it from); existing bun run build:bin invocations
    are unaffected.
  • The installer installs pinerun and pinetop. PINESTACK_BINS selects
    (default "pinerun pinetop"), alongside PINESTACK_VERSION and
    PINESTACK_INSTALL_DIR. The older PINERUN_VERSION / PINERUN_INSTALL_DIR
    names keep working.

v0.6.1

Choose a tag to compare

@github-actions github-actions released this 29 Jul 14:08
2bf4f60

Changed

  • MONTHLY TRADES break-even tallies are now bare counts like wins and losses
    (5/2/1 instead of 5/2/1E): color alone tells the segments apart — wins
    green, losses red, evens uncolored — and the header legend reads
    (win/loss/even).

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 29 Jul 13:59
5369a66

Added

  • MONTHLY TRADES tearsheet table. backtest and portfolio print a year ×
    month grid in the MONTHLY RETURNS layout tallying closed trades by exit month
    in win/loss/even order (5/3, 5/2/1E; zero tallies are omitted), with a
    YEAR total column. Wins paint green and losses red on a TTY; evens keep an
    E suffix because they carry no color. Like the other stats tables it always
    prints, independent of --no-chart.
  • Exact CSV CLI evidence for Bar Magnifier and static security. Every CSV
    leaf created by --data-dir now discovers canonical <SYMBOL>_<TF>.csv
    datasets for native or exactly aggregatable acquisition. --csv-alignment utc-24x7, strict --csv-week-anchor <YYYY-MM-DD|seconds>, and
    --csv-calendar <file.json> provide explicit alignment evidence; strict
    calendar loading rejects unknown keys, unsafe intervals, and invalid
    periods. Claims work for CSV: symbols in mixed routing without making CSV
    the fallback provider, and duplicate/conflicting scalar options fail early.
  • Authenticated CSV complete-record semantics. --csv-complete-record
    asserts that absent bars inside an explicit exact file's full record span mean
    no trades. The bars-only default is unchanged. Semantics and record spans are
    content- and identity-bound through native/aggregated acquisition, magnifier
    and static-security proofs, local/worker execution, and walk-forward prefix
    derivation. Bare fallback and empty files fail closed; requests and buckets
    crossing the record edge remain incomplete.

Changed

  • Repeating any scalar CLI option (for example --symbol a --symbol b) is now
    rejected with a duplicate scalar option error on every command instead of
    silently using the last value. The repeatable options (--input,
    --input-a/--input-b, --weights) are unchanged.
  • Exact CSV documentation now distinguishes compatibility history() row
    normalization from strict exact acquisition, documents whole-second/grid and
    OHLCV validation, strict exchange calendars, mixed routing, and the risk of
    complete-record assertions. CLI help exposes the same evidence flags on every
    analysis command. Bar Magnifier docs now describe the shipped
    contract-capable piner 0.11.1 runtime (active-traversal reporting) instead of
    the pre-0.5.0 capability-rejection state.