feat(stabilization)!: bytesbuf_io 1.0

[martintmk]

Summary

Adds pending stabilization notes for the bytesbuf_io crate based on O365 Core work item 7688115. The notes record the proposed owned-buffer I/O boundary, current and proposed trait requirements, read and write semantics, ecosystem adapter strategy, and unresolved review items. Also adds an empty docs/DESIGN.md placeholder.

Validation

• just package=bytesbuf_io format
• just package=bytesbuf_io readme
• cargo check -p bytesbuf_io --all-features
• cargo build -p bytesbuf_io --all-features
• cargo test -p bytesbuf_io --all-features
• git diff --check
• GitHub required checks passed, including repository spellcheck and CodeQL.
• Codecov reports 100% project and patch coverage.
• Multi-model review completed with no unresolved findings.

Local spellcheck was attempted, but the installed cargo-spellcheck process exits during startup on this machine. The GitHub spell-check job passed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (d799037) to head (5553dbe).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #644   +/-   ##
=======================================
  Coverage   100.0%   100.0%           
=======================================
  Files         473      473           
  Lines       45493    45493           
=======================================
  Hits        45493    45493           

Flag	Coverage Δ
linux	?
linux-arm	?
scheduled	?
windows	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[martintmk]

Posted by an AI agent

Two non-blocking stabilization-documentation findings remain.

Coverage: Complete current-head review covered API design, correctness, tests, performance, naming, telemetry, resilience, consistency, public API, and public documentation. This is a documentation-only change; the package build passed and no runtime or test behavior changed.

Vote: Not requested because the authenticated reviewer owns this PR.

[martintmk]

Posted by an AI agent · Non-blocking

The stable error boundary does not cover recovery classification

Problem
The stabilization decisions cover the associated error type and wrapper composition, but do not decide whether transient/unavailable classifications and retry-delay hints must survive conversion into the crate error.

Why this matters
Once the traits stabilize, adding a required recovery contract can become a breaking change, while callers cannot reliably drive retries or circuit breakers if wrapping erases that information.

Suggested fix
Add recovery classification and preservation to the error-boundary checklist, including an explicit decision if this lower-level crate intentionally leaves classification to adapters.

[martintmk]

Posted by an AI agent · Non-blocking

The arty_io review dependency is not identifiable

Problem
The pending checklist requires review against arty_io, but that identifier has no definition or link in this repository.

Why this matters
A future stabilizer cannot determine which consumer and requirements must be checked before completing this item.

Suggested fix
Use the canonical project/package name and add a reference or short identifying description.