[richlander]

dotnet-inspect builds robust, capable inspection features that provide
foundational capabilities or compelling experiences and are conventionally
sound, delightfully new or unique, or both.

Summary

• keep compact Type MemberGroups as Inspect Web's default least-work content
• add explicit exact-Member and documented-Member content backed by the shared
  Type document and documentation-composition operations
• preserve shared declaration identity, ordering, Share, diagnostics, and
  source-owned documentation capability across Package, Platform, and uploaded
  Library roots
• retain existing exact-Member transitions through Browser-owned
  declaration-token selector enrichment without giving the Browser population
  or ordering authority
• keep documentation and selector failures visible without removing
  declarations or substituting a success-shaped fallback

Design basis

Normative owner:
docs/design/inspect-web-subject-overview.md#owner-and-claim — Inspect Web owns
the Browser presentation grammar while exact/documented Member content consumes
the shared Type document operations only when explicitly selected.

Supporting owners:

• docs/design/type-member-inspection-documents.md owns exact declaration
  identity, population order, and documentation attachment correspondence.
• docs/design/cli-verbosity-retirement.md owns content-defined composition and
  the rule that optional documentation work requires explicit demand.

Validation

• canonical Inspect Web facade --check, including Browser/Wasm production
  publish
• canonical facade digest verification
• BrowserMemberDeclarationTests: 7 passed
• authored TypeScript type-check
• focused Type panel and ordinary Worker tests: 102 passed
• focused Member composition tests: 3 passed
• Inspect Web lint
• Inspect Web production build and site-artifact verification
• Markdown lint
• git diff --check

ProductionFacadeContextTests remains red for two failures already present at
the branch's starting head 6a68984f2d60027de0f79c187e3fe6e5dc22f73f:
the pre-existing TypeSignaturePresentation wire-type ownership violation and
the pre-existing unlisted FindIndexedTypes export. This change adds the three
new Type-document exports to that gate's expected partition; the canonical
facade generation and production publish pass.

Closes #10808

[richlander]

Round 1 review model substitution: GPT-6 Astra is not advertised by the active agent harness, so the single fixed-head review seat will use the approved non-Fast GPT-6 Sol model for this cross-layer Browser adoption. Candidate remains locked at 198fc76b1df5fa89d97332c14641ad14a940d4e9 over base 6a68984f2d60027de0f79c187e3fe6e5dc22f73f.

Authored by Copilot.

[richlander]

dotnet-inspect builds robust, capable inspection features that provide foundational capabilities or compelling experiences and are conventionally sound, delightfully new or unique, or both.

Round 1 is complete for PR 10903.

• Theme: Converge matching CLI and Inspect Web sections on shared host-neutral operations while retaining thin host-owned presentation and navigation.
• Review model GPT-6 Sol was used for adversarial review.
• Design basis: normative owner docs/design/inspect-web-subject-overview.md#type-composition — explicit exact/documented Member content consumes shared Type document operations while compact groups remain default and Browser selector enrichment preserves exact navigation; supporting docs/design/type-member-inspection-documents.md owns declaration identity/order and documentation correspondence, and docs/design/cli-verbosity-retirement.md owns explicit-demand composition.
• Review feedback is: diverging.
• Round start: 2026-10-30T00:12:50Z.
• Round end: 2026-10-30T00:15:19Z.
• Round duration: 0:02

Progress: 1 pushed candidate, 1 usable review, 1 accepted finding.
Reviews: 0/1 clean — GPT-6 Sol found one blocking exact-navigation defect.
Recommendation: continue.

Resolution: accepted. Exact rows in the navigation pane carry only an overload index, while the click handler resolves that index against the previously selected group. Immediately after choosing exact/documented content no group is selected, so the first click is inert; a later cross-group click can target the wrong declaration. Reproduced on exact head 198fc76b1df5fa89d97332c14641ad14a940d4e9 through type-panel.ts binding/rendering and dotnet-inspect.ts selection state. Round 2 will carry the row group key through the typed binding, select that group before its overload, and add focused cross-group activation coverage.

Authored by Copilot.

[richlander]

dotnet-inspect builds robust, capable inspection features that provide foundational capabilities or compelling experiences and are conventionally sound, delightfully new or unique, or both.

Round 2 is complete for PR 10903.

• Theme: Converge matching CLI and Inspect Web sections on shared host-neutral operations while retaining thin host-owned presentation and navigation.
• Review model GPT-6 Sol was used for adversarial review.
• Design basis: normative owner docs/design/inspect-web-subject-overview.md#type-composition — explicit exact/documented Member content consumes shared Type document operations while compact groups, filters, and Browser exact navigation remain available; supporting docs/design/type-member-inspection-documents.md owns declaration identity/order and documentation correspondence, and docs/design/cli-verbosity-retirement.md owns explicit-demand composition.
• Review feedback is: diverging.
• Round start: 2026-10-30T00:28:02Z.
• Round end: 2026-10-30T00:33:23Z.
• Round duration: 0:05

Progress: 2 pushed candidates, 2 usable reviews, 2 accepted findings.
Reviews: 0/1 clean — GPT-6 Sol confirmed the round 1 navigation repair, then found one blocking failed-request recovery defect.
Recommendation: continue.

Resolution: round 1 is resolved. The round 2 finding is accepted: Member navigation has four explicit grid rows, but failure status, filter disclosure, and declaration list become three separate children after the fixed heading/back rows. The declaration list enters an implicit auto row and a populated list collapses the filter disclosure track. Reproduced on exact head 0be82295373142ef4490ea829c88fa717a4658f2 in headless Chromium: with 30 declaration rows, the filter details box was 1px high and hit-testing its 30px summary returned Declaration 0. Round 3 will wrap status and filters as one controls-row child, add DOM/layout structure coverage, and retain the scrollable declaration list in the final minmax(0, 1fr) row.

Authored by Copilot.

[richlander]

Round 3 accepted two blocking correctness findings at exact head
78302a76b865a768bc698e696a5b0b72f6ba1d70.

1. A Package or Platform documentation-provider exception escapes the shared
   attachment composition. The Browser has already cleared the prior document,
   so documented content retains only the request error and loses the completed
   exact declarations. Exact-head reproduction reported retainedRows: 0
   after a documentation timeout.
2. Plain exact-Member groups are reconstructed from the Type document on each
   render. Member Overview mutates one transient overload with its successfully
   loaded documentation, but the next projection recreates that overload with
   summary: null and documentationLoaded: false. Exact-head reproduction
   observed the loaded summary become null.

The round 1 group-aware exact-row selection repair remains resolved. The round
2 controls-row/failure-recovery layout repair also remains resolved.

The next candidate will preserve a completed Type document beside a failed
optional documentation outcome and retain exact-Member detail documentation in
a stable declaration-keyed state across Type-document projections.

Round 3 is complete for PR 10903.

• Theme: Shared section convergence moves exact and documented Type Member semantics behind host-neutral operations while retaining Browser-owned presentation and navigation.
• Review model GPT-6 Sol was used for adversarial review.
• Design basis: normative owner docs/design/inspect-web-subject-overview.md#owner-and-claim — compact MemberGroups remain the least-work default while explicit exact/documented content consumes shared Type document operations without surrendering declaration identity, order, or visible failure; supporting docs/design/type-member-inspection-documents.md#owner-and-exact-claim owns declaration/attachment correspondence and docs/design/cli-verbosity-retirement.md#content-defined-sections owns explicit documentation demand and shared CLI/Browser semantics.
• Review feedback is: diverging.
• Round start: 2026-10-30T00:48:41Z.
• Round end: 2026-10-30T00:51:36Z.
• Round duration: 00:03.

Progress: 3 pushed candidates, 3 usable reviews, 4 accepted findings.
Reviews: 0/1 clean — GPT-6 Sol confirmed both prior repairs and found two reproducible documentation-retention defects.
Recommendation: continue.

Resolution: exact-head probes accepted both findings. Round 4 will preserve completed rows when optional documentation acquisition fails and keep selected exact-Member documentation stable across repeated Type-document group projection.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 4 conflict recovery merged live main tip 527db69d593918fe056aa38f6307239a17aa06db into the PR branch and pushed merge commit 21f3308d29b0cdb644aa29478e89834d6771f453. The only conflict was the closed Worker-operation count: main added one operation while this PR adds three, so the merged catalog count is 145. Round 4 repair work continues on this recovered base.\n\n_{Authored with GitHub Copilot CLI.}

[richlander]

Round 4 candidate 3ceabba9b917f29f413a5a6cca920303f198505f
repairs both accepted round 3 documentation-retention findings.

1. Optional documentation-provider exceptions now settle as a typed
   ProviderFailed attachment outcome beside the completed Type document.
   Package and Platform documented content therefore retain every exact
   declaration, while the Browser and CLI surface the provider detail.
   Caller-requested cancellation still propagates.
2. Exact-Member detail documentation now retains its settled outcome in stable
   request state and rehydrates replacement Type-document projections with the
   same full declaration key. Re-rendering no longer discards successfully
   loaded summaries, returns, exceptions, or documentationLoaded.

Focused validation passed:

• shared Type-document operation tests: 12/12;
• managed Browser Member declaration tests: 7/7;
• Member-detail and ordinary Worker tests: 83/83;
• focused Member composition assertions;
• affected CLI Release build;
• Inspect Web authored type-check, lint, production build, and artifact check;
• canonical Browser/Wasm facade --check and digest verification;
• git diff --check.

The complete composition file still reports two stale Package Dependency
assertions. The exact same source and assertions are present at merged
main 527db69d593918fe056aa38f6307239a17aa06db: the test expects six
renderPackageDependenciesSurface calls while that function contains seven,
and its graph-viewer HTML regex expects a removed
declarationFailureNotice. They are unrelated to this Member documentation
repair.

The live-base conflict probe is clean against
527db69d593918fe056aa38f6307239a17aa06db. Current-head ci-required is
running before fixed-head round 4 review.

_{Authored with GitHub Copilot CLI.}

[richlander]

Documented exact Members

System.Text.Json 10.0.13 on the recovered PR head
c73de5e8620eb7229fc144328c077e648a5d3de8.

The Member content selector is set to documented members. The navigation
pane shows all 104 exact declarations with their summaries, while the selected
overload presents its exact declaration, stable identity, summary, parameters,
return documentation, and documented exceptions.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 4 accepted one blocking correctness finding at exact head
c73de5e8620eb7229fc144328c077e648a5d3de8.

The Package Type-document cache key omits the selected runtime identifier even
though the managed exact/documented request receives that RID. A supported
Package RID switch therefore can retain the same key, and reopening the same
Type can reuse the previous RID's exact/documented result without issuing the
new request.

Exact-head reproduction evaluated the production key for the same Package,
framework, assembly, Type, spelling, accessibility, and documented content:

• linux-x64 key: unchanged;
• win-x64 key: unchanged;
• request argument: changes from linux-x64 to win-x64.

The finding is accepted. Round 5 will add the runtime identifier to the
Type-document request key and gate distinct RID keys/request execution.

All four prior finding occurrences are resolved:

1. exact-row navigation resolves the clicked group before overload selection;
2. failure recovery keeps status and filters in one controls row before the
   scrollable declaration list;
3. documentation-provider exceptions preserve the completed declaration
   document as typed ProviderFailed;
4. matching replacement projections rehydrate settled exact-Member
   documentation from stable request state.

Round 4 is complete for PR 10903.

• Theme: Shared section convergence moves exact and documented Type Member semantics behind host-neutral operations while retaining Browser-owned presentation and navigation.
• Review model GPT-6 Sol was used for adversarial review.
• Design basis: normative owner docs/design/inspect-web-subject-overview.md#owner-and-claim — compact MemberGroups remain the least-work default while explicit exact/documented content consumes shared Type document operations without redefining source identity or documentation outcomes; supporting docs/design/type-member-inspection-documents.md#owner-and-exact-claim owns declaration/attachment correspondence, docs/design/cli-verbosity-retirement.md#content-defined-sections owns explicit documentation demand and shared CLI/Browser semantics, and docs/evidence-and-validation.md#demand-shaped-execution supplies the least-work review lens.
• Review feedback is: diverging.
• Round start: 2026-10-30T03:40:48Z.
• Round end: 2026-10-30T03:44:38Z.
• Round duration: 00:04.

Progress: 5 pushed candidates, 4 usable reviews, 5 accepted findings.
Reviews: 0/1 clean — GPT-6 Sol resolved all four prior findings and found one reproducible Package RID cache-key defect.
Recommendation: continue.

Resolution: exact-head reproduction accepted the RID collision. Round 5 will
make the Type-document key source-complete by including the Package runtime
identifier and add a focused regression gate.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 5 candidate eb5a94e364aacb996ce2983cf213d421cc9d01e0
repairs the accepted Package RID cache-key defect.

Both Type Member source-dependent keys now include the selected Package runtime
identifier:

• the exact/documented Type-document key;
• the rich exact-Member population fallback key used for Browser selector
  enrichment.

The latter uses the same RID-specific managed request and therefore had the
same source-coordinate requirement. Package, framework, assembly, Type,
spelling, accessibility, content/source, and RID now all participate in cache
identity.

Focused evidence:

• exact-head probe: linux-x64 and win-x64 now produce distinct population
  and document keys;
• Member content composition gate passes and requires RID in both keys;
• authored TypeScript type-check passes;
• Inspect Web lint passes;
• production frontend build and site-artifact verification pass;
• git diff --check passes;
• live-base conflict probe is clean against
  bad102273d5c2862be15bba6651c13ce2cffdad4.

Current-head ci-required must pass before the fixed-head round 5 review.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 5 accepted one blocking correctness finding at exact head
eb5a94e364aacb996ce2983cf213d421cc9d01e0.

When exact Member content is retained across a same-session link restoration to
another Type, the retained Type document still belongs to the previous Type.
Both canonical validation and deep-link selection derive identity from
memberGroups(requestedType), which intentionally projects no ordinary exact
groups until the destination Type document arrives. Those paths run before
loadSelectionData(), so an existing destination declaration can be rejected
as “The shared member is no longer available.”

An exact-head in-memory probe evaluated the authored
declaredMemberGroups(), memberGroups(), and
canonicalViewRestorationFailure() implementations with:

• exact members content retained;
• a real destination Type declaration and matching Member anchor;
• the destination Type document still pending;
• ordinary shared-document population selected.

The result was The shared member is no longer available. Inspection of the
same authored restoration path confirmed validation precedes
loadSelectionData().

The finding is accepted. Round 6 will preserve exact Member identity during
restoration independently of whether the destination Type document has
finished loading, with a focused same-session cross-Type restoration gate.

All five prior finding occurrences are resolved:

1. exact-row navigation resolves the clicked group before overload selection;
2. failure recovery keeps status and filters in one controls row before the
   scrollable declaration list;
3. documentation-provider exceptions preserve the completed declaration
   document as typed ProviderFailed;
4. matching replacement projections rehydrate settled exact-Member
   documentation from stable request state;
5. Type-document and rich-population keys include the Package runtime
   identifier supplied to their managed requests.

Round 5 is complete for PR 10903.

• Theme: Shared section convergence moves exact and documented Type Member semantics behind host-neutral operations while retaining Browser-owned presentation and navigation.
• Review model GPT-6 Sol was used for adversarial review.
• Design basis: normative owner docs/design/inspect-web-subject-overview.md#owner-and-claim — compact MemberGroups remain the least-work default while explicit exact/documented content consumes shared Type document operations without redefining source identity or exact-Member transitions; supporting docs/design/type-member-inspection-documents.md#owner-and-exact-claim owns declaration identity and attachment correspondence, docs/design/cli-verbosity-retirement.md#content-defined-sections owns explicit documentation demand and shared CLI/Browser semantics, and docs/evidence-and-validation.md#demand-shaped-execution supplies the least-work review lens.
• Review feedback is: diverging.
• Round start: 2026-10-30T03:58:53Z.
• Round end: 2026-10-30T04:03:35Z.
• Round duration: 00:05.

Progress: 6 pushed candidates, 5 usable reviews, 6 accepted findings.
Reviews: 0/1 clean — GPT-6 Sol resolved all five prior findings and found one reproducible exact-Member restoration defect.
Recommendation: continue.

Resolution: exact-head reproduction accepted the premature identity-validation
failure. Round 6 will decouple restoration identity from the not-yet-loaded
destination exact-content projection and add a focused regression gate.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 6 candidate: f0b037caf70ed5ae553c1f0472803c15117b51c9.

This candidate repairs the accepted exact-Member restoration defect from
Round 5.

• portable Member validation now uses resident declaration identity rather
  than the selected exact-content projection;
• when the destination shared Type document is not yet loaded, restoration
  retains the portable anchor instead of selecting by a provisional overload
  index;
• after the shared document settles, the retained anchor is rebound to the
  matching exact row before Member section loading continues;
• stale pending restoration is discarded when Package, Type, population
  intent, or Content changes.

Focused evidence:

• the exact-head reproduction now returns no canonical restoration failure for
  an existing destination declaration while its Type document is pending;
• the focused Member content gate proves that pending identity remains
  available and that the loaded exact row is selected by anchor;
• all 64 workspace-navigation tests pass;
• authored TypeScript type-check passes;
• Inspect Web lint passes;
• the production frontend build and artifact verification pass;
• git diff --check passes.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 6 conflict recovery: 212512ad0d0b0a3e12b9595ce0a9b77ad2d7492f.

Live main moved to fcc3608477b54b99711579fccae5219227eefc66
before Round 6 received a usable review. The candidate conflicted in the
canonical facade digest and Worker operation inventory, so the pending
candidate was superseded and the effective base was merged immediately.

The recovery:

• preserves both landed and PR-owned Worker operations, for 149 distinct
  ordinary operation kinds;
• regenerates the combined canonical Browser facade sources and digest;
• adds the landed Package exports to the exhaustive production partition,
  whose merged total is 181;
• replaces a product-owned Type signature presentation object on the Metadata
  wire with an assembly-local Browser transport record.

Validation on the recovered head:

• 95 focused Worker and workspace-navigation tests pass;
• the focused pending exact-Member restoration gate passes;
• six production facade and Type dependency boundary tests pass;
• authored TypeScript type-check and Inspect Web lint pass;
• the production frontend build and artifact verification pass;
• all changed Markdown passes markdownlint-cli;
• git diff --check passes.

Round 6 remains pending. Current-head CI must pass again before the fixed-head
review can begin.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 6 recovered candidate: 88d34f9d0aa8a7336bb39b02cf8b2a4f11ff83ed.

The first conflict-recovery head failed the fast facade digest gate because
the combined Metadata wire fix had not been regenerated into the checked-in
canonical facade. The candidate was superseded before review.

The canonical eight-facade generator now records the assembly-local
BrowserTypeSignaturePresentation contract and its exact digest.

Validation:

• canonical Browser/Wasm facade generation succeeds with the worktree-local
  .NET 11 RC SDK;
• --verify-digest confirms all eight facade sources match the manifest;
• authored TypeScript type-check, Inspect Web lint, production build, and
  artifact verification pass;
• six production facade and Type dependency boundary tests pass.

Round 6 remains pending current-head CI and fixed-head review.

_{Authored with GitHub Copilot CLI.}

[richlander]

Round 6 accepted one blocking correctness finding at exact head
88d34f9d0aa8a7336bb39b02cf8b2a4f11ff83ed.

When a Type's private exact-Member document is already loaded, restoring a
canonical link to a public Member of that same Type validates the link before
applying its public accessibility intent. portableMemberMatches() prefers the
currently loaded exact document over resident declaration identities, so the
public Member can be rejected as "The shared member is no longer available."

An exact-source VM probe evaluated the authored portableMemberGroups(),
portableMemberMatches(), and canonicalViewRestorationFailure() functions
with:

• a resident public declaration matching the link's exact anchor;
• a loaded private exact document for the same Type that does not contain that
  public declaration; and
• canonical validation running before the link's accessibility filter is
  applied.

The loaded-private case returned
The shared member is no longer available. The otherwise identical
pending-document case returned no failure, confirming that stale projection
readiness changes portable identity validation.

The finding is accepted. If another review block is approved, Round 7 will
validate portable identity against resident declarations independently of the
currently loaded exact projection, retain the existing post-load exact-row
rebinding, and add a focused same-Type private-to-public restoration gate.

All six prior finding occurrences are resolved:

1. exact-row navigation resolves the clicked group before overload selection;
2. failure recovery keeps status and filters ahead of the scrollable
   declaration list;
3. documentation-provider exceptions preserve the completed declaration
   document as typed ProviderFailed;
4. matching replacement projections rehydrate settled exact-Member
   documentation from stable request state;
5. Type-document and rich-population keys include the Package runtime
   identifier supplied to their managed requests; and
6. cross-Type restoration retains resident identity while the destination
   document is pending and rebinds the anchor after that document loads.

The six-round boundary snapshot remains eligible for an operator decision:
current-head ci-required is successful, GitHub reports the PR mergeable and
clean, the live main tip remains
fcc3608477b54b99711579fccae5219227eefc66, and there are no unresolved review
threads. The review-clean label remains absent.

Round 6 is complete for PR 10903.

• Theme: Shared section convergence moves exact and documented Type Member semantics behind host-neutral operations while retaining Browser-owned presentation and navigation.
• Review model GPT-6 Sol was used for adversarial review.
• Design basis: normative owner docs/design/inspect-web-subject-overview.md#owner-and-claim — compact MemberGroups remain the least-work default while explicit exact/documented content consumes shared Type document operations without letting Browser projection state redefine declaration identity; supporting docs/design/type-member-inspection-documents.md#owner-and-exact-claim owns exact declaration identity and documentation attachment correspondence, docs/design/cli-verbosity-retirement.md#content-defined-sections owns the distinct group, exact-Member, and documented-Member questions, and docs/evidence-and-validation.md#demand-shaped-execution supplies the least-work review lens.
• Review feedback is: diverging.
• Round start: 2026-10-30T04:51:59Z.
• Round end: 2026-10-30T04:56:23Z.
• Round duration: 00:04.

Progress: 9 pushed candidates, 6 usable reviews, 7 accepted findings.
Reviews: 0/1 clean — GPT-6 Sol resolved all six prior finding occurrences and found one reproducible same-Type accessibility-restoration defect.
Recommendation: approve next rounds.

Resolution: exact-head reproduction accepted the projection-dependent identity
failure. At the six-round boundary, no repair or Round 7 review will begin
without operator approval for another block.

_{Authored with GitHub Copilot CLI.}