Rebuild Vibeflow as an n8n safety gate

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,22 @@
+name: Bug report
+description: Report incorrect CLI behavior
+title: "bug: "
+labels: [bug]
+body:
+  - type: textarea
+    attributes:
+      label: Minimal workflow
+      description: Attach an anonymized workflow or the smallest JSON that reproduces the problem. Never include credentials.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Command and output
+      render: shell
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Vibeflow and Node.js versions
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,28 +0,0 @@
----
-name: Bug report
-about: Report a problem in behavior, docs, examples, or packaging
----
-
-## Summary
-
-Describe the bug.
-
-## Expected behavior
-
-What should have happened?
-
-## Actual behavior
-
-What happened instead?
-
-## Where it appears
-
-- [ ] docs
-- [ ] prompt / skill behavior
-- [ ] examples
-- [ ] client guide
-- [ ] recipes
-
-## Additional context
-
-Add logs, screenshots, or reproduction notes.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
-blank_issues_enabled: true
+blank_issues_enabled: false
 contact_links:
-  - name: Questions and setup help
-    url: https://github.com/OWNER/REPO/discussions
-    about: Use Discussions for setup questions, ideas, and help requests.
+  - name: Private security report
+    url: https://github.com/domfelipe/vibeflow-n8n/security/advisories/new
+    about: Report vulnerabilities and sensitive findings privately.

.github/ISSUE_TEMPLATE/false-positive.yml

@@ -0,0 +1,23 @@
+name: False positive
+description: Report a policy finding that should not fire
+title: "false-positive: "
+labels: [false-positive]
+body:
+  - type: input
+    attributes:
+      label: Rule ID
+      placeholder: VF006
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Anonymized workflow fragment
+      description: Include relevant nodes and connections without secrets or customer data.
+      render: json
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Why the workflow is safe
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +0,0 @@
----
-name: Feature request
-about: Suggest an improvement, new recipe, or new client support idea
----
-
-## Summary
-
-Describe the improvement.
-
-## Why it matters
-
-What problem does it solve?
-
-## Proposed shape
-
-Describe your preferred implementation.
-
-## Additional context
-
-Links, examples, or related tools.

.github/ISSUE_TEMPLATE/good-first-issue.md

@@ -1,25 +0,0 @@
----
-name: Good first issue
-about: Template for starter tasks to help new contributors join the project.
-title: "[good first issue] "
-labels: ["good first issue"]
-assignees: []
----
-
-## Goal
-
-Describe the task in one or two sentences.
-
-## Why it matters
-
-Explain how this improves the project.
-
-## Acceptance criteria
-
-- [ ]
-- [ ]
-- [ ]
-
-## Helpful context
-
-Add links, files, or examples that make this easier to complete.

.github/ISSUE_TEMPLATE/rule-proposal.yml

@@ -0,0 +1,33 @@
+name: Policy rule proposal
+description: Propose a deterministic check backed by exported workflow JSON
+title: "rule: "
+labels: [enhancement]
+body:
+  - type: textarea
+    id: failure
+    attributes:
+      label: Production failure
+      description: What concrete failure would this rule prevent?
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Static evidence
+      description: Which exported JSON fields prove the unsafe and safe cases?
+    validations:
+      required: true
+  - type: textarea
+    id: fixtures
+    attributes:
+      label: Minimal fixtures
+      description: Paste anonymized unsafe and safe examples, or link to a branch containing them.
+    validations:
+      required: true
+  - type: textarea
+    id: false-positives
+    attributes:
+      label: False-positive boundary
+      description: When should this rule deliberately stay silent?
+    validations:
+      required: true