/**
 * Workspace-layout conventions shared by CLI, webapp, and worker code.
 *
 * The Fjall scaffolder writes application infrastructure under a `fjall/`
 * boundary directory. The customer-chosen app name lives **inside** that
 * boundary, not as a sibling of it. Two layouts are supported:
 *
 *   - Default (no container):   `fjall/<name>/infrastructure.ts`
 *   - With container:           `<container>/fjall/<name>/infrastructure.ts`
 *
 * The `fjall/` segment is the codemod blast-radius boundary; the
 * `--container` argument names the directory that sits between the repo
 * root and the boundary. Two `fjall create app` calls with the same
 * container value land as siblings inside one shared boundary (the T3
 * multi-app shape), e.g.
 *   `webapp/fjall/api/infrastructure.ts`
 *   `webapp/fjall/worker/infrastructure.ts`
 *
 * Multiple producers (the register-application flow, the auto-link
 * repository flow, the post-create linkage flow, the CLI `cd …` message
 * strings) all derive this path from this helper — keeping it as inline
 * template literals would invite silent CLI/webapp drift if the
 * convention shifts.
 *
 * See the 2026-05-11 marker-as-boundary-not-identity design and the
 * fjall-marker convention pattern for the
 * convention's full topology mapping.
 */
export declare function buildAppConfigPath(appName: string, container?: string): string;