## Summary
Update the Docker-in-Docker and Node devcontainer features after both exact pinned releases completed the configured seven-day cooldown.
## Changes
- Update Docker-in-Docker from 4.1.2 to 4.1.3 and Node from 2.1.0 to 2.1.1.
- Keep each resolved reference and integrity digest in agreement.
## Testing
- Reviewed the lockfile diff, configured feature references, upstream changes, and published package digests.
- Fresh CI passed the live cooldown guard for both exact digests on October 14, 2026: Docker-in-Docker became eligible at 17:25:01 UTC and Node at 17:17:44 UTC.
- Typechecking and formatting passed in the same rerun. Earlier native, package, and cross-platform test jobs passed; required aggregate checks must pass before merge.
## Risk and rollout
Patch updates for development containers. The configured seven-day cooldown is satisfied without an override. No application runtime or public CLI changes.
## Public disclosure review
- [x] No customer, partner, prospect, or user identities, data, or identifying details are included.
- [x] No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
- [x] I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.
Update the GitHub CLI and Docker-in-Docker devcontainer features and their immutable digests.
Reviewed the upstream installer changes and verified the published manifest digests against the lockfile.
Administrator merge follows local validation and review while hosted CI is delayed by the GitHub Actions incident.
Use the multi-architecture Noble base and retain the Node.js, Python, Docker, and GitHub CLI development tooling.
Share the dependency installer with Ona, honor the repository pnpm pin through Corepack, and preserve the restricted Ubuntu APT refresh.