You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TASK-035-006: Update Obsidian notes and config files for TurboHTTP branding
Replace all TurboHttp project/namespace references with TurboHTTP across
109 Obsidian vault notes and the .gitignore file. Type names
(TurboHttpClient, TurboHttpMetrics, etc.) are intentionally preserved.
The likec4 config was already correct from a prior task.
Copy file name to clipboardExpand all lines: notes/00-Index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# TurboHttp Knowledge Base
1
+
# TurboHTTP Knowledge Base
2
2
3
-
This is the central hub for all TurboHttp project knowledge — connecting session logs, architecture decisions, RFC compliance notes, and feature planning.
3
+
This is the central hub for all TurboHTTP project knowledge — connecting session logs, architecture decisions, RFC compliance notes, and feature planning.
4
4
5
5
## Architecture & Design Decisions
6
6
@@ -60,7 +60,7 @@ See [Architecture Notes](./Architecture/) for full decision records.
Copy file name to clipboardExpand all lines: notes/Architecture/00-ONBOARDING.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Developer Onboarding Guide
3
3
description: >-
4
-
Start here — orients new developers and fresh AI sessions to TurboHttp
4
+
Start here — orients new developers and fresh AI sessions to TurboHTTP
5
5
architecture, workflows, and vault navigation
6
6
tags:
7
7
- architecture
@@ -13,11 +13,11 @@ updated: '2026-04-07'
13
13
---
14
14
# Developer Onboarding Guide
15
15
16
-
Welcome to TurboHttp. This note is the single starting point for new developers and fresh AI agent sessions. Read it once, then follow the links to deeper references.
16
+
Welcome to TurboHTTP. This note is the single starting point for new developers and fresh AI agent sessions. Read it once, then follow the links to deeper references.
17
17
18
18
## Project Purpose
19
19
20
-
TurboHttp is a high-performance HTTP client library for .NET built on Akka.Streams. It implements HTTP/1.0, HTTP/1.1, HTTP/2, and HTTP/3 (QUIC) with full RFC compliance, including:
20
+
TurboHTTP is a high-performance HTTP client library for .NET built on Akka.Streams. It implements HTTP/1.0, HTTP/1.1, HTTP/2, and HTTP/3 (QUIC) with full RFC compliance, including:
21
21
22
22
- Connection pooling and keep-alive management
23
23
- Redirect following and retry logic
@@ -40,7 +40,7 @@ The library exposes an `ITurboHttpClient` interface compatible with `HttpMessage
Copy file name to clipboardExpand all lines: notes/Architecture/Analysis/10-DEADLOCK_ANALYSIS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ status: all-fixed
9
9
---
10
10
# Deadlock Analysis Catalog
11
11
12
-
Complete catalog of all known deadlock patterns in TurboHttp, organized by layer. Each entry includes root cause, affected files, fix status, and test coverage.
12
+
Complete catalog of all known deadlock patterns in TurboHTTP, organized by layer. Each entry includes root cause, affected files, fix status, and test coverage.
13
13
14
14
> **DL-009** and **DL-010** are **Fixed** — resolved by Feature 030 (IConnectionScope + linear topology rewrite).
Copy file name to clipboardExpand all lines: notes/Architecture/Analysis/11-STAGE_COMPLETION_AUDIT.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ tags:
13
13
14
14
## Executive Summary
15
15
16
-
A systematic audit of all 48 GraphStage implementations in TurboHttp found **20 confirmed bugs** where stream termination signals (onUpstreamFinish, onUpstreamFailure, onDownstreamFinish) were not properly propagated. These omissions violated the Reactive Streams contract and could lead to **backpressure deadlocks**, where downstream stages wait indefinitely for termination signals that never arrive.
16
+
A systematic audit of all 48 GraphStage implementations in TurboHTTP found **20 confirmed bugs** where stream termination signals (onUpstreamFinish, onUpstreamFailure, onDownstreamFinish) were not properly propagated. These omissions violated the Reactive Streams contract and could lead to **backpressure deadlocks**, where downstream stages wait indefinitely for termination signals that never arrive.
17
17
18
-
**Status (2026-03-27): All 20 bugs fixed.** Each fix adds `FailStage(ex)` (or `Fail(outlet, ex)` for BidiStages) after existing logging. 17 regression tests added in `TurboHttp.StreamTests/Streams/26–29_*StageCompletionRegressionTests.cs`. **0 open bugs remain.**
18
+
**Status (2026-03-27): All 20 bugs fixed.** Each fix adds `FailStage(ex)` (or `Fail(outlet, ex)` for BidiStages) after existing logging. 17 regression tests added in `TurboHTTP.StreamTests/Streams/26–29_*StageCompletionRegressionTests.cs`. **0 open bugs remain.**
0 commit comments