npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@hokusai/adapter-wavemill

v0.4.0

Published

Wavemill is the public reference adapter for showing how a richer harness composes over `@hokusai/core` without turning Wavemill internals into the SDK architecture.

Readme

@hokusai/adapter-wavemill

Wavemill is the public reference adapter for showing how a richer harness composes over @hokusai/core without turning Wavemill internals into the SDK architecture.

What this adapter contributes

  • Correlation replay metadata via priorCorrelationId and formatCorrelation(...).
  • Per-customer redaction lexicon support with customerNames.
  • Harness outcome extensions for spendUsdBucket and wallClockMinutes.
  • A Wavemill default task profile: deep reasoning for feature/refactor work, ['shell', 'git', 'test runner'], and ['pnpm workspace'].
  • Re-exported conformance fixtures for task packets, outcomes, and anonymization.

Vs a simpler harness

The examples/reference-harness shape can stick to plain task prompts, default reasoning inference, and minimal preview/output wiring. Wavemill adds replay-aware dispatch context, customer-specific redaction input, and typed harness telemetry that a simpler harness would not need.

Route/report flow

import {
  HokusaiClient,
  HokusaiDispatchBuilder,
  InMemoryModelRegistry,
} from '@hokusai/core';
import {
  reportWavemillOutcome,
  routeWithWavemill,
} from '@hokusai/adapter-wavemill';

const client = new HokusaiClient({ apiKey: 'k_prod_xxx' });
const dispatchBuilder = new HokusaiDispatchBuilder({
  consent: {
    subjectId: 'developer-123',
    grantedScopes: ['task-execution'],
  },
  modelRegistry: new InMemoryModelRegistry([
    {
      id: 'gpt-5-codex',
      provider: 'openai',
      family: 'gpt',
      capabilities: ['reasoning', 'tool-use'],
      default: true,
    },
  ]),
});

await routeWithWavemill({
  client,
  dispatchBuilder,
  task: {
    id: 'task-1',
    prompt: 'Implement the planned adapter change.',
  },
  modelId: 'gpt-5-codex',
});

// DEPRECATED. `reportWavemillOutcome` posts to the legacy `/outcomes` endpoint,
// which patches an inference log and bypasses training and reward attribution
// entirely — the row trains nothing and earns nothing. See
// docs/reference-pattern.md. New integrations should build a contribution row
// with `buildHarnessOutcomeRow()` and submit it via `client.submitContribution()`;
// `examples/reference-harness` shows the full loop.
await reportWavemillOutcome({
  client,
  input: {
    correlationId: 'route_123',
    recommendedModel: 'gpt-5-codex',
    actualModel: 'gpt-5-codex',
    recommendationAccepted: true,
    completionStatus: 'succeeded',
    latencyBucket: 'medium',
    costBucket: 'medium',
    tokenBucket: 'medium',
    spendUsdBucket: '0.50-1.00',
    wallClockMinutes: 18,
  },
});

Conformance fixtures

Use wavemillConformanceFixtures when you want one import that covers:

  • taskPacket
  • successOutcome
  • overriddenOutcome
  • anonymization