Bootstraps §1.2 scaffolding (README, CONTRIBUTING, CODEOWNERS, CHANGELOG, PR + issue templates, LICENSE, CI workflow, release workflow, commitlint, cliff, .editorconfig, .gitignore, .env.example) and ships a proprietary all-rights-reserved LICENSE naming both founders. Refs: M0.1
This commit was merged in pull request #1.
This commit is contained in:
@@ -0,0 +1,50 @@
|
||||
---
|
||||
name: Bug report
|
||||
about: Something works incorrectly or breaks
|
||||
labels: bug
|
||||
---
|
||||
|
||||
## What happened
|
||||
|
||||
<!-- One sentence. The observable symptom, not the root cause. -->
|
||||
|
||||
## What I expected
|
||||
|
||||
<!-- One sentence. -->
|
||||
|
||||
## Steps to reproduce
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
|
||||
## Environment
|
||||
|
||||
- **Env:** dev / stage / prod
|
||||
- **Tenant slug:** <!-- e.g. acme, demo, leave blank if platform-wide -->
|
||||
- **Product:** <!-- portal / certifai / compliance / tenant-registry / orca-proxy / ... -->
|
||||
- **Release tag / commit SHA:**
|
||||
- **Browser (if portal):**
|
||||
|
||||
## Evidence
|
||||
|
||||
<!-- Trace ID from SigNoz, log excerpts, screenshots, request/response bodies.
|
||||
STRIP PII before pasting. -->
|
||||
|
||||
```
|
||||
<paste here>
|
||||
```
|
||||
|
||||
**SigNoz trace:** <!-- link -->
|
||||
|
||||
## Blast radius
|
||||
|
||||
- [ ] Affects a single tenant
|
||||
- [ ] Affects multiple tenants
|
||||
- [ ] Affects all tenants on this env
|
||||
- [ ] Data loss or corruption risk
|
||||
- [ ] Security / authz implication
|
||||
|
||||
## Suspected cause (optional)
|
||||
|
||||
<!-- Leave blank if you don't know. Speculation here is welcome but not required. -->
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
name: Feature / change request
|
||||
about: Propose a new capability or behavior change
|
||||
labels: enhancement
|
||||
---
|
||||
|
||||
## Problem
|
||||
|
||||
<!-- What is the customer / operator / developer trying to do today, and why is it painful?
|
||||
Lead with the WHY. -->
|
||||
|
||||
## Proposed solution
|
||||
|
||||
<!-- One paragraph. The shape of the change, not the implementation detail. -->
|
||||
|
||||
## Acceptance criteria
|
||||
|
||||
<!-- A reviewer should be able to read these and say "shipped" or "not shipped". -->
|
||||
|
||||
- [ ]
|
||||
- [ ]
|
||||
- [ ]
|
||||
|
||||
## Alternatives considered
|
||||
|
||||
<!-- 1–2 sentences each. "Do nothing" is always one alternative — say why it's worse. -->
|
||||
|
||||
## Linked milestone
|
||||
|
||||
<!-- Optional. If this maps to an existing milestone in IMPLEMENTATION_PLAN.md, link it.
|
||||
If it doesn't, that's a signal the plan needs an update. -->
|
||||
|
||||
M13.1 — or **new milestone needed**
|
||||
|
||||
## Out of scope
|
||||
|
||||
<!-- Things this issue explicitly does NOT cover, so reviewers don't expand the scope. -->
|
||||
|
||||
## Open questions
|
||||
|
||||
<!-- Things to resolve before implementation can start. -->
|
||||
Reference in New Issue
Block a user