Skip to content

Sprint 10.3 — Build and smoke-test browser artifact #19

Description

@maruson08

Problem / motivation

Future same-origin vendoring requires one standalone browser-native artifact verified in a real browser context.

Scope

  • produce one readable browser ESM artifact exposing inspectMetadata, cleanMetadata, and verifyMetadata
  • ensure no runtime fetch, Node-only API, or production dependency
  • add deterministic browser execution smoke coverage with small fixtures

Non-goals

  • Secure Tools integration
  • CDN loading
  • multiple/minified bundle variants

Acceptance criteria

  • artifact builds reproducibly and remains auditable
  • real browser smoke import/API execution passes
  • artifact is excluded or deliberately placed in release payloads as documented

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions