more-changes

Signed-off-by: Matt Wrock <[email protected]>

bldr.env.sample

@@ -97,7 +97,7 @@ export OAUTH_CLIENT_ID=0123456789abcdef0123
 export OAUTH_CLIENT_SECRET=0123456789abcdef0123456789abcdef01234567
 
 # Modify these only if there is a specific need, otherwise leave as is
-export BLDR_CHANNEL=on-prem-LTS-2024
+export BLDR_CHANNEL=on-prem-stable
 export BLDR_ORIGIN=habitat
 export HAB_BLDR_URL=https://bldr.habitat.sh/
 # From the Automate CLI use

on-prem-docs/builder-oauth.md

@@ -96,6 +96,7 @@ In order to install the on-prem Chef Habitat Builder in an airgapped (no direct
      export DOWNLOAD_DIR=/some/base/download/directory
      cd on-prem-builder
      hab pkg download --target x86_64-linux --channel LTS-2024 --file package_seed_lists/builder_x86_64-linux_lts_2024 --download-directory ${DOWNLOAD_DIR}/builder_packages
+     hab pkg download --target x86_64-linux --channel stable --file package_seed_lists/builder_x86_64-linux_stable --download-directory ${DOWNLOAD_DIR}/builder_packages
      ```
 
 1. Zip up all the above content, transfer and unzip on the Linux system where Builder will be deployed in the Airgapped environment

package_seed_lists/README.md

@@ -5,6 +5,8 @@ With the `hab pkg download` command, you can download a list of seed packages al
 This directory contains sample 'seed lists' of packages for bootstrapping and syncing on-prem Builder for
 a number of different scenarios.
 
+> Note: We are moving away from seed lists. See [Bootstrap Core Origin](../on-prem-docs/bootstrap-core.md) for instructions on using the `pkg-sync` tool to sync packages from public builder to an on-prem instance.
+
 The basic file naming pattern is TASK\_ARCH\_CHANNEL. The files are a newline separated list of
 package identifiers. The contents are specific to a particular architecture and channel and the
 correct architecture and channel must be provided on the command line when running the `hab pkg