Add Progmaweb issue templates for account ViGet and corporate web reports

2 files changed, 61 insertions, 0 deletions

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..d0d19b8
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,35 @@
+---
+name: Progmaweb bug
+about: Report a problem with Progmasoft, accounts, or ViGet
+title: "[Bug] "
+---
+
+<!-- SPDX-FileCopyrightText: 2026 Progmasoft <support@progmasoft.com> -->
+<!-- SPDX-License-Identifier: AGPL-3.0-or-later WITH AdditionRef-Progmasoft-Patent-Grant-1.1 -->
+
+This repository owns `progmasoft.com`, `account.progmasoft.com`, and `viget.progmasoft.com`. Visual X# language pages and compiler behavior belong in their separate repositories. Never post passwords, verification codes, OAuth secrets, session cookies, email headers containing private data, or access tokens. Send security vulnerabilities privately to support@progmasoft.com.
+
+### Affected host and flow
+
+- Host and sanitized path:
+- Area (corporate page, account registration/login/recovery, dashboard, ViGet package catalog, DSL plugin catalog, API, localization, or theme):
+- Account state needed to reproduce (signed out, newly registered, signed in), without identifying a real account:
+
+### Observed and expected behavior
+
+Describe what happened, what you expected, and any visible status code or safe error message. If the issue involves a package path, distinguish `/<Publisher>/<Name>/` ViPkgs from `/dslplugins/<Publisher>/<Name>/` JAR plugins; do not attach private packages.
+
+### Reproduction
+
+List the shortest safe steps. For account or authorization issues, use redacted request/response details and say whether the problem also occurs in a fresh private browser session. Do not publish a real email address unless you intentionally want it public.
+
+### Environment
+
+- Browser and version, OS, and viewport:
+- Locale (`en-US` or `de-DE`) and light/dark theme:
+- Approximate incident time and time zone:
+- Progmaweb commit or deployment version, if known:
+
+### Evidence
+
+Attach a sanitized screenshot, browser-console message, or request ID. State whether the problem affects one host or multiple Progmasoft hosts.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 0000000..64fbd29
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,26 @@
+---
+name: Progmaweb improvement
+about: Propose an account, ViGet, or corporate-web improvement
+title: "[Proposal] "
+---
+
+<!-- SPDX-FileCopyrightText: 2026 Progmasoft <support@progmasoft.com> -->
+<!-- SPDX-License-Identifier: AGPL-3.0-or-later WITH AdditionRef-Progmasoft-Patent-Grant-1.1 -->
+
+This repository owns the Next.js public surfaces and ASP.NET Core account API. Requests about the Visual X# language website or compiler belong in their respective repositories.
+
+### User need and host
+
+Who needs the change, on which host and route, and what cannot they do today? For publisher-related changes, remember that the ViGet publisher is the canonical Progmasoft account name, not a second profile field.
+
+### Proposed behavior
+
+Describe the page, API, or account flow with a concrete example. For registry changes, specify whether the subject is a `.vipkg` or Kotlin DSL plugin JAR and how its public path should appear.
+
+### Security and data impact
+
+Would this change authentication, authorization, account identity, sessions, private data, publication rights, or existing package URLs? Explain how a user would recognize and recover from failure without exposing secrets.
+
+### Presentation and acceptance checks
+
+Describe `en-US`/`de-DE`, light/dark, accessibility, and mobile implications where relevant. What frontend/API tests and live-host checks would prove completion?