Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Persist typed browser probe results for downstream recipe steps

Open
  • Is something wrong?
#2,193 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
backend, tooling

Research direction

Start by locating the browser probe/page-evaluation commands and the recipe artifact registration flow. Trace how a typed result moves between recipe steps, then add contract and recipe integration tests covering successful reads and rejected paths; done means omitted output preserves existing behavior and persistence failures are distinguished.

Written by the indexing model from the issue text.

Description

Problem

Recipe browser probes can evaluate runtime page state, but cannot write the typed result to a caller-selected artifact path that a later recipe step can consume. This blocks pre-compilation runtime presentation evidence workflows.

Direction

Add a generic output-artifact contract to browser probe/page-evaluation commands. Persist the typed result atomically within the declared artifact root, register an artifact ref, and make it available to subsequent workflow steps.

Acceptance

  • Caller can declare a safe relative output artifact path.
  • Typed browser result is atomically persisted and registered.
  • A later recipe step can read the file in the same run.
  • Path traversal and writes outside the artifact root are rejected.
  • Failure evidence distinguishes evaluation, serialization, and persistence errors.
  • Existing browser probe behavior is unchanged when omitted.
  • Contract and recipe integration tests cover success and rejection.

Dependency

Automattic/static-site-importer#796, producer commit f246198c; Automattic/blocks-engine#757.

AI assistance

OpenAI gpt-5.6-sol through OpenCode analyzed the cross-recipe gap and drafted this issue. Chris Huber remains responsible for scope and implementation decisions.

Dominant language
TypeScript
Stars
17
Forks
4
Avg merge
1h 11m
Merged PRs (30d)
39

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/wp-codebox

All issues in Automattic/wp-codebox

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.