Jev DevTools 0.5.5

Jev DevTools 0.5.5

Published from c73f328df855707fac3a624a7065d3faf59c9317.

Compatibility and upgrade

• Supported environments are unchanged. Node 22.12+, React/React DOM 18 or 19, ESM, TypeScript 5.4+, and TypeSafe SDK 0.7.x remain supported. Upgrade the server adapter and drawer together to receive the capture fixes.
• Flow type corrections. Flow expression types now reject non-scalar equality and array method selection that already fail during execution. Generic field-selection helpers must derive supported keys from Parameters<FlowExpression<T>["get"]>[0] instead of accepting every keyof T. Runtime behavior is unchanged.

Changes

Fixed

• Redacted condition operators. Branch and loop views show an unavailable rule when a custom redactor replaces its operator with non-string JSON, instead of crashing or displaying a different comparison. Execution and captured values stay unchanged. (#126)

• Malformed stream recovery. Validate trace and nested flow records before publishing updates, and reconnect without partially changing cached history. Preserve version-1 optional metadata, compatible unknown fields, redacted content, and parallel flows with more than 256 lanes sharing existing nodes. (#122)

• Render transformed captures safely. Custom redactors can replace request roots or numeric answer fields without crashing the drawer. The drawer keeps usable questions, answer fields, and context visible beside unavailable-field placeholders; display masking preserves SDK map names in partial captures. Trace.capture retains bounded redacted JSON with warnings; application execution and complete-response fixture requirements stay unchanged. (#123)

• Scalar equality types. Reject object, array, and undefined receivers for .eq() while preserving literal, branded, and generic scalar comparisons. Finite numbers and matching resolved scalar types remain runtime requirements. (#121)

• Array selection types. Limit .get() on arrays to indices and length, preserving readonly arrays, tuple inference, common union fields, and constrained generic helpers. Array bounds and missing optional fields remain runtime checks. (#121)

Documentation

• Package README and AI agent guidance. Rewrite the npm README around installation, runtime and privacy limits, and a shorter flow example. Add task-based AI agent sections to both READMEs and link the repository-only flow-porting skill from the docs agent guide, while preserving installed-version guidance and existing section links. (#125)

• README for new users. Lead with request inspection and the no-key playground, link to complete framework setup guides, and introduce optional flows with one request and one branch. Preserve existing section links, compatibility requirements, security boundaries, and attribution. (#125)

• Shared porting skill. Version port-jev-to-flow in the repository with semantic guidance, cookbook examples, and agent discovery links. The skill supports Jev-to-Flow ports and capability audits; npm contents and public APIs are unchanged. (#124)

npm package

Publication verification

• npm publication: 2026-10-27T02:38:41.048Z (UTC).
• Approved source and verified tag: c73f328df855707fac3a624a7065d3faf59c9317.
• Archive SHA-256: 76d3111160bef6e72cfe9e65d3a1a4b764ea66196f50431b5cf96afafd59feb1.
• npm integrity: sha512-944cqrDQDZUpQfgyVx3c0hQwY8f6V+vehRcgfBwoxTtu50mbaIFm8f5SPiWT5E1uAcFdNkxET06sBh9qvQ1ViQ==; registry integrity and provenance checked by the publish job.
• Publication workflow (includes fresh registry consumer checks).
• GitHub release published, non-prerelease, and Latest verified at 2026-10-27T02:39:37.810Z (UTC); npm latest also matched this version. These are observations at verification time.

Package publication is verified. Hosted docs require a separate explicit request and live verification; record their result here after deployment. See the release checklist.

Hosted docs verification

The separately authorized documentation publication succeeded at 2026-10-27T02:50:48.533448+00:00 (UTC). Live artifact verification passed at 2026-10-27T02:51:00.290Z (UTC), and browser verification passed at 2026-10-27T02:51:17.092Z (UTC).

• Package snapshot: 0.5.5; clean canonical source: c73f328df855707fac3a624a7065d3faf59c9317; build mode: publication.
• GPT Sites project: appgprj_6add5705dbec8191b56b1c9555078a2d; saved version 26: appgprj_6add5705dbec8191b56b1c9555078a2d~appgver_52ca219828348191bba73657b55522e3.
• Deployment: appgdep_6ae01182c4348191bf181c0d20139bf6; generated Sites source commit: 8886d6416ef8af7ee5f42624004ac90fea6f3322.
• Saved deployment archive: sha256:15f1751d42c1e5195a8d9b13ce8d42444217afe4985f2f94bc45863ae0609494.
• Live /version.json matches the inspected artifact exactly. The served raw changelog matches SHA-256 30eb4d719f767ca327e0b2b8cb6fc81a29d99bed473b441669d2d3d1b721832c.
• Home, quick-start, API glossary, and changelog returned HTTP 200; the #flow-jev anchor is present. Live setup and Flow API browser checks passed in light/dark themes at desktop/mobile widths, with no page errors or horizontal overflow. Screenshots were visually reviewed for the publication artifact and live setup page.
• Full local verify:all and cookbook checks passed on the canonical release commit with current verification evidence. The final publication artifact passed the 17-page docs browser suite and artifact inspection before deployment. Main CI and the publication workflow passed.

The package, intended npm dist-tag, exact remote tag, GitHub release designation, hosted docs, and recorded verification results satisfy the release completion checklist as of the verification times above.

Jev DevTools 0.5.4

Jev DevTools 0.5.4

Published from 3806722f44db8727a4bec85898101aa1c73bd6b5.

Compatibility and upgrade

• Supported environments are unchanged. Node 22.12+, React/React DOM 18 or 19, ESM, TypeScript 5.4+, and TypeSafe SDK 0.7.x remain supported. No migration is required from 0.5.3; public APIs, package exports, and the version-1 capture format are unchanged.
• Cookbooks use the existing Flow API. The playground now includes nineteen cookbooks: thirteen new ports and six existing examples. The new ports use synthetic samples and require no API key. Autoresearch remains excluded. No live inference, measured model accuracy, or provider performance is claimed.
• Verification improvements are separate from the ports. Full verification now runs the existing cookbook browser checks and validates evidence against the current source. These development tools do not change installed package behavior.

Changes

Added

• Parallel Questions cookbook. Compare five batched requests with 65 sequential single-question requests over a fixed synthetic sample, with all 13 original questions, inspectable loops and computed answer statistics. No live timing or cost savings are claimed. (#106)

• Twitch chat filter cookbook. Replay the original 29-message feed with eight concurrent sample requests, inspect exact moderation precedence, and compare normal/quiet policies without additional inference. Includes a separate threshold-boundary feed; ongoing Twitch ingestion is outside this sample. (#108)

• Entity alignment cookbook. Inspect attributed beer pairs with one Score, three companion Nouls and exact unlink/review/proposed-sameAs boundaries. Includes no-key synthetic examples and boundary cases; no database mutation or full evaluation. (#109)

• Citation checking cookbook. Inspect exact normalized quote matches against RFC 7519, a zero-request fabricated path and Choice-confidence review routing in five no-key synthetic samples. (#107)

• Confidence fallback cookbook. Explore one 75-group industry Choice, the inclusive API-confidence cutoff and a deterministic parent-division task with four synthetic no-key cases. Preserves the original SIC taxonomy; no SEC evaluation or live inference. (#110)

• Line-by-line search cookbook. Search the complete pinned document with synthetic Choice and Noul responses, inspect exact existence routing and view every line option in the playground. (#113)

• Inspect candidate re-ranking. Run a no-key cookbook with an authored retrieval fixture, independent synthetic Nouls, bounded candidate requests and a stable sorting task. Compare before/after order and tied probabilities without claiming benchmark accuracy. (#112)

• Date extraction cookbook. Add a no-key playground adaptation with seven Choice questions per role, fixed-reference calendar assembly, ISO dates, and inspectable confidence review. Synthetic fixtures cover official examples, calendar boundaries, invalid dates and the strict 0.60 gate; missing used confidence requires review. (#114)

• Pre-parsed extraction cookbook. Explore document-order regex candidates, separate email/phone/money Choice helpers, amount-dependent credit routing and deterministic normalization with fixed synthetic samples. Includes missing-value routes and exact decimal strings; no live inference or public API changes. (#111)

• Function calling cookbook. Explore a proposed tool call from a batched request, with selected-argument branches, omitted defaults, set membership and source-faithful confidence arithmetic. Synthetic samples only; no tool execution. (#115)

• LLM guardrails cookbook. Screen input or output samples with the official hazard batteries, compare strict/permissive policies on one synthetic assessment, and inspect severity upgrades and action precedence. No live inference or LLM generation. (#117)

• Choice self-consistency cookbook. Run the original eight-question rubric through 15 sequential synthetic requests, inspect exact probability gates and compare raw agreement, abstention and probability variation in an interactive heatmap. No paid inference or measured consistency claims. (#118)

• Noul self-consistency cookbook. Explore fifteen sequential fourteen-question requests, exact uncertainty-band decisions and computed statistics from authored synthetic fixtures. Preserve every answer and requested/returned model labels; no measured consistency or provider comparison is claimed. (#116)

• Explore API references in place. Follow API links within the docs side panel and use Back to return to earlier entries with their reading positions preserved, without leaving the guide. (#104)

• API reference previews. Hover or focus a supported API link for its summary, then open the full reference or read its contract and examples in a side panel. Touch controls, keyboard navigation, copy buttons, and failed-load recovery keep reference reading available without losing the current page. (#104)

Changed

• Clearer landing copy. Explain captured requests, sample flows, and application-defined decisions in plain language, and add a community-project and TypeSafe AI non-affiliation notice beneath the hero actions. Preserve the drawer and Flow API heading treatments, accent the second line of the System One primitives heading, and remove decorative card numbers. (#105)

Fixed

• Search from an API reading panel. Opening search dismisses the reference panel and keeps focus in search, so glossary results appear without an old panel covering the destination. (#104)

Documentation

• Current cookbook collection guide. Separate the thirteen new ports from the six existing examples, document routine browser verification, and replace outdated API-fit proposals with current implementation status. Preserve the original research as historical context and identify Autoresearch as excluded. (#119)

• Even API panel close control. Give the close button a square touch target with a centered X in desktop and mobile layouts. (#104)

• Current API reference links. Mute links inside the reading panel that point to its open entry and label them “current,” updating the indication when following references or going Back. (#104)

• Useful resource entry points. Rewrite Examples & cookbooks with sample run instructions, expected results, and clearer cookbook descriptions. Rewrite For coding agents around the installed setup skill, version-matched contracts, Markdown access, and verification evidence. Preserve existing section links. (#104)

• Clearer API explanations. Revise the glossary and React, server, flow, expression, and recorder references. Separate parameter rules, execution behavior, and errors; explain replay and comparison results; add missing server parameter types. Preserve examples, signatures, and section links. (#104)

• Concepts and practical guides. Rename How it fits together to Concepts and explain capture, flows, and drawer controls. Rewrite the Next.js, Build a flow, Privacy & access, and Troubleshooting guides with setup steps, expected results, and diagnostic checks. Preserve existing page and section links. (#104)

• Introduction for new users. Explain request inspection, optional flows, the React and Node connection, and capture privacy before directing readers to setup guides. Keep the fixed-answer demo and existing section links. (#104)

• Guided first runs. Rewrite Quick start around a Vite and Express setup and Flows from scratch around a no-network greeting. Add expected results and keep full method contracts and examples in the API reference, preserving existing section links. (#104)

• Readable API contracts. Fix the server options table and replace stale unreleased labels in type descriptions, hover help, and the replay example with their 0.5.0 availability. (#104)

Maintenance

• Routine cookbook browser verification and current evidence. Run the existing recipe and collection browser checks in full verification and React 18/19 CI, with matching playground/root React versions and color-independent server readiness. Preserve each run’s source identity and evidence separately, and validate current source/reviewed HEAD before handoff. (#119)

npm package

Publication verification

• npm publication: 2026-10-26T16:51:35.731Z (UTC).
• Approved source and verified tag: 3806722f44db8727a4bec85898101aa1c73bd6b5.
• Archive SHA-2...

Jev DevTools 0.5.3

Jev DevTools 0.5.3

Published from 57d5ed781b3e793ed41e6af1c53a6c98b3c4c37f.

Compatibility and upgrade

• Supported environments are unchanged. Node 22.12+, React/React DOM 18 or 19, ESM, TypeScript 5.4+, and TypeSafe SDK 0.7.x remain supported. No migration is required from 0.5.2; public APIs, package exports, and the version-1 capture format are unchanged.
• Shared encoding preserves isolation. Matching flow viewers reuse encoding work while retaining independent response buffers and session filtering. Aggregate capture budgets and finer-grained deltas remain follow-up work.

Changes

Performance

• Shared flow stream encoding. Matching viewers share the server's flow projection and encoding within each delivery turn, while retaining independent response buffers, session isolation, and reader catch-up state. The version-1 wire format and capture policy are unchanged; whole-run budgets and finer-grained deltas remain follow-up work. (#97)

Documentation

• 0.5.2 publication records. Record verified npm publication, archive integrity/provenance, fresh registry consumers, and the exact Git tag and GitHub Latest release. Update source installation and API guidance to describe the published version. Hosted docs were subsequently published as Sites version 22 from the merged record commit; see the publication receipt. (#96, receipt #99)

Maintenance

• Simpler releases. Keep one release-preparation PR and record verified package and manual docs publication results in GitHub release notes, without routine receipt PRs or a custom receipt store. Preserve artifact checks, independent verification, and explicit approvals. (#102)

• Focused contributor guidance. Shorten the always-loaded agent instructions with task-specific links, and keep boundary and regression requirements in the contributor guide. Verification, review, and publication requirements remain unchanged. (#101)

• Release publication tooling. Add reusable docs artifact inspection, staging, and live readback helpers, plus a restricted local verification path for existing receipt edits. Check committed, staged, and working changes independently, and reject dangling provenance symlinks before staging writes. Replace self-referential pending-merge receipt text with durable PR links. Full CI, explicit publishing authorization, public APIs, and package behavior remain unchanged. Related to #77. (#100)

• Flow lifecycle regression coverage. Assert exact loop body calls, retained iterations and latest completed state, and distinguish task timeouts from cancellation in recorded step errors. Runtime behavior and public APIs are unchanged. (#95)

• Nested flow browser coverage. Extend the existing sample verifier with map-item and loop-iteration navigation, request inspection, direct child clicks and selection ownership, maps inside iterations, and shared-camera retention through updates and reopening. No runtime or public API changes. (#98)

npm package

Publication verification

• npm publication: 2026-10-26T00:25:44.633Z (UTC).
• Approved source and verified tag: 57d5ed781b3e793ed41e6af1c53a6c98b3c4c37f.
• Archive SHA-256: 772b11d88b560f5580774c21e81c78bf959177625681c818b1b74fb6b5e82ad5.
• npm integrity: sha512-wRmQp8zDUvfm0x2ptcpbUIg+M88AU7lMBJLzeJb2dgS519diuF4nGA0dKtafeUv2THLhqSU11cn8KP3bNtKSdg==; registry integrity and provenance checked by the publish job.
• Publication workflow (includes fresh registry consumer checks).
• GitHub release published, non-prerelease, and Latest verified at 2026-10-26T00:26:39.667Z (UTC); npm latest also matched this version. These are observations at verification time.

Package publication is verified. Hosted docs require a separate explicit request and live verification; record their result here after deployment. See the release checklist.

Hosted documentation — 2026-10-26

• Published the hosted docs as Sites version 23, successfully deployed at 2026-10-26T00:38:09.389393Z (UTC), preserving the existing public Site and domain.
• Canonical source: 57d5ed781b3e793ed41e6af1c53a6c98b3c4c37f, package jev-devtools@0.5.3, clean publication build; main Verify CI succeeded.
• Generated Sites source commit: dac3add4079a71408e7f25f1a468797234550848.
• Saved version: appgprj_6add5705dbec8191b56b1c9555078a2d~appgver_92d695d5927881919e6b6ebe8d0ec505; deployment: appgdep_6adea0eab03c81918d23d231058c4611.
• Saved archive SHA-256: a01b37142af09b5de9048af1060354bc6b0a79b5a8775fc2010a9cb0b5f03347. All 46 inspected artifact files were preserved in the packaged archive.
• Embedded and live changelog SHA-256: 716d1500555e5a0f8ca8fbc80f9523c222894fd721638ff499a95cebde7cb318.
• Local npm run verify:all and the final publication-artifact browser suite passed. Setup/API pages were reviewed across themes and mobile captures; no live inference was used.
• Live readback at 2026-10-26T00:38:41.998Z (UTC) matched the complete /version.json and raw changelog to the inspected artifact. Home, quick start, API reference, changelog, and the checked API deep link passed. Live browser checks confirmed the 0.5.3 setup/API content; no browser console errors were captured.
• Known documentation follow-up: the createJevDevtools inputs table in the API glossary renders as Markdown text. This content defect is present in the approved source artifact and does not affect the package or publication identity checks. Correct it through a reviewed docs PR and a separately authorized docs redeployment; automated checks did not catch it.

Release completion verified at 2026-10-26T00:42:38.126930Z (UTC): npm latest remains 0.5.3, the remote tag resolves to the exact published commit, and GitHub's Latest endpoint returns published, non-prerelease v0.5.3. Package verification is recorded above; hosted docs publication and live readback are now verified and recorded. The 0.5.3 release is complete, with the documentation formatting follow-up noted above.

Docs rewrite and API panels — 2026-10-26

• Published docs.jevtools.dev as Sites version 24, successfully deployed at 2026-10-26T03:36:48.653664+00:00 (UTC) after PR #104. The existing public audience and custom domain were preserved.
• Canonical source: 2fca08c5a937c2953f5f4cf832d977b876348605, package jev-devtools@0.5.3, clean publication build; main Verify CI passed.
• Generated Sites source commit: 217c68cf81f3c33de227da09c5f35b131f324930.
• Saved version: appgprj_6add5705dbec8191b56b1c9555078a2d~appgver_fe953070fbd88191823a192cbac49c6d; deployment: appgdep_6adecac869848191be9c5484f2a4c4b2.
• Saved archive content hash: sha256:3cf47753b2dbd1067ca2caf25e27ba7c84bd4388976bcc8bd106cec8d8e82b16. All 124 inspected artifact files were staged and packaged without rebuilding.
• Embedded and live changelog SHA-256: 7a79704b3dceded4728d92c60d91d9bcbf5cbbdd772a569e3e7ea719a742759b.
• Locked dependency installation, full local npm run verify:all, and the final publication-artifact browser suite passed. Setup and API pages were visually reviewed in both themes, with mobile setup, API glossary, and panel captures reviewed. All inference checks used samples.
• Live readback at 2026-10-26T03:36:59.356Z (UTC) matched the complete version manifest and raw changelog to the inspected artifact. Home, quick start, API reference, changelog, and the API deep link passed. Live browser review confirmed quick start, API previews, the reference panel, and the corrected server-options table, with no captured browser console errors.
• This publication delivers the documentation rewrites, API preview and panel navigation improvements, current-reference labels, and the search regression fix. It resolves the Markdown table formatting follow-up recorded for version 23 above. No npm package or landing site was published.
• Editorial reference: Cursor pstack technical-writing skill and its unslop guidance.

Jev DevTools 0.5.2

Jev DevTools 0.5.2

Published from 20e7dc0d9d81285e2c6e17b75dae5c8e37f2d0e4.

Compatibility and upgrade

• Supported environments are unchanged. Node 22.12+, React/React DOM 18 or 19, ESM, TypeScript 5.4+, and TypeSafe SDK 0.7.x remain supported. Review the type, expression-limit, and capture-metadata notes below before upgrading from 0.5.1.

• Resolved template types. Map items and loop state now infer resolved values from nested reference templates. Code that treated resolved task values as FlowExpression objects must use ordinary value operations instead; runtime behavior is unchanged.

• Composed expression limits. Expressions now reject depth greater than 80 or more than 4,096 expanded nodes during construction, including repeated uses of a shared child. Split larger generated logic into task results or smaller steps. Accepted expressions retain their semantics and public types; long legacy condition descriptions now end with [condition truncated] within a 4,096-code-unit cap.

• Flow capture metadata. Optional warning arrays extend version-1 records; older captures remain readable, but absent metadata cannot establish completeness. Update both server and drawer to see the new warnings. Execution values and decisions are unchanged.

Changes

Changed

• Simpler diagram footer. Keep only the pan, zoom, and fit instructions below request diagrams at all screen widths. (#92)

• Mobile request navigation. Show a full-height, searchable request list on small screens; selecting a request opens its details with an All requests button to switch back. Retain search, status filters, and selection while navigating, and keep the desktop split view. Hide the selected-step summary beside Show details on mobile. Public APIs are unchanged. (#92)

• Flow canvas boundary. Move the step selector beside Copy fixture in the run header and darken the diagram viewport so its pan/zoom area is easier to distinguish. Float zoom, Fit, and Focus controls in the canvas’s top-right corner to free vertical space. Header and canvas controls wrap in narrow drawers; public APIs and zoom behavior are unchanged. (#92)

Fixed

• Controls in short drawers. Reserve the floating panel’s rendered height inside the flow canvas, including wrapped buttons, and let flow metadata scroll when drawer space is limited. Zoom, Fit, and Focus remain reachable in small unexpanded drawers and after reopening; public APIs are unchanged. (#92)

• Consistent step selection. Stop automatically focusing the first selected step, including flows with no request steps. Flows start with the normal overview fit, and clicking steps preserves pan and zoom; the step picker and explicit Focus/Fit controls keep their existing behavior. Public APIs are unchanged. (#92)

• Select arrow spacing. Inset dropdown chevrons consistently across drawer selects and reserve space between their labels and arrows. Keep native menus and keyboard interaction, with the system arrow restored in forced-colors mode. Public APIs are unchanged. (#92)

• Resolved map and loop types. Map item builders and loop gates, iteration state, body returns and final results now agree with runtime template resolution, including nested objects and arrays, while preserving generic whole-reference/scalar types and branded scalar values. (#85)

• Bound composed expressions. Account for complete subtree depth and expanded size before recursive validation, projection, and evaluation; cap legacy descriptions independently of the structured rule projection. Fixes #43. (#86)

• Flow capture warnings. Retain and display outcome and condition-rule truncation, redaction, and unavailable-capture warnings, including rule projection limits, nested item runs, and non-JSON merge values. Warnings are separate metadata; user strings are never treated as capture signals. Fixes #45. (#88)

Documentation

• 0.5.1 publication records. Record verified npm publication, archive integrity/provenance, fresh registry consumers, and the exact Git tag and GitHub Latest release. Update source documentation to describe the published fixes and preserve their compatibility notes. Hosted docs were subsequently published as Sites version 21 from the merged record commit; see the publication receipt. (#87, receipt #89)

Maintenance

• Reproducible contributor verification. Add a pinned development runtime and formatter, a complete local verification command with source/archive provenance, and CI-connected sample flow browser checks. Document capture owners so upstream projection and snapshot losses remain visible during maintenance. Package runtime requirements and public APIs are unchanged. (#91)

• Boundary and contract verification. Require agents to identify affected guarantees, reproduce bugs on current main, and verify composed expressions, resolved template types, capture metadata, and meaningful regressions at their owning boundaries. Keep required repository checks and public package behavior unchanged. (#84)

• Faster docs verification. Serve the built preview without repeating documentation generation and reuse the CI runner's browser system libraries. Existing build, development, and browser checks remain enabled; package APIs are unchanged. (#90)

• Local expression benchmarks. Add a reproducible comparison of normal flow construction and execution, with isolated installs, alternating process order, local sample SDK responses, and recorder-on/off cases. (#86)

npm package

Jev DevTools 0.5.1

Jev DevTools 0.5.1

Published from c88aea5d615a65bcda1d820b5abc63bb6fbe05e6.

Compatibility and upgrade

• Supported environments are unchanged. Node 22.12+, React/React DOM 18 or 19, ESM, and TypeSafe SDK 0.7.x remain supported. The documented TypeScript 5.4+ minimum clarifies the existing declaration requirement. Review the two stricter validation/type rules below before upgrading from 0.5.0.
• Task input symbol keys. Task input literals containing own symbol keys now throw instead of silently discarding those keys. Remove symbol metadata from task data or represent needed values with string keys; valid JSON inputs and SDK request assets are unaffected.
• Primitive expression properties. .get() now requires an object or array receiver, including every member of a union. Calls such as string .get("length") or .get(0) become TypeScript errors instead of failing only at execution. Move primitive operations into a task callback. Generic helpers calling .get() must constrain their receiver type with extends object; unions must contain only object/array members. Object fields, array indexes, array length, and runtime missing-value checks retain their behavior.

Changes

Changed

• Landing navigation. Remove the "Explore the flows" header link and keep Docs visible on mobile. Package APIs are unchanged. (#78)

• Website sharing previews. Add the selected prismatic landing image and documentation image to Open Graph and Twitter metadata, requesting large image cards on both sites. The landing artwork uses a smaller, punctuation-free headline with clear separation between the “y” and “i”. Docs keep page-specific titles and descriptions with one shared image. Package APIs are unchanged; the previews become available after each site's manual publication. (#78)

Fixed

• Task input symbol keys. Reject own symbol keys in literal task inputs before template copying can silently discard them, including nested objects and arrays. Literal inputs fail during definition; referenced values retain their runtime rejection before the task callback. String-keyed JSON inputs and SDK request handling are unchanged. (#81)

• Expression property types. Reject primitive .get() receivers during type checking, aligning source and shipped declarations with the existing evaluator. Document object/array selection and a task-based string-length example. Fixes #49. (#82)

Documentation

• Compatibility docs published. Publish the reviewed import and setup guidance from PR #79 as GPT Sites version 20, preserving the existing sharing metadata. Record the verified source, deployment, and live checks in the publication receipt. Package APIs and npm contents are unchanged. (#80)

• Package compatibility and public imports. Include the /flow export in setup guidance and align the docs site, READMEs, and bundled agent instructions on Node, React, SDK, ESM, and the verified TypeScript 5.4+ declaration requirement. Focus setup on the three JavaScript entry points and automatic drawer styling, removing obsolete stylesheet-import guidance. Clarify required peers and server-only boundaries; package APIs and runtime requirements are unchanged. (#79)

• Verified 0.5.0 docs publication. Publish the reviewed release guidance as GPT Sites version 18 and record its canonical commit, hosting deployment, and matching live version/changelog checks. Package bytes and the landing Site are unchanged. (#76)

• README hero. Replace the root README's looping demo section with a static browser capture of the landing page heading and illustrative hierarchical flow, linked to the website. Include a reproducible capture script. Package APIs and the npm README are unchanged. (#74)

• 0.5.0 publication records. Record verified npm publication, archive integrity, registry consumers, and the recovered GitHub release/tag. Update mutable documentation to describe the published APIs. Docs version 18 was subsequently deployed and verified; see the publication receipt. (#75)

Maintenance

• Release verification dependencies. Install locked repository dependencies in the fresh release completion job before registry-consumer checks. This supplies the TypeScript compiler those checks use; it does not rebuild or republish the approved archive. The original 0.5.0 finish job failed because this install was missing. (#75)

npm package

Jev DevTools 0.5.0

Jev DevTools 0.5.0

Published from 64efa4c494a83207e94c67b42f6744802db18c11.

Compatibility and upgrade

• Runtime support is unchanged. React 18/19, Node 22.12+, and TypeSafe SDK >=0.7.0 <0.8.0 remain supported. Existing request and flow integrations keep their public entry points; APIs remain experimental before 1.0. Websites are separate private apps and are not included in the npm archive.
• Inspection data may differ. Expanded credential redaction and default-on redactAdditionalSensitiveData mask more captured/displayed fields. The display prop does not remove values from transport or memory; use server-side redaction for data that must never reach a browser. These policies do not alter SDK requests or application execution data.
• Replay and comparison are opt-in. Replay supplies captured Jev answers without inference, but tasks and request factories run again and can have side effects. Comparison executes both a replay and the supplied client's run; inspect answer differences as well as the top-level changed flag. Review exported fixtures and live responses before sharing them.

Changes

Added

• JevTools website. Add jevtools.dev with six simulated flow diagrams, System One primitive illustrations, a drawer recording, and a Flow API example. Include responsive navigation, reduced-motion support, and an animated hero. The standalone Vite app has isolated dependencies/styles and makes no inference requests. Docs and GitHub links lead to setup and source. (#72)

• Compare live runs with fixtures. Add compareWithFixture and formatComparison to jev-devtools/flow: compare a live client's run with a saved fixture, print the differences for CI logs, and get the live run back as a new fixture. Map items and loop iterations are reported under their composed ids; a step that ran on only one side sets changed. Recording observer failures and mutations to run snapshots cannot corrupt the comparison; captured response snapshots also prevent later observer mutations from hiding answer drift or rewriting the live fixture. Tasks run on both sides. (#32)

• Replay captured flows. Add Copy fixture to the Flows run header and replayClient(fixture) to jev-devtools/flow, so flow routing can be tested from captured answers with no network or API key. Map items and loop iterations are keyed by their request link (parent-id/index/step-id); tasks run locally on replay. flowFixture builds fixtures from captures in code. Fixture controls are scoped to DevTools; the clipboard fallback uses the drawer theme and keyboard focus styles. The repository's npm run replay helper accepts a macOS clipboard fixture, a JSON file or stdin for the refund, parallel and synthetic skill-shortlist examples, with optional input and expected-outcome checks. (#29)

Changed

• Fixture copy feedback. Confirm fixture copying with a brief animated Copied button state, respecting reduced-motion preferences. Keep partial-capture warnings and the clipboard fallback visible; clear stale feedback and fallback JSON when the display projection changes, including after pending clipboard operations. Document what fixtures contain and how to replay/share them in the flow guide. (#29)

Fixed

• Flow stream reconnections. Deliver required flow definitions to each inspector connection, including shared definitions first used by another session and definitions reused after clear or eviction. Avoid repeating definitions the reader still retains, preserve slow-reader catch-up, and reset browser flow caches and pending updates on reconnect. Public APIs and the version-1 stream format are unchanged. Fixes #42. (#68)

• Observer failures. Contain flow request observer failures before or after SDK dispatch, preserving the real result, request error, and cancellation without invoking the client twice. Custom observers should call through synchronously for trace linkage; failed or deferred recording can lose linkage but cannot replace execution. Public signatures and SDK retry behavior remain unchanged. Fixes #40. (#67)

• Observer data isolation. Detach task inputs, loop state, nested runs' data, and final values before exposing them to flow observers or redactors, so in-place capture edits cannot change execution. Reuse unchanged data snapshots for recorder caching and preserve shared references within each detached copy to avoid expanding small graphs into large trees. Runtime results and public APIs remain unchanged; non-JSON direct outputs remain available to callers but appear as [capture unavailable] in observer snapshots. Fixes #38. (#66)

• Response capture failures. Preserve successful request status when response parsing or redaction fails during recording. Omit the unavailable captured result and show a fixed safe warning without exposing redactor error messages or stacks. SDK results, genuine request errors/cancellation, and public APIs remain unchanged. Fixes #37. (#65)

Security

• Credential and personal-data redaction. Always redact documented credential aliases such as x-api-key, client_secret and sessionToken from DevTools inspection copies without changing SDK or runtime data. Add the default-on redactAdditionalSensitiveData component prop to mask supported email, phone, postal address, SSN and card-number fields in DevTools views only. Preserve question IDs and Choice labels/probabilities that resemble sensitive field names while masking personal data inside their content. Changing the prop updates existing views immediately and independently per viewer; additional personal values remain in capture/stream/browser memory, while credentials and custom server-redacted values cannot be revealed. No settings endpoint, checkbox, stream change or new Next.js route export is required. Actual HTTP headers/options remain uncaptured; field-name matching is not universal secret detection. Fixes #41. (#69)

Documentation

• Human-friendly docs and complete API reference. Add docs.jevtools.dev with 17 static pages: setup, framework guides, beginner flow examples, a public API glossary, and agent-readable Markdown. Show inputs, returns, and explained examples; pair synchronous flow definitions with awaited execution. Shiki/Twoslash and curated method/type help run at build time. Preserve deep links, label sticky method sections, and track reading position in the outline. (#70)

• Docs navigation and presentation. Add local search, copyable pnpm/npm/Yarn/Bun installation tabs, mobile navigation, persistent themes without unstyled page flashes, shared JevTools branding, and a passive GitHub star count. Clarify the independent community-project status. Keep interactions small and lazily loaded, with readable pages and links without JavaScript. (#70)

• Traceable docs publication. Build content, declarations, and the categorized changelog from one checkout. Emit a source/package-version manifest, reject dirty publication builds, and run browser checks with preview artifacts in CI. Keep GPT Sites deployment manual and separate from merging and npm publication, with an explicit release checklist and publication receipts. (#70)

• Website and documentation consolidation. Make jevtools.dev and the hosted docs the primary README/package entry points. Align repository guides, the offline setup skill, agent indexes, example archives, and version labels with the 0.5.0 candidate. Preserve repository reference paths and old docs anchors; clearly distinguish pending publication from npm availability. (#73)

Maintenance

• Landing validation. Add a separate read-only CI job that installs the landing app’s own lockfile, runs its tests, and builds it on Node 24. Keep website validation separate from package publishing and both manual Site deployments. (#73)

• Drawer CI setup. Run the React 18/19 drawer CI checks and release preparation on Ubuntu 24.04 using the runner's system libraries and Playwright's pinned Chromium headless shell, skipping per-run system package installation. In drawer CI, reuse matching installed React packages and read the lockfile for version overrides, verifying both React packages before browser checks. Package APIs, verification coverage, release approval, and publishing safeguards are unchanged. (#64)

• Release verification records. Record verified npm/GitHub publication for 0.4.1, including recovery from delayed npm visibility, exact-commit provenance, and archive integrity. Update installation guides to reflect publication.

• Registry processing timeout. Allow nearly ten minutes for npm version/latest verification after upload instead of about one minute. Keep manual approval, integrity/provenance checks, and the no-republish recovery rule unchanged; no package runt...

Jev DevTools 0.4.1

Jev DevTools 0.4.1

Published from 4ce235dd950b8b2f94e97d268ecbd5ae2b5b96ea.

Compatibility and upgrade

• React 18/19, Node 22.12+, SDK >=0.7.0 <0.8.0, public exports, and runtime flow behavior remain unchanged from 0.4.0.
• Published FlowExpression types now preserve their value types. Code relying on unsafe union narrowing or optional/nullable numeric comparisons may stop compiling; supply correctly typed values before comparing them.
• The drawer loads its own styles. Existing public CSS imports remain supported, but host styles and theme variables no longer affect internal flow styling. Document-level transforms and page JavaScript remain outside CSS isolation.

Changes

• Add a manually dispatched GitHub Actions release workflow using npm trusted publishing, with a required GitHub environment approval, exact-archive checks, registry consumer verification, and GitHub release completion. Support checking an existing tarball or registry version in the consumer scripts. Package APIs and runtime behavior are unchanged; publishing needs the configured npm trust and GitHub environment protection. (#60)

• Require a version-independent release checklist covering npm, the exact release tag, GitHub publication and Latest status, and explicit partial-completion reporting. Record the recovered v0.4.0 GitHub release and explain authentication options for remote publishing. Documentation only; existing checks and package compatibility are unchanged. (#59)

• Fix published FlowExpression declarations so they reject unsafe union narrowing and optional or nullable numeric comparisons, with packed-consumer type coverage. Runtime behavior is unchanged. Fixes #39. (#56)

• Standardize PR descriptions around Problem, Change, Scope and compatibility, Verification, and CSS review, with matching contributor and agent guidance. Preserve existing required checks and CSS review requirements; no automated description check or package compatibility change. (#58)

• Remove confirmed unused legacy layout, dot animation, caption, mark and instruction styles, unused textarea selectors, and declarations superseded by current rules or inline geometry. Preserve the public CSS export and current component appearance. Flow cascade conflicts and the question-connector/suppression rules remain deferred to #57. (#36)

• Scope connected-flow styles to the DevTools boundary and namespace their animation so the optional public stylesheet does not restyle host content. Keep the host reset in the shadow stylesheet instead of an expanded inline style attribute. Suppress page-authored host decorations, reset text direction and internal CSS-variable defaults, and keep flow hint colors independent of app theme variables. Remove redundant CSS imports from sample apps and setup snippets, and document automatic drawer styling in the guides and bundled skill. Existing component APIs and CSS imports remain compatible; document-level transforms and page JavaScript remain outside CSS isolation. (#36)

• Record verified npm publication metadata for 0.4.0, remove pending-publication instructions from installation docs, and link the published release. Documentation only; package behavior is unchanged. (#35)

npm package

Jev DevTools 0.4.0

Jev DevTools 0.4.0 expands the flow API and inspector with function tasks, runtime request factories, bounded collections, returning conditionals, numeric comparisons, and stateful loops.

Highlights

• Build flows with flow.map(), flow.if(), flow.loop(), and server function tasks; inspect collection items, loop iterations, and structured results inline.
• Explore six sample cookbooks for RAG passages, skill suggestion, SDE cascades, hierarchical classification, simple memory, and structure recovery. These apps and fixtures are repository examples, not part of the npm package.
• Use updated React/Next.js setup documentation and the bundled setup skill with version-matched flow guidance.
• Run the package and Next.js verification scripts on Windows.

Compatibility and upgrade

Install the SDK explicitly; it is now a peer dependency:

npm install jev-devtools@0.4.0 @typesafe-ai/sdk@0.7

Existing React mounting and static Jev requests remain supported. Upgrade the server and drawer together for the new flow records. The supported SDK range is >=0.7.0 <0.8.0.

Node middleware without authorize now accepts loopback connections only. Network-accessible, Docker, or proxy setups may need application authorization. Web Request servers must bind to 127.0.0.1 or configure authorize.

Flows remain experimental and in-process, without durable execution, automatic retries, or rollback.

Publication

The npm package was published on October 24, 2026 at 07:41:04 UTC from commit bc7f1609a6e94bf8fd9be4351db6983e8d0442ea. This GitHub release records that existing publication; it does not republish npm or include later changes on main.

npm package · 0.4.0 changelog · Release preparation #34 · Publication verification

Jev DevTools 0.3.0

Jev DevTools 0.3.0 adds connected multi-request flows and documentation for developers and coding agents.

• Define typed Jev calls, terminal branches, parallel lanes with joins, and named outcomes through the Node-only jev-devtools/flow API.
• Inspect full request diagrams together on one canvas, including incoming values, readable branch requirements, lane progress, and returned versus untaken outcomes.
• Add static titles and descriptions to every step. Browse compact expandable state/instruction properties and probability-weighted Noul cards.
• Use the bundled setup skill and references/flows.md for version-matched offline guidance, complete examples, and sample verification.

Existing root component props, server setup, and ordinary request calls remain compatible. Flow adoption is optional. This is an experimental in-process API, not a durable or distributed workflow engine. Business actions remain in your application.

Install: npm install jev-devtools@0.3.0

Flow guide · AI recipe · Release preparation PR #24 · Flow implementation PR #23

Validation used fixed samples, not live inference. Full local package, consumer, Next.js and drawer checks passed, along with typechecked/executed documentation examples for both branch outcomes. See PR #24 for the exact checks.