alksocks/tasks/architecture/oq-sk2-06-wasm-adapter-story.md at 126ae9ccf62f9c86681699b055b7bd442654741f

0 Fork 0

Files

T

glm-5.3-flash e196ed43e3 docs: remove em dashes from repo prose and forbid them going forward

- Rewrote em dash prose across the whole tree outside docs/reviews/
  (the historical reviews stay verbatim, matching the alktunnels and
  alktty precedent): src doc comments and inline comments (587),
  docs/architecture (319), docs/research + sdd_process (484), tests
  (361), tasks (899), fuzz (28), README/CHANGELOG/Cargo.toml (77),
  AGENTS.md (85), and the .opencode/agents prompts (109)
- Fenced content follows the precedent: comments, ASCII-diagram label
  separators, and template placeholders rewritten; wire data, JSON/BAST
  documents, byte diagrams, and transcripts survive verbatim; assert,
  expect, panic, error-display, and format message literals rewritten
  as prose; no code, fixture, or test data change
- src/rfc1928/LICENSE: the two dashes in alksocks' own provenance
  header rewritten; the MIT legal text untouched
- AGENTS.md adds Project Convention 18: no em dashes in prose; varied
  restructure, no spaced-hyphen substitutes, fenced prose rule, en
  dash numeric ranges exempt, docs/reviews/ exempt from the greps
- tasks/*.md frontmatter: the name values rewritten by the sweep are
  now quoted (a raw colon inside an unquoted YAML scalar parsed as
  null); taskgraph validate reports 37 tasks, no issues

Verification: cargo test; cargo clippy --all-targets -D warnings;
cargo fmt --check; cargo doc --no-deps; fuzz corpus replay
(cargo test --manifest-path fuzz/shared/Cargo.toml); wasm check and
clippy for wasm32-unknown-unknown with -D warnings; em dash grep over
the repo returns matches only in docs/reviews/ and the bast.md BAST
JSON data fence

2026-11-03 19:31:53 +00:00

1.7 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

architecture/oq-sk2-06-wasm-adapter-story

Track for OQ-SK2-06 unblock condition (sandboxed-wasm-consumer adapter)

pending

single

trivial

component

research

Description

External-trigger tracker for OQ-SK2-06 (docs/architecture/ open-questions.md): the sandboxed-wasm-consumer adapter story. This task is NOT actionable work; it tracks whether the external unblocking condition has arrived. Tagged [external-trigger, deferred-oq] per docs/sdd_process.md §Deferred OQs.

Unblocking condition: a concrete sandboxed-adapter use case exists: a TS/Python (or other) adapter embedding the alksocks consumer session in a wasm runtime.

Trigger ownership (checked 2026-09-28): external by verified default: no planned suite-internal surface names a sandboxed alksocks consumer (see the OQ's "Trigger ownership" bullet for the check). If a product surface later names one, convert this tracker to an owned dependency in the same round.

Work

When the condition arrives:

Mark this task completed (the condition arrived).
Transition OQ-SK2-06 from deferred(scope) to open (or directly to resolved if no architecture decision remains).
Decide: how much wasm surface to exercise in the default crate (bindings ergonomics, which session types to expose, whether any surface is missing).

Verification

N/A (tracking task; trivial risk, no code).

Out of scope

Any wasm-binding implementation; any protocol change (the wasm-clean default-crate invariant, ADR-009, holds regardless).

Notes

Agent fills this during implementation.

Summary

Agent fills this on completion.

1.7 KiB Raw Blame History