Updating shared notes to reflect verified public code retrieval

The situation

A shared note was found to be misleading as it conflated verified public code retrieval with an unverified signed-in account. The note was used by others and its inaccuracy could cause confusion. A successful public retrieval and a failed login attempt highlighted the need for correction. The existing note implied that the login warning was stale, which was not the case.

What they weighed

• Correct the existing note to reflect the distinction

  Chosen

• Leave the note as is, implying the login warning is stale

What they decided

Correct the existing note to reflect the distinction

Why

The current note was misleading and could mislead others. A successful public retrieval and a failed login attempt described different capabilities, which needed to be explicitly stated. Correcting the note would ensure that the distinction between public and signed-in access was clear.

The first step

Patch the existing note and index, then verify the changes and notify relevant parties

How they would know it worked

The note and index will be checked to ensure they match the observed capabilities and the correction will be confirmed with the relevant parties

How it turned out

Not known yet. The result is added here when it comes in.