Angular learning path execution

The complete guide workflow passed from a fresh Linux checkout of 270aef0b62e4f1298f1fb8520a2522cd6d604832. The source includes all three registered TypeScript excerpts. The maintained builder produced two separately observed Angular packages; the signed fixture export and real-node/browser workflow then passed without replacing the node or browser with test doubles.

The unaltered receipt has SHA-256 1e5f17edbf34e86892a13744541ef4ac99bdbf510b571349387f51abd7eaf395. It records the exact CLI, node, compiler, Node.js, Chromium, source snapshot, build observation, component, publication and immutable asset identities. Chromium 153.0.8010.52 and Node.js 24.19.0 exercised public pages, anonymous HTTP 401, distinct Alice/Bob sessions, original DOM reuse, client navigation and interactive counters over actual shared ingress.

Allowed/denied provider calls, cancelled held work and recovery, canary promotion, revocation, same-port restart, authenticated native-cache hits and rollback all passed. Three node incarnations and the provider peer stopped and were reaped; 122 CLI processes completed and temporary outputs were removed. Final active/queued activations and reserved fuel/memory were zero.

This was bounded execution on the shared Docker Desktop Linux host. Reproducibility remains not-checked and dependency completeness remains declared-inputs-incomplete. The receipt does not close the broader resource campaign or substitute for the required human newcomer review.

Reproduce the build, fixture and workflow with the commands in Build and deliver Angular.