chore: refresh SEP traceability manifest after SEP-2322 (#188)#301
Merged
Conversation
Regenerated from a client+server suite run against typescript-sdk@5fc42e9be115 following the recipe in .github/workflows/traceability.yml. New entries since the last refresh (typescript-sdk@22595b96): - SEP-2322 (MRTR, #188): 17 tested, 0 untested, 16 excluded, 3 untracked - SEP-2549 (TTL for list results, #275): 7 tested, 0 untested, 13 excluded - SEP-2260: 12 excluded rows, no checks - SEP-2207: yaml rows added since the last refresh now appear (1 tested, 1 untested: sep-2207-server-no-offline-access) No previously-tested requirement regressed.
commit: |
…os exist sep-2207-server-no-offline-access was declared in the yaml but no scenario emits it, so it surfaced as the only untested requirement in the refreshed manifest. The check needs to probe the SDK server's Protected Resource Metadata scopes_supported and WWW-Authenticate challenge scope, and the server suite does not yet exercise the SDK server as an OAuth protected resource at all. Mark the requirement excluded with a pointer to #116 (server-side authorization baseline) rather than leaving it as a permanently-untested row; revisit when server-side authorization scenarios land.
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
1 participant
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.
Regenerated
src/seps/traceability.jsonfrom a client+server suite run againsttypescript-sdk@5fc42e9be115, following the recipe in.github/workflows/traceability.yml.What changed
All other SEPs are unchanged; no previously-tested requirement regressed.
sourcemoves fromtypescript-sdk@22595b96totypescript-sdk@5fc42e9be115.Notes
untrackedIDs (multi-round-r1,multiple-inputs-incomplete,non-tool-incomplete) are flow gates that fired in round 1; the remaining round-2 gate checks (*-complete,multi-round-r2/r3) were not emitted because typescript-sdk's conformance server does not implement the MRTR test tools yet — they will appear inuntrackedonce it does.sep-2207-server-no-offline-accessshows asuntested— pre-existing drift from a yaml update that landed after the last manifest refresh, not introduced by this run.testedstatus, which only records that a scenario emitted the check ID.