ouroboros-ai 0.26.2.dev21__tar.gz → 0.26.2.dev26__tar.gz

ouroboros_ai-0.26.2.dev26/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,106 @@
+name: Bug report
+description: Report a reproducible problem in Ouroboros
+title: "[Bug] "
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Actionable bug issues in Ouroboros should be detailed enough for someone else to reproduce and verify a fix.
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Describe the bug in one or two sentences.
+      placeholder: What is broken?
+    validations:
+      required: true
+  - type: textarea
+    id: impact
+    attributes:
+      label: Impact
+      description: Explain why this matters and who or what is blocked, broken, or confused by it.
+      placeholder: Why does this bug matter?
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Include the environment details needed to reason about the bug.
+      placeholder: |
+        - Ouroboros version (ouroboros --version):
+        - OS:
+        - Python version:
+        - Installation method:
+        - Model/provider:
+        - Relevant flags or config:
+    validations:
+      required: true
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: Provide a clear sequence someone else can follow.
+      placeholder: |
+        1. 
+        2. 
+        3. 
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: Describe what should happen.
+      placeholder: What did you expect instead?
+    validations:
+      required: true
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+      description: Describe what happened instead.
+      placeholder: What actually happened?
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs or error output
+      description: Paste the most relevant output here.
+      render: text
+    validations:
+      required: false
+  - type: textarea
+    id: repro
+    attributes:
+      label: Minimal reproduction
+      description: Include the smallest seed, command, or config needed to reproduce the issue if possible.
+      placeholder: Minimal repro steps, config, or seed
+    validations:
+      required: false
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria for fix
+      description: List the concrete conditions that will be true once this bug is fixed.
+      placeholder: |
+        - [ ] 
+        - [ ] 
+    validations:
+      required: false
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I searched existing issues before opening this report.
+          required: true
+        - label: I can reproduce this on the latest main branch or latest release.
+          required: true
+        - label: I included clear reproduction steps.
+          required: true
+        - label: I included enough detail for someone else to verify the fix.
+          required: true

ouroboros_ai-0.26.2.dev26/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: GitHub Discussions
+    url: https://github.com/Q00/ouroboros/discussions
+    about: Ask questions, share ideas, or start open-ended conversations here.
+  - name: Discord
+    url: https://discord.gg/8cW7Wfxnpu
+    about: Chat with the community and maintainers in real time.

ouroboros_ai-0.26.2.dev26/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,114 @@
+name: Feature request
+description: Propose a new feature or workflow improvement
+title: "[Feature] "
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Lightweight structure helps both humans and tooling understand a proposal quickly.
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: Describe the user, maintainer, or workflow problem that exists today.
+      placeholder: What problem exists right now?
+    validations:
+      required: true
+  - type: textarea
+    id: why-now
+    attributes:
+      label: Why now
+      description: Explain why this is worth doing now.
+      placeholder: Why is this worth doing now?
+    validations:
+      required: false
+  - type: textarea
+    id: persona
+    attributes:
+      label: User / persona
+      description: Describe who is affected by this problem.
+      placeholder: Who is affected?
+    validations:
+      required: false
+  - type: textarea
+    id: current
+    attributes:
+      label: Current behavior
+      description: Describe what happens today.
+      placeholder: What happens today?
+    validations:
+      required: false
+  - type: textarea
+    id: desired
+    attributes:
+      label: Desired behavior
+      description: Describe what should happen instead.
+      placeholder: What should happen instead?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: Explain how you think this should work.
+      placeholder: What is your proposed solution?
+    validations:
+      required: false
+  - type: textarea
+    id: constraints
+    attributes:
+      label: Constraints
+      description: List technical, UX, policy, cost, or compatibility constraints.
+      placeholder: What boundaries or constraints matter here?
+    validations:
+      required: false
+  - type: textarea
+    id: non-goals
+    attributes:
+      label: Non-goals
+      description: Explain what is explicitly out of scope for this issue.
+      placeholder: What is this issue not trying to solve?
+    validations:
+      required: false
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: List other approaches you considered.
+      placeholder: What other approaches did you consider?
+    validations:
+      required: false
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      description: List specific, testable statements that define done.
+      placeholder: |
+        - [ ] 
+        - [ ] 
+        - [ ] 
+    validations:
+      required: true
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Add mockups, examples, related issues, PRs, docs, or screenshots.
+      placeholder: Links, screenshots, references, or related issues
+    validations:
+      required: false
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I searched existing issues and discussions first.
+          required: true
+        - label: I explained the problem, not just the solution.
+          required: false
+        - label: I included clear scope boundaries and non-goals.
+          required: false
+        - label: I listed concrete acceptance criteria.
+          required: true

ouroboros_ai-0.26.2.dev26/.github/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,58 @@
+name: Question or usage help
+description: Ask an actionable question when GitHub Discussions is not a better fit
+title: "[Question] "
+labels:
+  - question
+body:
+  - type: markdown
+    attributes:
+      value: |
+        For open-ended discussion or general community chat, prefer GitHub Discussions or Discord.
+  - type: textarea
+    id: question
+    attributes:
+      label: Question
+      description: Explain what you are trying to do.
+      placeholder: What are you trying to do?
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      description: Include the details needed for someone else to help.
+      placeholder: |
+        - Command or workflow:
+        - Seed or config involved:
+        - Expected outcome:
+        - What you already tried:
+    validations:
+      required: true
+  - type: textarea
+    id: output
+    attributes:
+      label: Relevant output
+      description: Paste any relevant output, errors, or logs.
+      render: text
+    validations:
+      required: false
+  - type: textarea
+    id: actionable
+    attributes:
+      label: Why this should be a GitHub issue
+      description: Explain why this looks actionable for maintainers rather than a general discussion question.
+      placeholder: Why should maintainers track this as an issue?
+    validations:
+      required: true
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I checked the README and docs first.
+          required: true
+        - label: I searched existing issues and discussions.
+          required: true
+        - label: I included enough context for someone else to help.
+          required: true
+

ouroboros_ai-0.26.2.dev26/CODE_OF_CONDUCT.md

@@ -0,0 +1,33 @@
+# Code of Conduct
+
+Ouroboros is built around rigorous thinking, iteration, and care. We want the community to feel precise without becoming hostile.
+
+## Core expectations
+
+- Question assumptions, not people.
+- Seek clarity without humiliation.
+- Prefer root causes over blame.
+- Critique ideas with precision and care.
+- Leave each cycle better than you found it.
+
+## Unacceptable behavior
+
+- Harassment, intimidation, or abuse
+- Personal attacks or demeaning language
+- Publishing private information without permission
+- Dogpiling, baiting, or repeated bad-faith engagement
+- Conduct that makes the project unsafe for contributors or users
+
+## Enforcement
+
+Project maintainers may remove, edit, or reject comments, commits, code, issues, pull requests, and other contributions that do not align with this Code of Conduct.
+
+## Reporting
+
+For conduct-sensitive reports, email **jqyu.lee@gmail.com** directly. This is the private reporting path.
+
+If no private path is available, open a GitHub issue titled "Conduct report" and include only the minimum information needed to route the report. Do **not** include private personal details, doxxing content, or anything that would further harm the affected person.
+
+## Scope
+
+This Code of Conduct applies to repository discussions, issues, pull requests, code review, and related community spaces associated with Ouroboros.

{ouroboros_ai-0.26.2.dev21 → ouroboros_ai-0.26.2.dev26}/CONTRIBUTING.md

@@ -52,6 +52,7 @@ uv run pytest tests/unit/ -q # run tests
 - Check [GitHub Issues](https://github.com/Q00/ouroboros/issues) for open tasks
 - For new features, open an issue first to discuss the approach
 - Label your issue with appropriate tags: `bug`, `enhancement`, `documentation`, etc.
+- Treat actionable issues as structured work artifacts, not casual notes. See [Issue Quality Policy](./docs/contributing/issue-quality-policy.md).
 
 ### 2. Branch
 
@@ -114,13 +115,20 @@ uv run mypy src/ouroboros
 Found a bug? Please open an issue with:
 
 1. **Clear title**: Summarize the bug
-2. **Description**: Steps to reproduce, expected vs actual behavior
-3. **Environment**: Python version, OS, `uv run ouroboros --version`
-4. **Logs**: Relevant error messages or stack traces
+2. **Impact**: Explain what is blocked or broken
+3. **Description**: Steps to reproduce, expected vs actual behavior
+4. **Acceptance criteria**: State what will be true once fixed
+5. **Environment**: Python version, OS, `uv run ouroboros --version`
+6. **Logs**: Relevant error messages or stack traces
 
-```markdown
-## Bug Description
-[What went wrong]
+See the [Issue Quality Policy](./docs/contributing/issue-quality-policy.md) for the full bug issue standard.
+
+````markdown
+## Summary
+[What is broken]
+
+## Impact
+[Why this matters]
 
 ## Steps to Reproduce
 1. Run `ooo interview "test"`
@@ -130,6 +138,12 @@ Found a bug? Please open an issue with:
 ## Expected Behavior
 [What should happen]
 
+## Actual Behavior
+[What happens instead]
+
+## Acceptance Criteria for Fix
+- [ ] [Condition that proves the bug is fixed]
+
 ## Environment
 - Python: 3.12+
 - Ouroboros: v0.9.0
@@ -139,16 +153,24 @@ Found a bug? Please open an issue with:
 ```
 [paste error output]
 ```
-```
+````
 
 ### Feature Proposals
 
-Have an idea? Open an issue with:
+Have an idea? Open an issue only when it is structured enough to act on.
 
-1. **Problem statement**: What problem does this solve?
-2. **Proposed solution**: How should it work?
-3. **Alternatives considered**: What other approaches did you think about?
-4. **Scope**: Is this a breaking change? Can it be incremental?
+Feature issues should be written in a **PRD-lite** format with:
+
+1. **Problem**: What problem exists today?
+2. **Why now**: Why is this worth doing now?
+3. **User / persona**: Who is affected?
+4. **Current vs desired behavior**: What changes?
+5. **Constraints and non-goals**: What boundaries matter?
+6. **Acceptance criteria**: What would make this done?
+
+If the idea is still fuzzy, use GitHub Discussions or Discord first, then turn it into a structured issue.
+
+See the [Issue Quality Policy](./docs/contributing/issue-quality-policy.md) for the full feature issue standard.
 
 ### Pull Requests
 
@@ -721,11 +743,15 @@ ls skills/*.yaml 2>/dev/null || echo "No skill YAML files found"
 
 - **GitHub Issues**: [Report bugs or request features](https://github.com/Q00/ouroboros/issues)
 - **GitHub Discussions**: [Ask questions or share ideas](https://github.com/Q00/ouroboros/discussions)
+- **Security Reports**: See [SECURITY.md](./SECURITY.md) before reporting vulnerabilities
+- **Community Conduct**: See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md)
 
 ---
 
 ## Code of Conduct
 
+The canonical community rules live in [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
+
 ### Our Pledge
 
 We pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

{ouroboros_ai-0.26.2.dev21 → ouroboros_ai-0.26.2.dev26}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ouroboros-ai
-Version: 0.26.2.dev21
+Version: 0.26.2.dev26
 Summary: Specification-first workflow engine for AI coding agents. Works with Claude Code and Codex CLI.
 Author-email: Q00 <jqyu.lee@gmail.com>
 License-File: LICENSE

{ouroboros_ai-0.26.2.dev21 → ouroboros_ai-0.26.2.dev26}/docs/README.md

@@ -43,6 +43,8 @@ Ouroboros is a specification-first workflow engine for AI coding agents. It tran
 - [Testing Guide](./contributing/testing-guide.md) - Writing and running tests
 - [Key Patterns](./contributing/key-patterns.md) - Result type, immutability, event sourcing, protocols
 - [Findings Registry](./contributing/findings-registry.md) - Documentation audit findings registry
+- [Issue Quality Policy](./contributing/issue-quality-policy.md) - Quality bar for actionable issues and PRD-lite feature requests
+
 
 ## Key Concepts
 

ouroboros_ai-0.26.2.dev26/docs/contributing/issue-quality-policy.md

@@ -0,0 +1,29 @@
+# Issue Quality Policy
+
+This document explains why Ouroboros prefers structured GitHub issues.
+
+GitHub is the source of truth for actionable work. Clear issues help maintainers, contributors, and future tooling understand what problem exists, what success looks like, and whether something is ready to implement.
+
+## What we prefer
+
+- Bug reports should make reproduction and verification possible.
+- Feature requests should explain the problem, the desired outcome, and what “done” looks like.
+- Exploratory ideas should usually start in Discussions or Discord before becoming implementation issues.
+
+## Why this matters
+
+- Better issue quality reduces clarification churn and off-target PRs.
+- Structured issues are easier for both humans and tooling to read.
+- Ambiguous issues are hard to review, scope, and verify safely.
+
+## Practical guidance
+
+- For bugs, include enough detail for someone else to reproduce the problem.
+- For features, focus on the problem and acceptance criteria before debating implementation details.
+- If an idea is still fuzzy, discuss it first and turn it into a GitHub issue once it is actionable.
+
+## Maintainer guidance
+
+- Ask for the minimum missing structure rather than rejecting an idea outright.
+- Redirect open-ended brainstorming to Discussions or Discord when needed.
+- Avoid starting implementation from issues that are too vague to verify.

{ouroboros_ai-0.26.2.dev21 → ouroboros_ai-0.26.2.dev26}/src/ouroboros/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.26.2.dev21'
-__version_tuple__ = version_tuple = (0, 26, 2, 'dev21')
+__version__ = version = '0.26.2.dev26'
+__version_tuple__ = version_tuple = (0, 26, 2, 'dev26')
 
 __commit_id__ = commit_id = None