code-coordinator 0.5.327__tar.gz → 0.5.329__tar.gz

{code_coordinator-0.5.327 → code_coordinator-0.5.329}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.327
+Version: 0.5.329
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.327 → code_coordinator-0.5.329}/code_coordinator.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.327
+Version: 0.5.329
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.327 → code_coordinator-0.5.329}/code_coordinator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.5.327",
+  "tag": "0.5.329",
   "distance": 0,
-  "node": "g33af929d66cfc03789a677518e08ff5c0b6d4000",
+  "node": "g620161040c983239a8258b25aa0e4e1fc5cf3c8a",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-31"

{code_coordinator-0.5.327 → code_coordinator-0.5.329}/coord/agent.py

@@ -4027,14 +4027,36 @@ response (a session that silently chose to file instead of asking is \
 exactly the failure this design exists to prevent); the submission's \
 OUTCOME, AUDIENCE, DONE DEFINITION, and CONSTRAINTS; its mapped repo(s); \
 `coordinator.yml` topology context for those repo(s) (depends_on, which \
-machines claim each repo); and a RUNNING CONTEXT section rendering the \
-submission's full ledger so far — every question asked and (if answered) \
-its answer, every decision on record (current and archived, archived ones \
-carrying WHY they were ruled out), and the current narrative. Read \
-RUNNING CONTEXT before doing anything else: never re-ask a question already \
-answered there, and never re-propose a decision already archived there \
-without new information that changes the calculus — cite the existing \
-entry's seq/reason if the operator or a re-briefed fact brings it up again.
+machines claim each repo); a HOUSE STACK section (#2997) naming what the \
+REST of this org's registered repos already run and deploy on, which \
+managed services are already in use and already paid for, and any coord \
+gate that assumes a particular host; and a RUNNING CONTEXT section \
+rendering the submission's full ledger so far — every question asked and \
+(if answered) its answer, every decision on record (current and archived, \
+archived ones carrying WHY they were ruled out), and the current \
+narrative. Read RUNNING CONTEXT before doing anything else: never re-ask a \
+question already answered there, and never re-propose a decision already \
+archived there without new information that changes the calculus — cite \
+the existing entry's seq/reason if the operator or a re-briefed fact \
+brings it up again.
+
+**HOUSE STACK is context, not a mandate** — you may still propose \
+something outside it when it genuinely fits better (a greenfield repo is \
+not required to inherit the fleet's stack). But you may never propose a \
+stack/architecture/hosting/vendor decision in SILENCE about it: if HOUSE \
+STACK names a service that's a plausible fit and you're proposing \
+something else, you MUST record the house-stack option itself as a \
+considered-and-rejected alternative (`coord portal decision propose` \
+naming it, then `coord portal decision reject ... "<why it loses>"`) in \
+the SAME iteration you propose your own recommendation — the same \
+"record every alternative you seriously considered and ruled OUT" rule the \
+PROPOSE terminal move already requires below applies to the house stack \
+first, not last. The failure this closes (#2997, SUB-1EA1D3) was a session \
+proposing a brand-new vendor for a greenfield repo with FOUR rejected \
+alternatives on record and Cloudflare — the stack the rest of the org \
+already runs and pays for — never mentioned in any of them. Silence, not \
+disagreement, was the bug; a reasoned rejection is a completely fine \
+outcome.
 
 You can always re-fetch the live ledger mid-session with:
 
@@ -4260,7 +4282,41 @@ exists. Any time the operator gives you a substantive fact about the \
 client, the users, or the scope, say back what you would record and ask \
 whether to record it. Keep the wording theirs, not your paraphrase — the \
 ledger is verbatim by design, and the narrative (which is regenerable) is \
-where summarizing belongs.\
+where summarizing belongs.
+
+**Confirming a decision on the operator's instruction (#2998).** The base \
+prompt above says never to run `coord portal decision confirm` — that rule \
+was written for a session with nobody to ask. You have someone to ask: the \
+operator sitting at this terminal, who is exactly who that command is \
+reserved for. What never changes, headless or attended, is that YOU may \
+never confirm your own proposal on your own initiative — inferring consent, \
+or treating agreement about something else as consent to confirm, is \
+exactly the self-approval the base rule exists to prevent.
+
+But when the operator gives you an EXPLICIT, PRESENT-TURN instruction to \
+confirm a specific decision ("confirm decision 8", "yes, confirm that"), you \
+MAY act on it, in this order:
+
+1. Quote the operator's instruction back, verbatim, so the transcript makes \
+unambiguous that this was ordered, not inferred.
+2. Record the attribution on the ledger BEFORE confirming, so a later \
+session (or a human reading the ledger) can see this was operator-\
+instructed rather than session-initiated:
+
+    coord portal note <submission_id> "Operator instructed: confirm decision #<seq> (\"<their exact words>\")"
+
+3. Only then run:
+
+    coord portal decision confirm <submission_id> <seq>
+
+Do not collapse this into one step, and do not run it on a vague or implied \
+go-ahead — if you are not sure which decision the operator means, ask for \
+the seq before running anything. This carve-out covers `decision confirm` \
+ONLY. Every other entry on the deny list stays forbidden in this session \
+exactly as it is headlessly (raw `gh` mutations, `git push`, `git commit`, \
+destructive git, `coord approve`, `coord merge`, `coord assign`) — an \
+operator being present changes who may authorize a RESERVED command, it \
+does not change whether a DANGEROUS one is safe.\
 """
 
 # Deny list applied to decomposition-chat workers (#2533; extended #2750
@@ -4274,6 +4330,13 @@ where summarizing belongs.\
 # confirm` (the OPERATOR's move, never this session's own — #2750's "Propose"
 # terminal move must not self-confirm), while every write path this session
 # actually needs is allowed by omission.
+#
+# This is the HEADLESS list — used verbatim by `default_worker_command`'s
+# `spec.type == "decomposition-chat"` branch below, where the session
+# genuinely has nobody to ask, so `decision confirm` stays hard-denied. The
+# `--interactive` posture has an operator in the room; see
+# DECOMPOSITION_CHAT_ATTENDED_DENY_COMMANDS below (#2998) for its own,
+# narrower carve-out of exactly this one entry.
 DECOMPOSITION_CHAT_DENY_COMMANDS: list[str] = [
     "Bash(gh issue edit *)",
     "Bash(gh issue create *)",
@@ -4302,6 +4365,23 @@ DECOMPOSITION_CHAT_DENY_COMMANDS: list[str] = [
     "Bash(coord portal decision confirm *)",
 ]
 
+# #2998: the ATTENDED counterpart to the list above — every entry the same
+# EXCEPT `coord portal decision confirm`. An attended session has an
+# operator sitting at the terminal, and `decision confirm` is RESERVED for
+# the operator (not DANGEROUS the way `git push`/`coord merge`/destructive
+# git are) — the question in that posture is who authorised it, not whether
+# it's safe. DECOMPOSITION_CHAT_ATTENDED_ADDENDUM spells out the condition
+# under which the session may actually run it (an explicit, present-turn
+# operator instruction, quoted back and attributed on the ledger via `coord
+# portal note` before confirming) — this list only stops blanket-denying it
+# so that addendum isn't fighting a FORBIDDEN COMMANDS entry telling the
+# session the opposite. Every genuinely dangerous entry stays denied,
+# unchanged, in both postures.
+DECOMPOSITION_CHAT_ATTENDED_DENY_COMMANDS: list[str] = [
+    cmd for cmd in DECOMPOSITION_CHAT_DENY_COMMANDS
+    if cmd != "Bash(coord portal decision confirm *)"
+]
+
 MOCK_AUTHOR_SYSTEM_PROMPT = """\
 You are an independent mock-author agent for Gate A of a milestone \
 (#930, docs/ORACLE_LOOP.md) — the pre-work architecture gate. You have \

{code_coordinator-0.5.327 → code_coordinator-0.5.329}/coord/commands/portal.py

@@ -723,7 +723,7 @@ def _run_decompose_chat_interactive(
     from coord.agent import (  # noqa: PLC0415
         AssignmentSpec as _AssignmentSpecDc,
         DECOMPOSITION_CHAT_ATTENDED_ADDENDUM,
-        DECOMPOSITION_CHAT_DENY_COMMANDS,
+        DECOMPOSITION_CHAT_ATTENDED_DENY_COMMANDS,
         DECOMPOSITION_CHAT_SYSTEM_PROMPT,
         build_deny_prompt,
     )
@@ -731,6 +731,7 @@ def _run_decompose_chat_interactive(
         build_decomposition_chat_briefing,
         describe_unapproved_submission,
         fetch_running_context,
+        house_stack_context,
         render_running_context_section,
         repo_topology_context,
         resolve_approved_submission,
@@ -794,6 +795,7 @@ def _run_decompose_chat_interactive(
     # that the Ask move would "refuse loudly" — no longer true.
 
     topology_context = repo_topology_context(cfg, repos)
+    house_stack = house_stack_context(cfg, exclude_repos=repos)
     discuss_mode, discuss_reason = select_discuss_mode(cfg, submission, discuss_override=discuss)
     running_context = render_running_context_section(fetch_running_context(submission_id))
     briefing = build_decomposition_chat_briefing(
@@ -802,6 +804,7 @@ def _run_decompose_chat_interactive(
         discuss=discuss_mode,
         discuss_reason=discuss_reason,
         running_context_section=running_context,
+        house_stack_context_section=house_stack,
     )
 
     repo_path = str(_Path(machine.repo_path(repos[0]) or str(_Path.cwd())).expanduser())
@@ -819,9 +822,9 @@ def _run_decompose_chat_interactive(
     seed_prompt = (
         f"Intake session for portal submission {submission_id} "
         f"(MODE: {mode_word} — {discuss_reason}): read the full context at "
-        f"{brief_path} (submission fields, repo topology, and the running-"
-        "context ledger so far) and let's work through it. This is an "
-        "ATTENDED session: state your read and your PROPOSED exit, then stop "
+        f"{brief_path} (submission fields, repo topology, the house stack, "
+        "and the running-context ledger so far) and let's work through it. "
+        "This is an ATTENDED session: state your read and your PROPOSED exit, then stop "
         "and wait for me — write nothing until I answer (#2867)."
     )
 
@@ -851,13 +854,21 @@ def _run_decompose_chat_interactive(
     # This session, by contrast, has a human in the pane: the addendum makes
     # its first turn confirm-then-write (#2742's absorbed half, which #2750
     # only ever wired into mode SELECTION, never into the posture itself).
+    #
+    # #2998: the deny list here is the ATTENDED one — identical to the
+    # headless DECOMPOSITION_CHAT_DENY_COMMANDS except it does not blanket-
+    # forbid `coord portal decision confirm`, because DECOMPOSITION_CHAT_
+    # ATTENDED_ADDENDUM spells out the (narrow, operator-instruction-gated)
+    # condition under which this session may run it. The headless path above
+    # keeps using the unmodified list, so a headless session still cannot
+    # confirm, self-confirm, or be talked into confirming.
     argv = provider.build_command(
         spec,
         resolved_model=resolved_model,
         system_prompt=(
             DECOMPOSITION_CHAT_SYSTEM_PROMPT
             + DECOMPOSITION_CHAT_ATTENDED_ADDENDUM
-            + build_deny_prompt(DECOMPOSITION_CHAT_DENY_COMMANDS)
+            + build_deny_prompt(DECOMPOSITION_CHAT_ATTENDED_DENY_COMMANDS)
         ),
         allowed_tools="Read,Bash",
     )

{code_coordinator-0.5.327 → code_coordinator-0.5.329}/coord/decomposition_chat.py

@@ -409,6 +409,209 @@ def pick_decomposition_chat_machine(cfg: "Config", repos: list[str]) -> "Machine
     return None
 
 
+# ── #2997: HOUSE STACK — the fleet's existing stack, not just this
+# submission's mapped repo(s). See the module briefing (SUB-1EA1D3, the
+# grocery-list submission) for why this section exists: a MODE: DISCUSS
+# iteration proposed Vite+React+Supabase for a greenfield repo without ever
+# weighing Cloudflare — the stack every other repo in this org already runs
+# and pays for — because nothing in the briefing carried it. This section is
+# CONTEXT, not a mandate (the design sketch's own framing): a session may
+# still propose something else, but the system prompt (coord/agent.py) is
+# what requires it to then record the house alternative as a
+# considered-and-rejected decision rather than staying silent about it.
+
+#: Root-level marker file -> the stack signal its mere presence implies.
+#: Deliberately mechanical and small, same posture as `_SEEDED_ROOT_FILES`
+#: above: cheap to check, cheap to extend, wrong at worst by omission (a
+#: repo using something unlisted here just contributes nothing) never by a
+#: false positive.
+_ROOT_STACK_MARKERS: dict[str, str] = {
+    "wrangler.toml": "Cloudflare Workers/Pages (wrangler.toml)",
+    "Cargo.toml": "Rust (Cargo.toml)",
+    "package.json": "Node/TypeScript (package.json)",
+    "pyproject.toml": "Python (pyproject.toml)",
+}
+
+#: Same idea, scoped to `.github/workflows/` — a deploy LANE is a workflow
+#: file, not a root marker.
+_WORKFLOW_STACK_MARKERS: dict[str, str] = {
+    "deploy-cloudflare.yml": "Cloudflare Pages deploy (.github/workflows/deploy-cloudflare.yml)",
+}
+
+#: `wrangler.toml` binding keys -> the managed Cloudflare service they name
+#: (Cloudflare's own `wrangler.toml` schema) — read only when the file is
+#: actually present, so this never guesses at a service that isn't wired up.
+_WRANGLER_BINDING_MARKERS: dict[str, str] = {
+    "d1_databases": "Cloudflare D1 (bound in wrangler.toml)",
+    "r2_buckets": "Cloudflare R2 (bound in wrangler.toml)",
+    "kv_namespaces": "Cloudflare KV (bound in wrangler.toml)",
+}
+
+#: Keywords worth a mention when they show up in a repo's own `CLAUDE.md` —
+#: the design sketch's "cheapest read from each repo's own CLAUDE.md" half,
+#: for a lane that leaves no marker file at all (e.g. Cloudflare Access,
+#: which is edge config, never a repo artifact — coord-portal's own
+#: `docs/CUSTOMER_PORTAL.md` names it in prose, not in a file this module
+#: could otherwise detect). Casefolded substring match: a false positive
+#: here only adds one extra weighed line, never a wrong guess about what
+#: exists, since the word is genuinely present in the repo's own docs.
+_CLAUDE_MD_KEYWORD_MARKERS: dict[str, str] = {
+    "cloudflare access": "Cloudflare Access (mentioned in CLAUDE.md)",
+    "cloudflare pages": "Cloudflare Pages (mentioned in CLAUDE.md)",
+    "cloudflare d1": "Cloudflare D1 (mentioned in CLAUDE.md)",
+    "cloudflare r2": "Cloudflare R2 (mentioned in CLAUDE.md)",
+}
+
+
+def _repo_stack_signals(repo_github: str, branch: str) -> list[str]:
+    """Mechanical, best-effort stack signals for *repo_github* on *branch* —
+    root-level marker files, known deploy-workflow files under
+    `.github/workflows/`, and (when `wrangler.toml` is present) the managed
+    Cloudflare services it binds.
+
+    **Degrades gracefully** (#2997 acceptance criterion): any lookup
+    failure, or a repo with nothing recognisable, returns `[]` rather than a
+    guess — this feeds an informational briefing section, not a gate, so
+    silence is always the safe failure mode.
+
+    "Any lookup failure" is meant literally, hence the deliberately broad
+    ``except Exception`` guards below rather than the narrow
+    ``RuntimeError``/``ValueError`` pair an earlier revision used. The
+    Contents-API seam this walks is not exception-typed end to end:
+    ``github_ops.list_repo_dir`` indexes ``entry["name"]`` on whatever JSON
+    came back (``KeyError``/``TypeError`` on a malformed or
+    unexpectedly-shaped payload), and ``_gh`` itself is a subprocess
+    boundary that a caller lower in the stack can surface as ``OSError``.
+    None of those are worth turning an *informational* paragraph into a
+    hard failure of ``coord portal decompose-chat`` for — a crash here
+    costs the operator the whole intake session, while a swallowed lookup
+    costs one unweighed line.
+    """
+    from coord import github_ops  # noqa: PLC0415
+
+    try:
+        root_files, root_dirs = _dir_entries(repo_github, "", branch)
+    except Exception:  # noqa: BLE001 - informational section, never a gate
+        return []
+
+    signals = [label for marker, label in _ROOT_STACK_MARKERS.items() if marker in root_files]
+
+    def _file_text(path: str) -> str:
+        """*path*'s contents on *branch*, or ``""`` on any lookup failure."""
+        try:
+            text = github_ops.get_repo_file(repo_github, path, branch)
+            # `isinstance` rather than a bare return: a Contents-API payload
+            # that decodes to something other than text must not turn a
+            # substring probe below into a `TypeError`.
+            return text if isinstance(text, str) else ""
+        except Exception:  # noqa: BLE001 - see the docstring
+            # Covers `binascii.Error` (a ValueError subclass) from
+            # `get_repo_file_with_sha`'s `base64.b64decode` on a malformed
+            # Contents-API response, `GhError` from the subprocess boundary,
+            # and anything else the seam can surface: this feeds an
+            # informational section, not a gate, so a failed read degrades
+            # to "no signal" rather than blowing up the briefing build.
+            return ""
+
+    def _entries(path: str) -> tuple[list[str], list[str]]:
+        """``(files, dirs)`` under *path*, or ``([], [])`` on any failure."""
+        try:
+            return _dir_entries(repo_github, path, branch)
+        except Exception:  # noqa: BLE001 - see the docstring
+            return [], []
+
+    if "wrangler.toml" in root_files:
+        wrangler_text = _file_text("wrangler.toml")
+        signals += [
+            label for key, label in _WRANGLER_BINDING_MARKERS.items() if key in wrangler_text
+        ]
+
+    if "CLAUDE.md" in root_files:
+        claude_md_text = _file_text("CLAUDE.md").casefold()
+        signals += [
+            label for key, label in _CLAUDE_MD_KEYWORD_MARKERS.items() if key in claude_md_text
+        ]
+
+    if ".github" in root_dirs:
+        _, gh_dirs = _entries(".github")
+        if "workflows" in gh_dirs:
+            wf_files, _ = _entries(".github/workflows")
+            signals += [
+                label for marker, label in _WORKFLOW_STACK_MARKERS.items() if marker in wf_files
+            ]
+
+    return signals
+
+
+def house_stack_context(cfg: "Config", exclude_repos: list[str] | None = None) -> str:
+    """Render the HOUSE STACK briefing section: what the *rest* of the
+    fleet's repos already run and deploy on, derived mechanically from each
+    registered repo's tracked files rather than hand-maintained (the design
+    sketch's own preference — a hand-maintained approved-stack list rots and
+    suppresses the reasoning the decision archive exists to capture).
+
+    *exclude_repos* is normally the submission's own mapped repo(s) — the
+    one(s) actually being decomposed, which say nothing about "the REST of
+    the fleet" even when they aren't greenfield.
+
+    A repo that contributes no recognisable signal (no CLAUDE.md, no known
+    marker file, no known workflow file) is omitted from the per-repo list
+    entirely — #2997's "degrades gracefully" criterion: nothing beats a
+    wrong guess. When *no* repo in the fleet contributes anything, the whole
+    section reads as empty rather than asserting a managed-services list or
+    a host-coupled gate that nothing here actually evidences.
+
+    One sick repo never costs the operator the whole intake session: each
+    repo's probe is isolated, so a lookup that blows up for `acme/api`
+    still leaves `acme/coord-portal`'s Cloudflare signal in the rendered
+    section. This section is built on the critical path of *every*
+    `coord portal decompose-chat` (headless and `--interactive` alike) —
+    an informational paragraph must never be able to abort a dispatch.
+    """
+    exclude = set(exclude_repos or [])
+    per_repo: list[str] = []
+    saw_cloudflare = False
+    for repo_cfg in cfg.repos:
+        if repo_cfg.name in exclude:
+            continue
+        branch = repo_cfg.default_branch or "main"
+        try:
+            signals = _repo_stack_signals(repo_cfg.github, branch)
+        except Exception:  # noqa: BLE001 - one repo must not sink the section
+            continue
+        if not signals:
+            continue
+        per_repo.append(f"- {repo_cfg.name} ({repo_cfg.github}): {'; '.join(signals)}")
+        if any("Cloudflare" in s for s in signals):
+            saw_cloudflare = True
+
+    if not per_repo:
+        return (
+            "HOUSE STACK (fleet-wide, #2997): no recognisable stack/deploy signal on any "
+            "other registered repo — nothing to weigh here."
+        )
+
+    lines = [
+        "HOUSE STACK (fleet-wide, not just this submission's mapped repo(s) — #2997):",
+        *per_repo,
+        "",
+        "This is CONTEXT, not a mandate: propose something else if it genuinely fits "
+        "better, but if you do, record the house-stack alternative as a "
+        "considered-and-rejected decision with a reason (`coord portal decision propose` "
+        "then `coord portal decision reject ... \"<why the house stack loses>\"`) instead "
+        "of leaving it unweighed.",
+    ]
+    if saw_cloudflare:
+        lines.append("")
+        lines.append(
+            "Gate that assumes a host: `coord portal enqueue-preview` reads a Cloudflare "
+            "Pages PREVIEW deployment URL created per-PR by `cloudflare/pages-action` "
+            "(docs/CUSTOMER_PORTAL.md) — choosing a different host means the #2359 "
+            "customer preview-approval gate does not apply without new coord work."
+        )
+    return "\n".join(lines)
+
+
 def repo_topology_context(cfg: "Config", repos: list[str]) -> str:
     """One paragraph of `coordinator.yml` topology per mapped repo — the
     "coordinator.yml topology context ... the same way docs/CUSTOMER_PORTAL.md's
@@ -442,6 +645,7 @@ def build_decomposition_chat_briefing(
     discuss: bool,
     discuss_reason: str,
     running_context_section: str = "",
+    house_stack_context_section: str = "",
 ) -> str:
     """Compose the seed briefing the worker sees as its first user message.
 
@@ -454,6 +658,15 @@ def build_decomposition_chat_briefing(
     pane already shows the operator (ms-67 contract §4b: "nothing hidden
     between 'looks right in the panel' and 'is what the session got'"),
     plus everything #2749's ledger has accumulated across prior iterations.
+
+    **#2997:** also carries a HOUSE STACK section (*house_stack_context_section*,
+    normally :func:`house_stack_context`'s output) — the fleet's existing
+    stack and infrastructure conventions, which used to be entirely absent
+    from this briefing. That gap is what let a MODE: DISCUSS iteration on a
+    greenfield repo propose a brand-new vendor (Supabase) without ever
+    weighing the Cloudflare stack the rest of this org already runs and
+    pays for (SUB-1EA1D3, this issue's own measured regression case). Empty
+    by default so every existing caller/test keeps working unchanged.
     """
     submission_id = submission.get("submission_id", "")
     repos = submission.get("repos") or []
@@ -484,6 +697,11 @@ def build_decomposition_chat_briefing(
     parts.append("COORDINATOR.YML TOPOLOGY CONTEXT:")
     parts.append(topology_context)
     parts.append("")
+    parts.append(
+        house_stack_context_section.strip()
+        or "HOUSE STACK (fleet-wide, #2997): (not computed for this briefing)"
+    )
+    parts.append("")
     parts.append(
         running_context_section.strip()
         or "RUNNING CONTEXT (from the portal ledger): (none yet — first iteration)"
@@ -677,6 +895,7 @@ def dispatch_decomposition_chat(
         machine = picked
 
     topology_context = repo_topology_context(config, repos)
+    house_stack = house_stack_context(config, exclude_repos=repos)
     discuss_mode, discuss_reason = select_discuss_mode(
         config, submission, discuss_override=discuss
     )
@@ -687,6 +906,7 @@ def dispatch_decomposition_chat(
         discuss=discuss_mode,
         discuss_reason=discuss_reason,
         running_context_section=running_context,
+        house_stack_context_section=house_stack,
     )
 
     resolved_model = config.models.default