Repository navigation
docs: add the phase 8a and 8b designs and implementation plans (#87) - #91
Merged
Merged
Conversation
File the conformance-kit and reference-transport designs and plans under docs/work/mvp/phase8/ and link them from the roadmap's phase 8 row.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #87.
Adds the phase 8 designs and implementation plans, filed under
docs/work/mvp/phase8/, and links them from the roadmap's phase 8 row. Documentation only; no code changes. Implementation is tracked by the phase 8 umbrella (#90) and its two sub-issues (8a: #88, 8b: #89); this PR does not close them.Each sub-phase went design → plan → independent validation of the plan against the design (findings verified before reporting, with scratch compile probes on SDK 10.0.401) → resolution of the verified findings. 8b's design was written after 8a's, which owns the phase segmentation.
TRANSPORTrows not listed for 8b, and all 22ASYNCrowsTRANSPORT-1,-4,-5,-6,-8,-9,-10,-12,-13,-14,-17,-18,-28,-30Key decisions
Dexpace.Sdk.Conformance: references onlyDexpace.Sdk.Core; 40 assertions, each with a negative control; the wire fixture promoted from the SystemNet tests; per-ID reporting, waivers by ID (8b's rows start asOwner = "8b"waivers, each deleted by the 8b PR that closes it). First published version: the first release's lockstep version, proposed0.1.0.DelegateHttpClientas well asSystemNetHttpClient.Dexpace.Sdk.Reactivenot built: no consumer exists;ASYNC-6/ASYNC-21vacuous for runtime facades.SystemNetHttpClientOptionsplus four constructors; a handler constructor that rejects a redirect-following handler; proxy installed on the owned client only, with no implicit environment read; a genuinely synchronousExecute;RequestOptions.Timeoutenforced; the caller'sContent-Typeauthoritative; anObjectDisposedExceptionlatch.Open for the lead
0.1.0).OperationCanceledException), P8b-9 (genuinely synchronousExecute), P8b-10, P8b-14 (1 MiB default limit), P8b-18 (theCallKeystamp moved to phase 9).Known caveats
ASYNC-2's rejecting-scheduler clause is not met today (AsAsyncthrowsTaskSchedulerExceptionsynchronously); the plan re-dispositions it rather than pinning it as met.Execute, enforced timeout, terminal internal cancellation, post-disposeObjectDisposedException,Content-Typeauthority) are listed in its design with migration lines.Housekeeping probe: no drift found.
scripts/knowledge verify-structure: OK.