@playform/ets-hook-dsh-normalize-ellipsis

The DeepSeek Harness Plugin Family for PlayForm.

[!NOTE]

The ellipsis normalizer for model output - a DeepSeek Harness plugin that hooks the llm/stream waterfall (the interceptable wrapper around EVERY streaming model call, bound to the LlmRuntime) and normalizes the horizontal ellipsis in model output, live in the transcript: every typographic three-dot ellipsis code point becomes the ASCII three-dot sequence - U+2026 to ....

A CLASS flavor of the normalize family: the core's Ellipsis class plus a configurable replacement string (default ...).

The @-sentence identity: Hook @ DSH @ Normalize @ Ellipsis.

The family's raw-write tool (registered by ets-hook-dsh-normalize-dash) bypasses this flavor's transforms too - the exemption is family-wide: the core's Stream/Chunk + Stream/Block pass every raw-write call through by identity, so the tool's explicit normalize parameter (default false = verbatim) is the only normalization it applies.

Where It Fits

Family position (the @-sentence Hook @ DSH @ Normalize @ Ellipsis): a hook child of the ets-plugin-dsh-factory service and the ets-hook-dsh-core machinery; the second of the six stream normalizer siblings.

One of six siblings in the stream-normalization family, all built on the shared machinery - ets-plugin-dsh-factory for State/Append (and the named Schema helper, shared: false, for the config), ets-hook-dsh-core for the Ellipsis class and the generic Replace/Chunk/Block dispatch:

| flavor | table | substitution | | ----------------------------------------------------------------- | ---------------------- | ----------------------------- | | ets-hook-dsh-normalize-dash | core Dashes class | → replacement (default -) | | ets-hook-dsh-normalize-quotes | core Quotes MAP | curly → straight | | ets-hook-dsh-normalize-ellipsis (this bundle) | core Ellipsis class | U+2026 → ... | | ets-hook-dsh-normalize-spaces | core Spaces class | unicode spaces → " " | | ets-hook-dsh-normalize-invisible | core Invisible class | removed (default "") | | ets-hook-dsh-normalize-fullwidth | core Fullwidth MAP | full-width → half-width |

A non-manifest factory consumer: it injects ["pluginFactory"] and uses State (cell unwrap + shared Ledger/Enabled mappings + its own fields), Append and Journal (the shared P5 record on every N > 0 pass); the config is composed by the factory's standalone Schema helper with shared: false - the minimal block, no fs/observed dead fields.

It touches no files, so fs/write-intent and fs/observed never see it; it wraps the downstream result and always calls next(), so it composes with other llm/stream listeners regardless of registration order.

The DSH plugin family is the DeepSeek Harness plugin layer of the PlayForm ecosystem: TypeScript-first Source/ → Target/, the deterministic @playform build, prepublishOnly-only - the same conventions as every other @playform package.

Install

Terminal (registry)

pnpm add @playform/ets-hook-dsh-normalize-ellipsis

1. Remote / dependency install (auto-activation): pnpm add @playform/ets-hook-dsh-normalize-ellipsis in a profile dir (+ the package name in dsh.profile.bundles, or dsh plugin add) - installed automatically and activated at the next host start.
2. Local git clone: clone → pnpm install inside the bundle (its pnpm-workspace.yaml pins packages: [.] so the install lands in the bundle, not the workspace root) → build → dsh plugin --profile <name> add <this directory>.
3. Tarball / npm: dsh plugin --profile <name> add <tarball-or-spec> - the package ships built Target/ (minified, .d.ts twins), so no build runs at install time.

Verify with the ets-hook-dsh-normalize-ellipsis: activated (...) ledger line.

Usage

The bundle is configured through its cordis.patch.yml row (or the profile's dsh.bundle manifest) - the full config table is in The Config:

- insert:
      - id: ets-hook-dsh-normalize-ellipsis
        name: "@playform/ets-hook-dsh-normalize-ellipsis"
        config:
            log: true
            logFile: ~/.dsh/ets-hook-dsh-normalize-ellipsis.log
            replacement: "..."

The shared Effect-TS plumbing - the runtime wiring, the stream machinery and the hook contract types - comes from the base ets-base-dsh package.

The Problem

Text processors collapse the typographic three-dot run into a single code point - U+2026, the horizontal ellipsis.

In code blocks, commands and diffs the collapsed form is simply wrong: three literal dots are what every parser, shell and search expects.

This flavor makes the ASCII spelling the one that reaches the transcript.

How It Works

The stream pipeline

  llm/stream waterfall (options, next)     the interceptable wrapper around
       │                                   EVERY streaming model call
       ▼  next() called FIRST, always - options never touched
  Normalize(upstream, state)               the async generator
       │   for await (chunk of upstream)
       ▼
  CoreChunk(chunk, transform, reasoning, toolArgs, raw)  the core's per-chunk dispatch
       │
       ├─ text-delta ─────────► Replace(text, Ellipsis, "...")  rewrite the text field
       ├─ reasoning-delta ────► same, when normalizeReasoning (default ON)
       ├─ block-end ──────────► the assembled block's text fields -
       │                        TextBlock.text / ReasoningBlock.text (plus a
       │                        runtime `thinking` string field) - the deltas
       │                        AND the block must agree, or consumers see
       │                        inconsistencies
       ├─ tool-call-delta ────► Replace(argumentsDelta, Ellipsis, "...") when
       │                        normalizeToolArguments (IMPLEMENTED, default
       │                        OFF - execution-critical raw JSON, the user's
       │                        accepted risk; this profile's patch turns it
       │                        on) - the assembled ToolCallBlock.arguments
       │                        follows the same flag via block-end
       │                        The gate is THREE-WAY with the flag on: a
       │                        delta/block whose `name` is "edit", "raw-write"
       │                        or "normalize-file" passes through BY IDENTITY
       │                        (the edit tool's `old_string` must match the real
       │                        file bytes; the raw-write tool owns its content
       │                        normalization; the normalize-file tool's arguments
       │                        carry a file path - a normalized dash inside a
       │                        filename would corrupt the target),
       │                        and a call whose arguments open with the
       │                        `{"__normalize":false` marker (FIRST key,
       │                        tracked per call id) passes through
       │                        UNNORMALIZED with the marker entry stripped,
       │                        so the executed call carries no unknown key
       └─ block-start / usage / finish
                                 ──► PASSTHROUGH BY IDENTITY, ALWAYS
                                     (usage/finish ordering is the
                                      adapter contract)
       │   count === 0 → original chunk BY IDENTITY; rewritten → shallow copy
       ▼
  yield ──► downstream consumers = the live UI + the durable transcript
       │    (order preserved, no buffering; upstream throws propagate)
       ▼  normal loop completion, Count > 0
  Factory.Append ──► `ets-hook-dsh-normalize-ellipsis: normalized N ellipsis char(s) in one stream`

The transform

Exactly the core's Ellipsis class (@playform/ets-hook-dsh-core's Normalize/Ellipsis), applied per text segment through the core's generic class-to-string Replace:

[\u2026]  →  replacement

U+2026 (horizontal ellipsis - the typographic three-dot run collapsed into one code point by text processors) becomes the config replacement (default ..., the ASCII three-dot sequence - the ellipsis's own ASCII spelling).

• No context rules - whole-chunk replacement, no lookahead; chunk-boundary-safe.
• The replacement is applied with a function replacer, so a custom replacement containing $ patterns is inserted literally.
• Replaced characters are counted per stream for the ledger line - each replaced ellipsis code point counts once, even though the default replacement emits three characters.

The Pitfalls

• U+2026 only - the class matches exactly the horizontal ellipsis; a pre-existing three-dot sequence and Unicode's other ellipsis forms are never touched.
• A dependency alone is NOT activation - the package must be in dsh.profile.bundles (or the patch row inserted), or no listener registers and no ledger exists.
• The stream gate rewrites model output only - it never touches disk; files already on disk are the normalize-file tool's job.
• The count is per replaced code point - N counts matched characters, not output characters; N = 0 and an upstream throw both write no count line and no journal record.

The Config

| Field | Type | Default | Volatile | Meaning | | ------------------------ | ------- | ---------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | log | boolean | true | yes | write the durable ledger file | | logFile | string | ~/.dsh/ets-hook-dsh-normalize-ellipsis.log | yes | the ellipsis ledger (separate from the family's logs) | | replacement | string | ... | yes | the transform's only knob - hot-editable, the next stream picks it up with no remount | | normalizeReasoning | boolean | true | no | normalize reasoning deltas and the assembled reasoning block too | | normalizeToolArguments | boolean | false | no | IMPLEMENTED (default OFF): rewrite the tool-call argumentsDelta and the assembled ToolCallBlock.arguments when on (with three exemptions: edit, raw-write and normalize-file calls pass through by identity (the edit tool's old_string must match the real file bytes; the raw-write tool owns its content normalization through its explicit normalize parameter; the normalize-file tool's arguments carry a file path - a normalized dash inside a filename would corrupt the target); and a call whose arguments open with the {"__normalize":false first-key marker passes through unnormalized, the marker entry stripped) - execution-critical raw JSON, the user's accepted risk; the example patch turns it on |

Volatile cells commit without remounting the plugin; the factory's State builder unwraps them defensively.

The Granular Scopes (all volatile)

The scopes object gates every arm of the ets-hook-dsh-normalize-ellipsis hook independently — the defaults are exactly the pre-scopes behavior, and because the schema shape is identical in every family hook, one grouped override in the profile patch turns the whole family off in one edit (see the patch fragment at the end of this section). The whole object carries the volatile marker (its leaves stay plain — schemastery rejects volatile leaves under an enclosing volatile field): one leaf change commits one loader/volatile-update dispatch whose whole object the State's refresh listener re-reads — live, silent, no remount, no new activation line.

| Scope | Default | Gates | | ------------ | ------- | --------------------------------------------------------------------- | | conversation | on | text-delta text + the assembled text/reasoning blocks | | reasoning | on | the reasoning-delta sub-gate (ANDed with normalizeReasoning) | | toolInput | off | the tool-call arguments arm (OR-ed with normalizeToolArguments) | | toolResults | off | the tools/post-execute arm (tool results in the transcript) | | files | on | inert in a stream flavor (present so one patch override drives the whole family) | | batch | off | the agent/pre-step arm (the incoming step batch) |

normalizeToolArguments is kept and OR-ed in (effective toolInput = the field || scopes.toolInput), so every existing profile keeps working.

The per-call {"__normalize":false first-key marker is the tool-args arm's escape hatch — the "leave that search alone" control: a deliberate search for an irregular character (an em dash, a curly quote, a full-width form as a PATTERN) survives byte-exact while the rest of the call stream normalizes. Documented edges: the marker must be the FIRST key, and a pathologically tiny first delta (shorter than the marker) is invisible to the startsWith probe — the call normalizes normally.

toolResultsExempt (volatile): a tool result whose exec name is listed passes the tool-results arm by identity — read, edit, raw-write, normalize-file, ccr_retrieve, subagent, ask_user_question by default.

The Overpass Arms

Two additional listeners, both registered at apply and both opt-in (gated at RUNTIME on the scope cells, so flipping a scope lands through the P10 volatile-refresh without any re-registration):

• Tool results — tools/post-execute, { prepend: true } (OUTERMOST vs the ccr hook's own prepended gate: the ccr compression sees the NORMALIZED bytes; the <<<CCR: marker guard makes any load order safe). Accepted, non-value-carrying decisions only; TEXT blocks only (never tool-call/argument blocks); N = 0 is a true no-op — no ledger line; fail-open. The invisibility contract: the replacement is PRE-COMMIT — the waterfall settles before the result is appended to the durable log — so the model only ever sees the normalized output and never notices the replacement (the write-path counterpart is the governance trio's never-notify precedent: the tool result is built from the author's own content, and the observation-policy's version record is refreshed by the re-emitted fs/observed).
• Step batch — agent/pre-step, default order. While scopes.batch is on every incoming batch is normalized; the command's one-shot arm fires ONCE regardless of the scope value and is cleared after one use. Text blocks only; never the assistant/tool history.

The ellipsis overpass lines (N > 0 only):

ets-hook-dsh-normalize-ellipsis: overpass: normalized N char(s) in tool result <toolName> <callId>
ets-hook-dsh-normalize-ellipsis: overpass: normalized N char(s) in step batch (turn T step S)
ets-hook-dsh-normalize-ellipsis: overpass: swept K file(s), normalized M char(s)

The normalize-overpass Command

Registered through the commands service when it is present (probe-once — a missing service simply skips the registration). Grammar:

| Input | Effect | | ------------------ | --------------------------------------------------------------------------------- | | files <path…> | declined — the sweep is owned by the normalize-file hook | | batch | arm the one-shot step-batch overpass (consumed by the next incoming batch) | | results on\|off | flip scopes.toolResults via the settings service / config editor — never direct State mutation; absent services → reports the settings-UI path | | scopes | read-only report of the current effective values (the activation line never changes) |

The Patch-Level Global Off

- id: ets-hook-dsh-normalize-ellipsis
  config:
    scopes:
      conversation: false
      reasoning: false
      toolInput: false
      toolResults: false
      files: false
      batch: false

In Action

One stream, one transformation.

The model emits the collapsed typographic ellipsis; the live UI and the transcript receive three ASCII dots:

text-delta in (what the model wrote):

  "loading the modules, one by one … then the whole set … and then …"

text-delta out (what reaches the transcript):

  "loading the modules, one by one ... then the whole set ... and then ..."

Each U+2026 code point becomes the three-dot ASCII sequence ...; dots that were already ASCII are untouched.

Each replaced code point counts once in the ledger even though it expands to three characters - which is why the sample's three U+2026 code points show up as normalized 3 ellipsis char(s), not nine output characters:

ets-hook-dsh-normalize-ellipsis: normalized 3 ellipsis char(s) in one stream

The replacement is hot-editable: change it in the config (say to . . .) and the very next stream picks it up with no remount.

The same pass runs over reasoning deltas when normalizeReasoning is on, and over tool-call arguments when the example patch enables normalizeToolArguments - with the edit, raw-write and normalize-file names exempt and the raw-marker calls passing through unnormalized.

The Ledger

Two lines, both written through the factory's Append (the ets-hook-dsh-normalize-ellipsis: prefix is the logger's <State.Module>:; the durable file line is [<ISO>] <message>):

ets-hook-dsh-normalize-ellipsis: activated (replacement=..., reasoning=on, toolArgs=off, logFile=~/.dsh/ets-hook-dsh-normalize-ellipsis.log)
ets-hook-dsh-normalize-ellipsis: normalized N ellipsis char(s) in one stream

The activation line is written by apply(); the count line only follows a normal stream completion and only when N > 0 (a thrown-away stream writes no ledger line).

Every N > 0 pass also journals one normalized record into the shared package_governance v2 domain - event normalized, path = the empty stream-level path, detail byte-identical to the count line - best-effort: with no storage facility the record buffers or drops, and the human ledger stays the complete record.

License 📜

CC0-1.0.