Pp Toretabi

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/travel/toretabi/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Toretabi — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the toretabi-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install toretabi --cli-only

2. Verify: toretabi-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/travel/toretabi/cmd/toretabi-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Discover a bounded regional ticket shortlist, read the linked official operator document, and compare source periods and conditions. Japanese evidence, independent source clocks, conflicts and unknowns stay visible.

When to Use This CLI

Use for Toretabi regional ticket discovery, bounded linked official rule inspection and a small dated comparison. Separate publisher and operator evidence, purchase dates, use dates and unresolved eligibility; cached records retain both original clocks.

Anti-triggers

• Bookings, payments, messages or account writes
• Tourist-train operating timetables or live seats
• Pass savings and route optimization
• Whole-site articles or archive edition discovery outside /ticket/

Evidence and coverage

Toretabi's public /ticket/ directory supplies editorial discovery and detail evidence. Live tickets get and tickets compare also inspect exactly one official operator URL linked by that detail. The operator read stays inside these command paths. ticket.observed_at and ticket.operator.observed_at are separate retrieval clocks; neither is a publisher revision time.

The operator object preserves its source/effective URL, HTTP status, Japanese identity evidence, periods, ticket-fare category/unit evidence, purchase channels, eligibility, supplements, exclusions and referenced PDF URLs. It accepts bounded HTML from the six supported JR document hosts listed below, binds evidence to a unique product container and its own identity, and compares explicit date endpoints and validity days against publisher facts. rule_checks distinguishes corroborated, conflict, operator_only and unknown; fare categories from two sources require an explicit category comparison. Publisher facts are never overwritten by operator facts. all_rules_verified remains false: calendar exceptions, traveler eligibility, complete train coverage, referenced documents and inventory remain unresolved.

Supported linked hosts are railway.jr-central.co.jp, www.jrhokkaido.co.jp, www.jreast.co.jp, tickets.jr-odekake.net, www.jrkyushu-kippu.jp and www.jr-eki.com. Other hosts return unsupported_operator without a request. Missing links, access errors, non-200 responses, oversized documents, unsupported formats, PDFs, mismatched identity and insufficient labelled rules have distinct statuses. A fetched HTML page or a title match alone never confirms rules. PDFs are identified but their text is not extracted; linked PDFs remain under pdf_references. Access failure does not mean a ticket is unavailable, sold out or closed.

tickets list scans native area/type pages, then applies a literal Japanese name/tag query. --max-pages defaults to 2 (maximum 5), independently of --limit default 10 (maximum 50). Coverage reports inspected routes, scanned/returned counts and continuation. complete concerns those native-filtered pages; returned rows can still be capped. A zero match has that bounded scope. Use get before comparing conditions.

tickets get preserves sale/use/validity evidence and conditions from both sources. Prices stay source-specific: publisher price.status: unknown is normal when no fare row is present; official fare tables can supply operator.price. Each operator amount retains passenger/product category, JPY currency basis and per_ticket unit. No trip total or savings is calculated. A 1,000 JPY voucher remains a benefit. Airline proof can qualify a voucher rather than pass eligibility; U25 evidence concerns age at purchase and required documents/channels.

tickets compare inspects 2..4 distinct IDs. --use-on is the intended first use date; --as-of defaults to Asia/Tokyo today for sales and edition checks. Publisher and operator date checks stay separate. closed means after an explicit published deadline, not_started before an explicit start, and within_published_window only within known bounds. Weekdays, holidays, sale lead times and yearless blackout spans remain conditional. archived_use_window means an explicit use deadline precedes as-of; fetching an old edition today does not make it current. Inventory and confirmed traveler eligibility stay unknown. Partial publisher read failures appear under fetch_failures; an operator failure stays inside its successfully fetched ticket.

Live details save normalized observations unless --no-cache is set. --data-source live reads both sources; local reads saved evidence and performs no operator refresh. Auto prefers live and can use an explicitly warned saved fallback for other publisher read failures, while publisher 403/404 and rate limits remain errors. Operator 403/404 are evidence-access failures inside the ticket. Original source clocks and their cache ages remain attached; stale is recomputed independently from each original clock using root --max-age (zero disables); an absent operator clock has freshness: unknown_clock. Missing caches return an empty result; tickets cached neither refreshes nor creates/migrates a database.

Cache capacity is 100 inspected tickets, 32 KiB per normalized payload, 50 output records and an 8 MiB read-file bound. Normal SQLite transactions preserve committed WAL rows. A delayed older save cannot overwrite a newer publisher observation. The cache is tickets.sqlite under the resolved cache directory; framework learning data and generic SQL use a separate data directory and do not query these ticket observations.

Every live domain command passes the root timeout context. The shared polite limiter allows at most 2 requests/second; each document is capped at 512 KiB, with bounded charset decoding for operator HTML. Requests are anonymous GETs; the CLI accepts stable ticket IDs, not arbitrary URLs. Tourist-train timetables/live seats, exhaustive archives, route optimization, eligibility certification, purchases and payments are unsupported.

Unique Capabilities

These capabilities aren't available in any other tool for this API.