refactor(#2416): remove the non-pr config-change flow (request_apply_commit / applycommit)

hive-c0re/src/lifecycle/setup.rs

@@ -44,8 +44,7 @@ pub async fn setup_proposed(proposed_dir: &Path, name: &str) -> Result<()> {
     // manager's ergonomics. The URL is the path inside the manager
     // container (`/applied/<n>/.git`), where the RO bind in
     // `set_nspawn_flags` makes it real. hive-c0re itself never
-    // dereferences this remote; the host-side fetch in
-    // `request_apply_commit` uses absolute host paths.
+    // dereferences this remote.
     ensure_applied_remote(proposed_dir, name).await
 }
 
@@ -71,9 +70,8 @@ async fn ensure_applied_remote(proposed_dir: &Path, name: &str) -> Result<()> {
 /// Set up the applied repo. First-spawn only: init the repo, pull
 /// proposed's initial commit in via `git fetch`, tag it `deployed/0`.
 /// This is the *only* time hive-c0re reads from `proposed` for an
-/// agent — subsequent proposals are fetched at `request_apply_commit`
-/// time and tagged `proposal/<id>` (see `actions::approve` for the
-/// tag state machine).
+/// agent — subsequent config changes are fetched from the reviewed
+/// forge PR head at merge time (see `actions::run_merge_config_pr`).
 ///
 /// `proposed_dir` is `None` on rebuild paths where the repo already
 /// exists — we just verify it's the right shape and bail otherwise.
@@ -100,10 +98,8 @@ pub async fn setup_applied(
         git(applied_dir, &["init", "--initial-branch=main"]).await?;
         let proposed_str = proposed.display().to_string();
         // Seed the applied repo at the root (template) commit of proposed,
-        // not at `main`. This ensures `deployed/0` is the template baseline
-        // so the first ApplyCommit diff shows the manager's real changes
-        // rather than an empty diff (which happens when the manager has
-        // already committed their config and proposed/main == proposal/<id>).
+        // not at `main`, so `deployed/0` is the template baseline rather
+        // than whatever the manager may have already committed on top.
         let root_sha = git_root_commit(proposed).await?;
         git(
             applied_dir,