Summary
Defer Inferno SMART App Launch conformance testing to a dedicated follow-up. HAIStack will continue to provide library-level SMART/auth support (pkg/smart, pkg/auth, pkg/http hooks); Inferno CI and a reference OAuth host are out of scope until hosts have a clearer SMART deployment story.
Background
Issue #8 Phase 5 proposed optional Inferno SMART App Launch tests against a reference pkg/http deployment. An initial implementation added:
cmd/inferno-reference + pkg/smart/host (stub OAuth + well-known)
pkg/testkit/infernotest (discovery-aligned Go tests)
.github/workflows/inferno.yml
That work was removed to avoid maintaining stub OAuth endpoints and partial conformance claims before the primary authorization test kit (#8 / pkg/testkit/authztest) lands on main.
Proposed scope (when picked up)
Phase 1 — Discovery
Phase 2 — Launch workflows
Phase 3 — Integration with HAIStack
Out of scope
- Building a production OAuth2/OIDC authorization server in HAIStack
- Replacing
pkg/testkit/authztest with Inferno (complementary: semantic authz vs ecosystem conformance)
Related
References
Summary
Defer Inferno SMART App Launch conformance testing to a dedicated follow-up. HAIStack will continue to provide library-level SMART/auth support (
pkg/smart,pkg/auth,pkg/httphooks); Inferno CI and a reference OAuth host are out of scope until hosts have a clearer SMART deployment story.Background
Issue #8 Phase 5 proposed optional Inferno SMART App Launch tests against a reference
pkg/httpdeployment. An initial implementation added:cmd/inferno-reference+pkg/smart/host(stub OAuth + well-known)pkg/testkit/infernotest(discovery-aligned Go tests).github/workflows/inferno.ymlThat work was removed to avoid maintaining stub OAuth endpoints and partial conformance claims before the primary authorization test kit (#8 /
pkg/testkit/authztest) lands on main.Proposed scope (when picked up)
Phase 1 — Discovery
/.well-known/smart-configuration(host-owned, not necessarily in-tree stub OAuth)smart_discovery_stu2group (well-known endpoint + required capabilities)Phase 2 — Launch workflows
system/*.read+ client assertion)Phase 3 — Integration with HAIStack
PrincipalResolver+AuthCheckerfor Inferno-tested deploymentspkg/testkit/authztestsemantic scenarios (policy deny overrides scope)Out of scope
pkg/testkit/authztestwith Inferno (complementary: semantic authz vs ecosystem conformance)Related
References