Repository navigation
feat: add native API container provider and service definition (#617) - #618
Conversation
|
Current verify and PR-template validation pass. Hold integration on #620: the base-owned AGPL authorization check cannot find .github/approved-committers.json at exact cordis base 72e410a. Existing legacy policy blob b1a687db754ee2fac141919e6c63052d12bf2812 already lists adrianwebb. Its separately reviewed exact-byte restoration/trusted first admission is proposed, not performed; feature-head data cannot authorize itself. |
|
Review complete for the bounded container slice at fecbaf0. Native declaration/service projection and program tests are consistent; current owner verification (3 tests), normal base-owned authorization and metadata validation pass. Includes unchanged restored policy and durable documentation links. The HTTP missing-application regression is scoped to the separate #619 server slice and must pass there before integration. Merging this container slice into cordis under the maintainer's explicit instruction; #617 and #620 remain open. |
Outcome
Add the API-owned native Cordis container provider and bounded generated service definition. The server root is the separately reviewed #619.
Work authority
Contributor mode:
Plan
Owner documentation → outside-in built-program tests → native class provider → owner and installed verification → review and cordis integration.
Changes and commits
Public container provider, native provide/inject fields and exact owner-generated service metadata. Includes restored cordis policy without modifying its approved identities. README links survive task-branch cleanup. Runtime server/authentication routes remain in #619.
Verification
Risk and rollback
The qualified profile is Ubuntu 26.04 x64/local Unix Docker. No production or legacy service changes. Revert through a new reviewed issue-linked cordis PR if necessary. Test cleanup validates fixture installation labels before removing its resources.
Completion summary
Container slice reviewed; current CI passes against the restored trusted base. #621 restored exactly the already-approved policy blob b1a687db754ee2fac141919e6c63052d12bf2812. This runtime PR passes normal admission and uses no bootstrap exception. The server follow-up and parent installed gate remain separate. Issues remain open until release.
Submission checklist
Part of #617