Strip language surfaces from hyperpush root

.github/CODEOWNERS

@@ -1,23 +1,6 @@
-# Default review owners
-#
-# These owners are inferred from current repo history and active maintenance.
-# If the maintainer roster changes, update this file before relying on automatic review requests.
 * @rcodyp @snowdamiz
 
-# Core compiler, runtime, and packaging
-/compiler/ @rcodyp @snowdamiz
-/registry/ @rcodyp @snowdamiz
-
-# Docs and public sites
-/website/ @rcodyp @snowdamiz
-/packages-website/ @rcodyp @snowdamiz
-/*.md @rcodyp @snowdamiz
-
-# Editors and tooling integrations
-/tools/ @rcodyp @snowdamiz
-
-# Examples and starter templates
-/examples/ @rcodyp @snowdamiz
-/scripts/fixtures/ @rcodyp @snowdamiz
-/reference-backend/ @rcodyp @snowdamiz
 /mesher/ @rcodyp @snowdamiz
+/.github/ @rcodyp @snowdamiz
+/scripts/ @rcodyp @snowdamiz
+/*.md @rcodyp @snowdamiz

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,5 +1,5 @@
 name: Bug report
-description: Report a reproducible defect in Mesh, its tooling, starter templates, or docs.
+description: Report a reproducible defect in Mesher, landing, frontend-exp, or product repo CI/docs.
 title: "[Bug]: "
 labels:
   - bug
@@ -9,40 +9,37 @@ body:
       value: |
         Thanks for taking the time to file a bug report.
 
-        Please use this form for reproducible defects in Mesh itself, its compiler/runtime/tooling, starter templates, examples, installers, or documentation.
+        Please use this form for reproducible defects in the product-owned Hyperpush surfaces.
   - type: checkboxes
     id: checks
     attributes:
       label: Before you submit
       options:
-        - label: I searched existing issues and checked the relevant docs/examples first.
+        - label: I searched existing issues and checked the nearest maintainer docs first.
           required: true
-        - label: I can reproduce this with a current build, the latest public release, or a specific commit I list below.
+        - label: I can reproduce this with the current main branch or a specific commit I list below.
           required: true
     validations:
       required: true
   - type: dropdown
     id: area
     attributes:
       label: Affected area
-      description: Pick the closest match.
       options:
-        - compiler / meshc
-        - package manager / meshpkg
-        - runtime / mesh-rt
-        - LSP / editor integration
-        - starter templates / examples
-        - installers / release tooling
-        - documentation / website
+        - Mesher runtime / API
+        - Mesher maintainer scripts
+        - landing app
+        - frontend-exp
+        - product CI / deploy
+        - product docs / runbooks
         - other
     validations:
       required: true
   - type: input
     id: version
     attributes:
-      label: Version / commit
-      description: Paste the output of `meshc --version`, `meshpkg --version`, or the commit SHA you tested.
-      placeholder: meshc 12.0.0 / meshpkg 12.0.0 / abc1234
+      label: Commit / version tested
+      placeholder: a9ad114 / local branch / release tag
     validations:
       required: true
   - type: dropdown
@@ -57,16 +54,15 @@ body:
     validations:
       required: true
   - type: input
-    id: setup
+    id: path
     attributes:
-      label: Project / starter / path (if relevant)
+      label: Product path
       description: Tell us what you were running.
-      placeholder: examples/todo-postgres, meshc init --clustered, website/docs/docs/getting-started/index.md
+      placeholder: mesher/, mesher/landing/, mesher/frontend-exp/
   - type: textarea
     id: steps
     attributes:
       label: Reproduction steps
-      description: Give the smallest truthful sequence that reproduces the problem.
       placeholder: |
         1. Run ...
         2. Open ...
@@ -77,24 +73,16 @@ body:
     id: expected
     attributes:
       label: Expected behavior
-      placeholder: What should have happened?
     validations:
       required: true
   - type: textarea
     id: actual
     attributes:
       label: Actual behavior
-      placeholder: What happened instead?
     validations:
       required: true
   - type: textarea
     id: logs
     attributes:
       label: Logs, errors, or screenshots
-      description: Paste terminal output, stack traces, diagnostics, or screenshots if they help.
       render: shell
-  - type: textarea
-    id: context
-    attributes:
-      label: Additional context
-      description: Include workarounds, frequency, regression range, or anything else useful.

.github/ISSUE_TEMPLATE/config.yml

@@ -2,13 +2,13 @@ blank_issues_enabled: false
 contact_links:
   - name: Support guide
     url: https://github.com/hyperpush-org/hyperpush-mono/blob/main/SUPPORT.md
-    about: Before filing an issue, check the support guide and starter/example pointers.
-  - name: Getting Started docs
+    about: Start with the product support guide and maintainer runbook links.
+  - name: Mesher maintainer guide
+    url: https://github.com/hyperpush-org/hyperpush-mono/blob/main/mesher/README.md
+    about: Mesher maintainer-facing startup, smoke, and verification workflow.
+  - name: Mesh language docs
     url: https://meshlang.dev/docs/getting-started/
-    about: Install Mesh, run hello-world, and choose the right starter path.
-  - name: Tooling docs
-    url: https://meshlang.dev/docs/tooling/
-    about: Compiler, editor, and tooling workflows.
+    about: Mesh installation, language/tooling docs, and starter guidance.
   - name: Security policy
     url: https://github.com/hyperpush-org/hyperpush-mono/blob/main/SECURITY.md
     about: Use the private reporting path for vulnerabilities instead of public issues.

.github/ISSUE_TEMPLATE/documentation.yml

@@ -1,13 +1,13 @@
 name: Documentation issue
-description: Report missing, outdated, confusing, or incorrect documentation.
+description: Report missing, outdated, confusing, or incorrect product documentation.
 title: "[Docs]: "
 labels:
   - documentation
 body:
   - type: markdown
     attributes:
       value: |
-        Use this form for docs problems on the website, in starter/example READMEs, or in contributor-facing repo docs.
+        Use this form for docs problems in the product repo, Mesher runbook, landing docs, or product maintainer instructions.
   - type: checkboxes
     id: checks
     attributes:
@@ -21,8 +21,7 @@ body:
     id: page
     attributes:
       label: Affected page or file
-      description: Paste the URL or repo path.
-      placeholder: https://meshlang.dev/docs/getting-started/ or README.md
+      placeholder: README.md / mesher/README.md / mesher/frontend-exp/README.md
     validations:
       required: true
   - type: dropdown
@@ -43,17 +42,13 @@ body:
     id: problem
     attributes:
       label: What is wrong today?
-      placeholder: Describe the mismatch, omission, or confusing part.
     validations:
       required: true
   - type: textarea
     id: fix
     attributes:
       label: Suggested fix
-      description: If you know how the page should read, describe it here.
-      placeholder: Explain the change, updated command, corrected link, or missing context.
   - type: textarea
     id: context
     attributes:
       label: Additional context
-      description: Screenshots, exact commands, related pages, or follow-up notes.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,21 +1,21 @@
 name: Feature request
-description: Propose a new capability or improvement for Mesh, its tooling, docs, or starter templates.
+description: Propose a product improvement for Mesher, landing, frontend-exp, or product operations.
 title: "[Feature]: "
 labels:
   - enhancement
 body:
   - type: markdown
     attributes:
       value: |
-        Please describe the problem you are trying to solve, not only the shape of the solution.
+        Describe the product workflow or user problem you want to improve.
   - type: checkboxes
     id: checks
     attributes:
       label: Before you submit
       options:
-        - label: I searched existing issues, docs, and examples for prior discussion or an existing workflow.
+        - label: I searched existing issues and the maintainer docs first.
           required: true
-        - label: I explained the user problem or workflow gap this request is addressing.
+        - label: I explained the user problem or workflow gap, not only the solution shape.
           required: true
     validations:
       required: true
@@ -24,45 +24,36 @@ body:
     attributes:
       label: Area
       options:
-        - language / compiler
-        - runtime / distribution
-        - meshpkg / packaging
-        - LSP / editor support
-        - starter templates / examples
-        - docs / website
-        - release / installer workflow
+        - Mesher runtime / API
+        - Mesher maintainer workflow
+        - landing app
+        - frontend-exp
+        - product CI / deploy
+        - product docs / runbooks
         - other
     validations:
       required: true
   - type: textarea
     id: problem
     attributes:
       label: Problem statement
-      description: What are you trying to do, and where does the current workflow break down?
-      placeholder: Describe the workflow, limitation, or recurring pain point.
     validations:
       required: true
   - type: textarea
     id: proposal
     attributes:
       label: Proposed solution
-      description: Describe the change you want to see.
-      placeholder: Describe the smallest useful improvement.
     validations:
       required: true
   - type: textarea
     id: alternatives
     attributes:
       label: Alternatives considered
-      description: Workarounds, rejected approaches, or prior art.
   - type: textarea
     id: impact
     attributes:
       label: Expected impact
-      description: Who benefits, and how would success be measured?
-      placeholder: Better onboarding, fewer manual steps, simpler deployment proof, lower runtime overhead, etc.
   - type: textarea
     id: context
     attributes:
       label: Additional context
-      description: Links, screenshots, code snippets, or related issues/PRs.

.github/dependabot.yml

@@ -6,7 +6,7 @@ updates:
       interval: weekly
     labels:
       - dependencies
-      - area: release
+      - area: ci
     commit-message:
       prefix: "ci"
 
@@ -19,3 +19,13 @@ updates:
       - area: landing
     commit-message:
       prefix: "landing"
+
+  - package-ecosystem: npm
+    directory: "/mesher/frontend-exp"
+    schedule:
+      interval: weekly
+    labels:
+      - dependencies
+      - area: frontend-exp
+    commit-message:
+      prefix: "frontend-exp"