cdk.context.json best practice

Could you clarify the best practice here regarding cdk.context.json and CI/CD? Should it be committed to source control? When deploying multiple environments to a single account via CI/CD, how does cdk.context.json get generated for, say, prod environment and committed to source control when synth may only be happening for prod via CI/CD server?

No file or test is named. Start by reviewing the repository's CDK and CI/CD guidance alongside the cdk.context.json question, then establish the recommended source-control and multi-environment workflow. Done means the documentation clearly explains whether the file is committed and how production context is generated.

Written by the indexing model from the issue text.