chore(devtools): record bitty-core jurisdiction + fix stale docs + sync trace accounting semantics

AGENTS.md

@@ -7,8 +7,12 @@
 - The canonical GitHub organization is <https://github.com/bitty-terminal>.
 - Core debug and command contracts belong to the [`bitty`](https://github.com/bitty-terminal/bitty) repository; canonical
   architecture, security, and public behavior belong to [`bitty-docs`](https://github.com/bitty-terminal/bitty-docs).
-- The project is pre-implementation. Do not claim that a DevTools client,
-  protocol, panel, trace, connection, or control operation exists.
+- Managed by the `bitty-core` commander (terminal-platform jurisdiction,
+  alongside `bitty` and `bitty-terminal-docs`).
+- The repository is past pre-implementation for its scoped surfaces: tracing
+  phases 1 and 2, inspect-only watch mode, and live-socket fixtures are
+  `Implemented` only, never `Verified`/`Compatible`. Do not claim capabilities
+  beyond merged code.
 - Product code requires an explicitly scoped task. Governance initialization
   does not authorize a frontend or protocol implementation.
 
@@ -101,7 +105,7 @@
 ## Workspace conventions
 
 - Run Git and CarryCtx inside this repository, never from the umbrella root.
-- Use this repository's `recording/` (gitignored), not system `/tmp/bitty/`, for durable scratch
-  material.
+- Ephemeral scratch goes under `/tmp/bitty/`; durable material goes under this
+  repository's `recording/` (gitignored).
 - Treat reference repositories and diagnostic captures as untrusted, read-only
   evidence unless a task explicitly authorizes an isolated experiment.

CHANGELOG.md

@@ -89,3 +89,16 @@ and this project adheres to no released version yet.
   Changelog entries, commitlint configuration
   ([commitlint.config.ts](./commitlint.config.ts)), and markdownlint-cli2
   configuration ([.markdownlint-cli2.jsonc](./.markdownlint-cli2.jsonc)).
+
+### Changed
+
+- **Trace accounting semantics documentation (CTX-0075, docs-only)**: README
+  now records the trace-helper semantics already implemented by CTX-0053/#117
+  and CTX-0054/#119 and clarified in `bitty-terminal-docs`
+  `specifications/devtools-rfc.md` (CTX-0026): retained redacted logical UTF-8
+  export-byte accounting (not heap/filesystem occupancy), independent
+  per-record normalization with a leading `U+FEFF` preserved as data, effective
+  `min(trace maxBytes, retention maxBytes)` rejection with one counted drop and
+  unchanged retained state, opaque raw append distinct from typed stream
+  coalescing, and `fetchTraceChunk` pagination on retained UTF-8 byte offsets.
+  No code behavior changed.

README.md

@@ -42,7 +42,7 @@ Core protocol contracts belong to
 `bitty-ui`). Canonical architecture, security, compatibility, and public
 behavior belong to
 [bitty-docs](https://github.com/bitty-terminal/bitty-docs) (accepted
-[DevTools RFC](https://github.com/bitty-terminal/bitty-docs/blob/main/docs/specifications/devtools-rfc.md)
+[DevTools RFC](https://github.com/bitty-terminal/bitty-terminal-docs/blob/main/specifications/devtools-rfc.md)
 OQ-019 and Performance Budgets OQ-001). Any future protocol change requires
 coordinated, explicitly ordered work in each owning repository.
 
@@ -159,6 +159,36 @@ Rust counterpart at `crates/devtools-client` mirrors the same contracts:
 `cargo test` `37` tests pass; `just check` green; `bun test` `62` tests
 pass. No `unsafe`, no PTY/GPU/window handle, no TCP, no ambient credential.
 
+## Trace accounting semantics (Implemented, CTX-0053 / CTX-0054)
+
+The trace helpers account **retained, redacted, logical UTF-8 export bytes** —
+the bytes that would be retained after typed redaction (serialized JSON for
+structured events, per-record UTF-8 normalization for raw records) — never heap
+or filesystem occupancy. This mirrors the client trace helper note in the
+accepted
+[DevTools RFC](https://github.com/bitty-terminal/bitty-terminal-docs/blob/main/specifications/devtools-rfc.md)
+(bitty-terminal-docs CTX-0026) and remains `Implemented` only.
+
+- **Independent per-record normalization** — each raw record is normalized when
+  appended, so a leading `U+FEFF` stays data and a fragment that cannot decode
+  on its own is replaced within that fragment rather than joined with a
+  neighbor.
+- **Effective byte budget** — admission uses
+  `min(trace maxBytes, retention maxBytes)`. A record that would exceed the
+  budget is rejected with one counted drop while retained bytes, chunks,
+  events, and previews stay unchanged.
+- **Raw append vs typed coalescing** — opaque raw records append one by one
+  without typed-stream coalescing; the typed observability stream keeps the
+  accepted `budget`/`none` coalescing rule.
+- **Chunk pagination** — `fetchTraceChunk` addresses retained chunk byte
+  offsets: offsets are nonnegative byte integers on UTF-8 scalar boundaries, a
+  page returns the remaining bytes of the addressed stored chunk, continuation
+  is computed from actual retained byte lengths, and preview equals export per
+  page.
+
+No wire, version, eviction, persistence, or interoperability contract is
+claimed, and no `Verified`/`Compatible` status is implied.
+
 ## Test-automation drivers (candidate, CTX-0024)
 
 `src/automation.ts` adds typed, fail-closed client bindings for the headless
@@ -168,7 +198,7 @@ split integration testing. The bindings target the `bitty` candidate methods
 `bitty.debug/frameHash` (serving dispatcher
 `crates/bitty-ipc/src/devtools.rs`, CTX-0188/CTX-0244); they remain
 `Candidate` here because the accepted
-[DevTools RFC](https://github.com/bitty-terminal/bitty-docs/blob/main/docs/specifications/devtools-rfc.md)
+[DevTools RFC](https://github.com/bitty-terminal/bitty-terminal-docs/blob/main/specifications/devtools-rfc.md)
 does not yet name these methods.
 
 - Bounded keyboard `keyDown`/`keyUp` and mouse `clickTrajectory` /
@@ -421,8 +451,8 @@ technical record remains
 
 Phase 2 extends phase 1 with live IPC and advanced tracing/control as
 experimental evidence for
-[DevTools RFC](https://github.com/bitty-terminal/bitty-docs/blob/main/docs/specifications/devtools-rfc.md)
-(OQ-019), [IPC and Agent RFC](https://github.com/bitty-terminal/bitty-docs/blob/main/docs/specifications/ipc-agent-rfc.md)
+[DevTools RFC](https://github.com/bitty-terminal/bitty-terminal-docs/blob/main/specifications/devtools-rfc.md)
+(OQ-019), [IPC and Agent RFC](https://github.com/bitty-terminal/bitty-ai-docs/blob/main/specifications/ipc-agent-rfc.md)
 (OQ-018), and budgets OQ-001. No installation procedure, supported API,
 compatibility guarantee, release, or distributable artifact is claimed until
 independent review and `Verified` lifecycle.

repo.toml

@@ -4,7 +4,7 @@ name = "bitty-devtools"
 kind = "tooling"
 lang = "ts/rust"
 role = "devtools protocol, automation, campaigns"
-owner = "TBD"
+owner = "bitty-core"
 docs = "bitty-docs"
 
 [contracts.consumes]