Skip to content

docs: add tsnet migration status — what is left#270

Merged
GeiserX merged 1 commit into
mainfrom
docs/migration-status
Jun 15, 2026
Merged

docs: add tsnet migration status — what is left#270
GeiserX merged 1 commit into
mainfrom
docs/migration-status

Conversation

@GeiserX

@GeiserX GeiserX commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Adds docs/MIGRATION_STATUS.md — a complete "what's left of the tsnet→Rust migration" status:

  • Per-subsystem verdicts (PRESENT / PARTIAL / ABSENT) across all 14 major subsystems, each cross-referenced to its open tsr- bead(s).
  • Public Device/facade API surface vs Go tsnet.Server/LocalClient — what's implemented, partial, or missing.
  • Intentional fork supersets (IPv4-only, fail-closed egress, ring-clean crypto, residential-proxy exit) flagged as design posture, not gaps.
  • Downstream daemon engine-asks (ci: bump the github-actions group with 5 updates #1Responder-side cookie/mac2 issuance (under-load DoS mitigation) #27) status — shipped vs remaining.
  • Full open-bead backlog by priority (P0 epic + P2 leverage items + the P3 tail) — with the note that bd list --status open stays the source of truth.

Docs only. Mermaid diagram included; states the conclusions, no sources cited.

Signed-off-by: Sergio sergio@geiser.cloud

Created using Claude Code (Opus 4.8)

A complete status of the pure-Rust engine versus Go tsnet/tailscaled v1.100.0:
per-subsystem PRESENT/PARTIAL/ABSENT verdicts, the public Device/facade API
surface vs tsnet, the intentional fork supersets that are not gaps, the
downstream daemon engine-asks status, and the full open-bead backlog by
priority. The orienting map for what remains; the beads stay the source of
truth.

Signed-off-by: GeiserX <9169332+GeiserX@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@GeiserX, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 20 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9bc3386b-b365-495c-bf16-9ec9a5dbd24e

📥 Commits

Reviewing files that changed from the base of the PR and between 35e5db2 and da18c83.

📒 Files selected for processing (1)
  • docs/MIGRATION_STATUS.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/migration-status

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@GeiserX GeiserX merged commit a095d79 into main Jun 15, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant