Parent DOX: HTTPS.
- Expose HTTPS policy and certificate management through ordinary programs.
- Own program manifests and argument boundaries. Shared policy and lifecycle
stay in
../src/.
- Configuration reads require
the8020.https.configuration.view; writes use the owning API's permission. Snapshots contain public certificate material and secret references only. - Certificate commands receive private keys only through execution-scoped secure input. Never return keys or put them in positional arguments or job history.
- Upload uses
--key-file; one-time deployment import uses--state-file. Both use generic command secure-file inputs. Import returns only completion status and leaves local listener publication to the startup owner. - Challenge lookup validates the kind and delegates to the exact shared lookup. Native ingress invokes it as system; it creates no independent service.
- Challenge's fourth boolean argument requests local lookup only, preventing loops when separate systems share a configured public challenge endpoint.
- Snapshot initialization ensures the single package maintenance schedule. Issue/renew and scheduled maintenance share the same fenced operation API. Issuance reports local application separately from successful storage.
secret-usagesimplements thethe8020/secretsusage contract for the ACME account, local certificate authority, certificate version and pending order keys, so their secrets cannot be deleted from the Secrets screen.
- Keep program entrypoints small and reuse package-owned semantic fields and ordinary command helpers.
- Run
deno task checkanddeno task testfrom the package root.
- https/AGENTS.md: Own discoverable configuration, certificate uploads/details, and advanced HTTPS screens.