[Pipelines] Compile multi-model pipelines' models in parallel

I observe that pipelines with multiple models (currently mostly vision
models) spend a lot of their compilation time pinned to a single core.
This is not an efficient use of time. We have two pieces of work, so at
least have each one pinned to one core. This slows down each compile
from about 70 seconds to 90 seconds, but because those 90 seconds are
overlapped, this still saves about 50 seconds overall.

MODULAR_ORIG_COMMIT_REV_ID: 9b7b1e12e297132f15c560e9510af673b322f18c

Author: akirchhoff-modular

.clang-format

@@ -0,0 +1,2 @@
+BasedOnStyle: LLVM
+AlwaysBreakTemplateDeclarations: Yes

.clang-tidy

@@ -0,0 +1,57 @@
+InheritParentConfig: true
+Checks: >
+        bugprone-argument-comment,
+        bugprone-assert-side-effect,
+        bugprone-branch-clone,
+        bugprone-copy-constructor-init,
+        bugprone-dangling-handle,
+        bugprone-dynamic-static-initializers,
+        bugprone-macro-parentheses,
+        bugprone-macro-repeated-side-effects,
+        bugprone-misplaced-widening-cast,
+        bugprone-move-forwarding-reference,
+        bugprone-multiple-statement-macro,
+        bugprone-suspicious-semicolon,
+        bugprone-swapped-arguments,
+        bugprone-terminating-continue,
+        bugprone-unused-raii,
+        bugprone-unused-return-value,
+        misc-redundant-expression,
+        misc-static-assert,
+        misc-unused-using-decls,
+        modernize-use-bool-literals,
+        modernize-loop-convert,
+        modernize-make-unique,
+        modernize-raw-string-literal,
+        modernize-use-equals-default,
+        modernize-use-default-member-init,
+        modernize-use-emplace,
+        modernize-use-nullptr,
+        modernize-use-override,
+        modernize-use-using,
+        performance-for-range-copy,
+        performance-implicit-conversion-in-loop,
+        performance-inefficient-algorithm,
+        performance-inefficient-vector-operation,
+        performance-move-const-arg,
+        performance-no-automatic-move,
+        performance-trivially-destructible,
+        performance-unnecessary-copy-initialization,
+        performance-unnecessary-value-param,
+        readability-avoid-const-params-in-decls,
+        readability-const-return-type,
+        readability-container-size-empty,
+        readability-inconsistent-declaration-parameter-name,
+        readability-misleading-indentation,
+        readability-redundant-control-flow,
+        readability-redundant-smartptr-get,
+        readability-simplify-subscript-expr,
+        readability-use-anyofallof
+
+CheckOptions:
+  - key:             readability-identifier-naming.MemberCase
+    value:           camelBack
+  - key:             readability-identifier-naming.ParameterCase
+    value:           camelBack
+  - key:             readability-identifier-naming.VariableCase
+    value:           camelBack

.gitattributes

@@ -0,0 +1,4 @@
+# Add an override so that .🔥 files are highlighted as Mojo files within github
+# since the linguist system does not work with the .🔥 extention.
+# See https://github.com/github/linguist/blob/master/docs/overrides.md
+*.🔥 linguist-language=Mojo

.github/ISSUE_TEMPLATE/CODEOWNERS

@@ -0,0 +1,5 @@
+# Codeowners for MAX repo.
+# Every line is a file pattern that is followed by one or more code owners.
+# Order is important; the last matching pattern takes the most precedence.
+
+* @modularml/max-code-reviewers

.github/ISSUE_TEMPLATE/doc_issue.yaml

@@ -12,19 +12,20 @@
 ##===----------------------------------------------------------------------===##
 
 name: Documentation issue
-description: Report a problem with the Mojo docs
+description: Report a problem with the MAX docs
 title: "[Docs]"
 labels:
   - documentation
 body:
   - type: markdown
     attributes:
       value: |
-        Thank you for helping us improve the Mojo docs!
+        Thank you for helping us improve the MAX docs!
 
         Please add a title above and fill in the following fields so we can understand the problem.
 
   - type: input
+    id: url
     attributes:
       label: Where is the problem?
       description: Provide a link to the problematic page (with a heading anchor).

.github/ISSUE_TEMPLATE/max_bug_report.yaml

@@ -0,0 +1,55 @@
+##===----------------------------------------------------------------------===##
+# Copyright (c) 2025, Modular Inc. All rights reserved.
+#
+# Licensed under the Apache License v2.0 with LLVM Exceptions:
+# https://llvm.org/LICENSE.txt
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##===----------------------------------------------------------------------===##
+
+name: MAX bug report
+description: Create a bug report to help us improve MAX
+title: "[BUG]: "
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out a bug report!
+
+        Please provide a descriptive title above and fill in the following fields.
+
+  - type: textarea
+    id: Description
+    attributes:
+      label: Bug description
+      description: Describe the bug you encountered and what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: Steps
+    attributes:
+      label: Steps to reproduce
+      description: Provide the specific steps to reproduce the issue.
+      value: |
+        - Include relevant code snippet or link to code that did not work as expected.
+        - If applicable, add screenshots to help explain the problem.
+        - Include anything else that might help us debug the issue.
+    validations:
+      required: true
+
+  - type: textarea
+    id: Context
+    attributes:
+      label: System information
+      description: What version of MAX are you using?
+      value: |
+        - Provide the system information by running `magic info`.
+        - Provide version information for MAX (includes Mojo) by pasting the output of `magic list max`.
+      render: shell

.github/ISSUE_TEMPLATE/max_builds_bug_report.yaml

@@ -0,0 +1,53 @@
+##===----------------------------------------------------------------------===##
+# Copyright (c) 2025, Modular Inc. All rights reserved.
+#
+# Licensed under the Apache License v2.0 with LLVM Exceptions:
+# https://llvm.org/LICENSE.txt
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##===----------------------------------------------------------------------===##
+
+name: MAX Builds model bug report
+description: Report a bug with a model
+title: "[BUG]: "
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out a bug report!
+
+        Please provide a descriptive title above and fill in the following fields.
+
+  - type: input
+    id: model-variant
+    attributes:
+      label: On which model did the bug occur?
+      description: Provide the model (and variant).
+    validations:
+      required: true
+
+  - type: textarea
+    id: Description
+    attributes:
+      label: Bug description
+      description: Describe the bug you encountered and what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: Steps
+    attributes:
+      label: Steps to reproduce
+      description: Provide the specific steps to reproduce the issue.
+      value: |
+        - Include relevant code snippet or link to code that did not work as expected.
+        - If applicable, add screenshots to help explain the problem.
+        - Include anything else that might help us debug the issue.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/max_feature_request.yaml

@@ -0,0 +1,49 @@
+##===----------------------------------------------------------------------===##
+# Copyright (c) 2025, Modular Inc. All rights reserved.
+#
+# Licensed under the Apache License v2.0 with LLVM Exceptions:
+# https://llvm.org/LICENSE.txt
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##===----------------------------------------------------------------------===##
+
+name: MAX feature request
+description: Suggest an enhancement for MAX
+title: "[Feature Request]"
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to suggest a MAX enhancement!
+
+        Please enter a concise title above and fill out the following fields.
+
+  - type: textarea
+    id: Request
+    attributes:
+      label: What is your request?
+      description: Describe how you'd like us to improve MAX.
+    validations:
+      required: true
+
+  - type: textarea
+    id: Motivation
+    attributes:
+      label: What is your motivation for this change?
+      description: Describe the problem that your feature seeks to address (what is the value to the product/user?).
+    validations:
+      required: true
+
+  - type: textarea
+    id: Description
+    attributes:
+      label: Any other details?
+      description: Perhaps some minimum functional attributes the implementation should include, or other context about your feature.
+    validations:
+      required: false