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

feat: tracking traces, replay and debugging tools

Open
  • Is something wrong?
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, json, node.js, playwright, typescript
Domain
observability, testing, tooling

Research direction

Start by reading the related issue #5 and inspect tests/helpers/frames.ts to understand the existing frame data. The proposal also names scripts/trace-diff.mjs and check-agent-docs.mjs; check which trace tasks are unclaimed and how the Node integration tests run. Done means same-build traces report no difference and a deliberate filter change reports one, with a baseline versus facade diff available for #5.

Written by the indexing model from the issue text.

Description

Part of Phase 1 (#1). Gives #5 an objective "same behaviour" check.

Context

#5 is accepted when the e2e tests behave the same with less tracking code. The e2e tests check that tracking works, not how it behaves frame by frame. Traces make the comparison measurable.

Proposal

  • Trace format: JSONL with one record per frame (the FrameResult shape: per-marker pose, found / lost transitions, timing), plus a header with the settings and the jsartoolkit-nft version.
  • Recording: from the browser (an Inspector option, or a debug.trace node) and from the Node integration tests.
  • Replay: a deterministic replay in Node from recorded frames (tests/helpers/frames.ts).
  • Diff: scripts/trace-diff.mjs compares two traces and reports pose deltas, found / lost timing and jitter. Uses: ArtkSession vs the facade, or two jsartoolkit-nft versions.
  • Agent tooling:
    • a .mcp.json with Playwright MCP (drive the studio with the fake camera) and Chrome DevTools MCP (console including the worker, network for the 404 hosting rule, performance traces of the tracking loop), versions pinned, Chrome DevTools started with --isolated;
    • a tracking-debugger skill or agent that reproduces, records, diffs and reports.

Tasks

  • Trace format and recorder (Node)
  • Recorder in the browser
  • Replay and trace-diff
  • Baseline traces of the current ArtkSession before the facade lands
  • .mcp.json (Playwright, Chrome DevTools); check-agent-docs.mjs validates it
  • tracking-debugger skill

Acceptance

  • trace-diff on two runs of the same build reports no difference; on a deliberate filter change it reports one.
  • #5 can attach a baseline vs facade diff to its PR.

Generated by Claude Code

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
2d 15m
Merged PRs (30d)
2

Getting set up

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 webarkit/webarkit-studio

All issues in webarkit/webarkit-studio

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.