Instead of reading the extension parameters from run-scheduled-docs.ts, it reads it from an external config.yml file that is distributed with the extension.
The default is now to store scheduled-docs yaml options in _schedule.yml instead of _quarto.yml. This is to separate the look of the website from the scheduling and to break what would be a very long file (for a complex website) into two smaller, specialized ones. If, at a later date, it'd be advantageous to made the _schedule.yml available as project-level metadata, that file can be added to _quarto.yml using metadata-files: _schedule.yml.
run-scheduled-docs.ts, it reads it from an externalconfig.ymlfile that is distributed with the extension.scheduled-docsyaml options in_schedule.ymlinstead of_quarto.yml. This is to separate the look of the website from the scheduling and to break what would be a very long file (for a complex website) into two smaller, specialized ones. If, at a later date, it'd be advantageous to made the_schedule.ymlavailable as project-level metadata, that file can be added to_quarto.ymlusingmetadata-files: _schedule.yml.Fixes #2