Bug: Repo folder hierarchy missing `custom/` directory layer

[jmiller-moko]

Describe the bug
Repo folder hierarchy does not match the intended structure. This breaks modules such as Google where the module path is hardcoded to /htdocs/custom/ - the repo is missing the custom folder layer, causing path resolution to fail at runtime.

To Reproduce

1. Clone the repo and deploy to an htdocs-based server environment
2. Attempt to load a module that references /htdocs/custom/ (e.g., Google module)
3. Observe that the module fails to load — the custom/ directory layer is absent from the repo structure

Expected behavior
The repo folder structure should include a custom/ directory layer under htdocs/, matching the hardcoded paths expected by dependent modules:

htdocs/
└── custom/
    └── [module folders]

Current behavior
The repo structure is missing the custom/ layer:

htdocs/
└── [module folders]

Additional context
Any module with a hardcoded reference to /htdocs/custom/ will be affected. Audit other modules for similar path assumptions to prevent recurrence.