froid-loop 0.11.1__tar.gz

froid_loop-0.11.1/.bandit

@@ -0,0 +1,14 @@
+# Bandit configuration (read by trunk via `bandit --ini .bandit`).
+#
+# froid-loop is a deterministic orchestrator: it shells out to tmux and coding-CLI
+# binaries by design, and uses `assert` for internal type-narrowing invariants.
+# Skip the low-severity rules those patterns trip so the signal isn't drowned out.
+# Higher-signal checks stay ON — notably B602 (subprocess with shell=True), which is
+# acknowledged at its single legitimate call site with an inline `# nosec B602`.
+#
+#   B101  assert_used            - intentional type-narrowing / invariant asserts
+#   B404  import_subprocess      - the orchestrator drives external processes
+#   B603  subprocess_without_shell_equals_true - args are built internally, not user input
+#   B607  start_process_with_partial_path       - relies on PATH to find tmux/CLIs
+[bandit]
+skips = B101,B404,B603,B607

froid_loop-0.11.1/.claude-plugin/marketplace.json

@@ -0,0 +1,26 @@
+{
+  "name": "froid-loop",
+  "owner": {
+    "name": "cordya-ai"
+  },
+  "license": "MIT",
+  "homepage": "",
+  "repository": "https://github.com/cordya-ai/froid-loop",
+  "keywords": ["froid", "froid-loop", "automation"],
+  "plugins": [
+    {
+      "name": "froid-loop",
+      "source": "./src/froid_loop/data/skills",
+      "description": "Automation-mode skills driven by the froid-loop orchestrator: project bootstrap (froid-loop-setup), interactive escalation resolution (froid-loop-resolve) and deferred-work sweep triage (froid-loop-sweep) — the inner dev primitive (which self-reviews and commits) is the upstream froid-dev-auto skill",
+      "version": "0.11.1",
+      "author": {
+        "name": "pinkyd"
+      },
+      "skills": [
+        "./src/froid_loop/data/skills/froid-loop-setup",
+        "./src/froid_loop/data/skills/froid-loop-resolve",
+        "./src/froid_loop/data/skills/froid-loop-sweep"
+      ]
+    }
+  ]
+}

froid_loop-0.11.1/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+the official FROID Discord server (<https://discord.com/invite/gk8jAdXWmj>) - DM a moderator or flag a post.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.

froid_loop-0.11.1/.github/FUNDING.yaml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: froid
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

froid_loop-0.11.1/.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -0,0 +1,139 @@
+name: Bug Report
+description: File a bug report to help us improve froid-loop
+title: "[BUG] "
+labels: bug
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug report! Please fill out the information below to help us reproduce and fix the issue.
+
+        Running `froid-loop diagnose --out diag.md` produces a **sanitized** dump (no code, specs, prompts, paths, or PII) that helps us debug — please attach it below. **Review it first** and confirm it contains nothing private.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Clear and concise description of what the bug is
+      placeholder: e.g., When I start a run, the loop hangs after the dev session ends
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: Step-by-step instructions to reproduce the behavior
+      placeholder: |
+        1. Run 'froid-loop run <story-key>'
+        2. Watch the TUI / journal
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: What you expected to happen
+      placeholder: The run should advance to the review stage
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+      description: What actually happened
+      placeholder: The run stalled with no further journal output
+    validations:
+      required: true
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: Add screenshots if applicable (paste images directly)
+      placeholder: Paste any relevant screenshots here
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Which area is this for?
+      description: Select the part of froid-loop this issue relates to
+      options:
+        - Orchestrator / control loop
+        - TUI (dashboard)
+        - Plugins
+        - Skills (froid-loop-*)
+        - CLI adapters & profiles
+        - Setup / init
+        - Not sure / Other
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: froid-loop Version
+      description: "Check with: froid-loop --version"
+      placeholder: e.g., 0.5.1
+    validations:
+      required: true
+
+  - type: dropdown
+    id: cli
+    attributes:
+      label: Which coding CLI are you using?
+      options:
+        - Claude (claude)
+        - Codex (codex)
+        - Gemini (gemini)
+        - Cursor (cursor)
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: Operating System
+      description: On WSL, run `froid-loop mux` and read the `selection:` line — `platform default for linux`
+        is the supported setup, `platform default for win32` means you are on the Windows build
+        and should say so below. A forced `FROID_LOOP_MUX_BACKEND`/`[mux] backend` choice replaces
+        that line with the forced reason; `froid-loop diagnose` reports `sys.platform` either way.
+      options:
+        - macOS
+        - Windows
+        - Windows (WSL)
+        - Linux
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Copy and paste any relevant log output (journal, run directory, tmux session)
+      render: shell
+
+  - type: textarea
+    id: diagnostics
+    attributes:
+      label: Diagnostic dump (froid-loop diagnose)
+      description: |
+        Output of `froid-loop diagnose --out diag.md` (add `--all` to cover every run; `--json --out diag.json` writes a machine-readable JSON document instead of the markdown report). **Drag-and-drop the written file here** (or paste its contents). It's sanitized — identifiers are pseudonymized and the output is re-scanned by a fail-closed leak check before it's written — but **no scrubber is perfect**: open the file and verify it contains no PII, secrets, or project-specific content before attaching.
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Confirm
+      options:
+        - label: I've searched for existing issues
+          required: true
+        - label: If I attached a diagnose dump, I reviewed it and confirmed it contains no PII, secrets, or project-specific information
+          required: false
+        - label: I'm using the latest version
+          required: false

froid_loop-0.11.1/.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📚 Documentation
+    url: https://docs.froid-plane.org
+    about: Check the docs first — tutorials, guides, and reference
+  - name: 💬 Discord Community
+    url: https://discord.gg/gk8jAdXWmj
+    about: Join for questions, discussion, and help before opening an issue
+  - name: 🛠 Troubleshooting — run `froid-loop diagnose`
+    url: https://github.com/cordya-ai/froid-loop/blob/main/README.md#contributing
+    about: Before filing a bug, run `froid-loop diagnose` and attach the sanitized dump — and verify it has no PII first

froid_loop-0.11.1/.github/ISSUE_TEMPLATE/documentation.yaml

@@ -0,0 +1,55 @@
+name: Documentation
+description: Report issues or suggest improvements to documentation
+title: "[DOCS] "
+labels: documentation
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Help us improve the froid-loop documentation!
+
+  - type: dropdown
+    id: doc-type
+    attributes:
+      label: What type of documentation issue is this?
+      options:
+        - Error or inaccuracy
+        - Missing information
+        - Unclear or confusing
+        - Outdated content
+        - Request for new documentation
+        - Typo or grammar
+    validations:
+      required: true
+
+  - type: textarea
+    id: location
+    attributes:
+      label: Documentation location
+      description: Where is the documentation that needs improvement?
+      placeholder: e.g., docs/setup-guide.md, or "In the README Quick start section"
+    validations:
+      required: true
+
+  - type: textarea
+    id: issue
+    attributes:
+      label: What's the issue?
+      description: Describe the documentation issue in detail
+      placeholder: e.g., Step 3 says to run command X but it should be command Y
+    validations:
+      required: true
+
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Suggested improvement
+      description: How would you like to see this improved?
+      placeholder: e.g., Change the command to X and add an example
+
+  - type: input
+    id: version
+    attributes:
+      label: froid-loop Version (if applicable)
+      placeholder: e.g., 0.5.1

froid_loop-0.11.1/.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,22 @@
+---
+name: Feature Request
+about: Suggest an idea or new feature
+title: ''
+labels: ''
+assignees: ''
+---
+
+**Describe your idea**
+A clear and concise description of what you'd like to see added or changed.
+
+**Why is this needed?**
+Explain the problem this solves or the benefit it brings to the froid-loop community.
+
+**How should it work?**
+Describe your proposed solution. If you have ideas on implementation, share them here.
+
+**PR**
+If you'd like to contribute, please indicate you're working on this or link to your PR. Please review [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
+
+**Additional context**
+Add any other context, screenshots, or links that help explain your idea.

froid_loop-0.11.1/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+## What
+
+<!-- 1-2 sentences describing WHAT changed -->
+
+## Why
+
+<!-- 1-2 sentences explaining WHY this change is needed -->
+<!-- Fixes `#issue_number` (if applicable) -->
+
+## How
+
+<!-- 2-3 bullets listing HOW you implemented it -->
+
+-
+
+## Testing
+
+<!-- 1-2 sentences on how you tested this -->
+
+## Changelog
+
+<!-- Entry added under `## [Unreleased]` in CHANGELOG.md, under one of: Added, Changed,
+     Deprecated, Removed, Fixed, Security. Write "n/a" if nothing user-visible changed. -->

froid_loop-0.11.1/.github/dependabot.yml

@@ -0,0 +1,22 @@
+version: 2
+updates:
+  # Keep the pinned GitHub Actions majors current.
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: ci
+
+  # Security advisories only, for the Python dependencies in uv.lock.
+  # `open-pull-requests-limit: 0` switches off routine version-update PRs;
+  # security updates are exempt from the limit and still open. Version pins here
+  # are deliberate (pyright is pinned exactly so CI and contributors run one
+  # version), so a weekly bump stream would be noise — an advisory is not.
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 0
+    commit-message:
+      prefix: chore