alktunnels/tasks/tunnels/corrmiss-alkssh-adopt.md at 0ceecf582b7ebc118d5c547e2c63181a00cd0808

0 Fork 0

Files

T

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

- Rewrote the remaining em dashes outside docs/reviews/ (preserved as
  historical record, matching the alktty precedent): tests/ (313),
  fuzz/ (34 plus one shell comment), tasks/ (671 plus 12 kept in
  fences), docs/research + sdd_process + plans (525 plus 25 in
  fences), docs/architecture/overview.md fence labels (13), README,
  CHANGELOG, AGENTS.md, fuzz/README.md (176), and the
  .opencode/agents prompts (110)
- Rewrote fenced content too: ASCII tree and module-map label
  separators, Rust snippet comments, and template placeholders; wire
  data, JSON/BAST examples, and transcripts survive verbatim
- Rewrote 6 assert/expect message literals in tests/ and 2 format
  strings in fuzz/shared/src; no test data changed
- Added Project Convention 18: no em dashes in prose (doc comments,
  markdown including docs/ and tasks/, agent prompts, commit
  messages); fence content rule, en-dash clause rule, and the
  no-spaced-hyphen prohibition follow alktty's convention 15

Follows 6b20924 (src doc comments) and cd0afe0 (docs/architecture).

Verification: cargo test (141 pass); cargo clippy --all-targets -D
warnings; cargo fmt --check; cargo doc --no-deps; wasm check and
clippy for wasm32-unknown-unknown with -D warnings; em dash grep over
the repo returns matches only in docs/reviews/

2026-11-03 14:12:46 +00:00

2.4 KiB

Raw Blame History

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

name

status

depends_on

scope

risk

impact

level

Description

Cross-repo pointer: executed in the alkssh repo, not here. This task exists in this repo's decomposition so the dependency graph and the plan's ordering (W1 → {W2, W3}) stay visible; the work session is booked in alkssh (its wave-3 review gate item 5 lineage from tasks/implementation/review-wave-3.md item 5 and docs/plans/implementation.md "Still booked with their owners").

Per plan 003 §W2 (read that section, since it is the spec for this session; this task only carries the dependency + the acceptance summary):

Move pump_forwarded_arrival's route lookup (alkssh src/tunnel_map.rs, the ListenRouter lookup) into the new register_tunnel_forwarded_openable_with_establisher gate (consumed from alktunnels at the version W1 landed).
The residual handler keeps decline_arrival("correlation-miss", …) at its shipped debug level for the narrow post-open race only.
Verify the fabric-side silence fix: a stale-token arrival now fails the open (alkssh-side typed error; the producer-side generic arm fires with a parseable reason, so the race window no longer produces a zero-signal pump.
Fold alkssh's em-dash doc cleanup into its release for this change (user-owned, out of plan scope).

Acceptance Criteria (alkssh-side; the plan-level §W2 box)

alkssh serves the gate shape (the route lookup rides the gate; the residual handler is the narrow race only)
A stale-token arrival produces a typed call-plane failure (no zero-signal pump)
The residual class is named correlation-miss at debug
alkssh's release includes its doc cleanup (user-owned)

References

docs/plans/003-correlation-miss-resolve.md §W2 (THE spec)
docs/reviews/003-correlation-miss-arrival-class-alkssh-input.md
The alkssh repo: src/tunnel_map.rs (pump_forwarded_arrival, ListenRouter), src/observe.rs
This repo's landed surface (W1): tasks/tunnels/corrmiss-forwarded-gate.md

Notes

To be filled by the executing session (in alkssh)

Summary

To be filled on completion

2.4 KiB Raw Blame History