docs: adopt manual server deployment

docs/decisions/0003-consume-licensed-font-from-frontend.md

@@ -16,7 +16,7 @@ The deployment repository must not duplicate application assets or introduce a s
 
 Treat both files as ordinary frontend-owned build inputs. Frontend CI builds them through the normal frontend context and the immutable frontend image contains the emitted font resource. Deployment consumes only that normal frontend image/build context.
 
-Platform Operations does not create a separate asset-injection path, copy either file into deployment Git, or maintain font-specific credentials. Release provenance is the frontend Git SHA and immutable frontend image digest.
+Platform Operations does not create a separate asset-injection path, copy either file into deployment Git, or maintain font-specific credentials. Release provenance is the recorded frontend Git commit and the local image built from that checkout.
 
 Frontend CI and deployment smoke checks must fail if the required source inputs are absent, the built resource is absent, or the resource is not served with the expected font MIME type. The deployment repository records no second binary or license copy.
 
@@ -42,6 +42,6 @@ Frontend CI and deployment smoke checks must fail if the required source inputs
 
 - Frontend commit `64f5ac2` is the first approved provenance point for the tracked assets.
 - Frontend repository policy and license compliance govern changes to the files.
-- Deployment rollback automatically rolls font output back with the selected frontend image digest.
+- Deployment rollback restores the recorded frontend commit and rebuilds its font output through the normal context.
 - No separate font injection workflow, font-specific deployment secret, or deployment-repository font copy is allowed.
 - Platform smoke tests verify the emitted resource without reading or reproducing the license text.