While it's expected that users will usually let xcengine handle the stage-out catalogue, there should be an option (both for technical users with particular needs and for development and testing) for the notebook to do this itself. The simplest implementation would simply be for xcengine to skip writing its own STAC stage-out data if it detects a pre-existing (i.e. created by the user code) catalog.json in the CWD.
While it's expected that users will usually let xcengine handle the stage-out catalogue, there should be an option (both for technical users with particular needs and for development and testing) for the notebook to do this itself. The simplest implementation would simply be for xcengine to skip writing its own STAC stage-out data if it detects a pre-existing (i.e. created by the user code)
catalog.jsonin the CWD.