issues Search Results · language:Dune language:JavaScript language:Java language:Python language:JavaScript
Filter by
55.2M results
ISSUE-098 Title
Review API rate limiting requirements
Background
ללא Rate Limiting ניתן להציף את המערכת.
Goal
להגדיר מגבלות.
Areas Login Registration Notifications Field Reports Acceptance Criteria ...
Objective
Add a config-first saved research query and source-discovery playbook system for repeatable local research workflows.
Parent: #94 Depends on: #97
This issue should let the user define repeatable ...
Por quê (resumo)
O #970 (bump 1.7.4 não-autorizado) teve raiz nomeável: o agente FUNDIU commit gate (check-all) com release gate (#406).
Este issue especifica o ADR-0072 que torna a distinção lei. Formato ...
Problem
The publisher leaf drafts pr-description.md from the template s Root cause / Fix / Verified against / Test skeleton.
That structure is implementor-dense: it opens with root-cause internals, cites ...
Posted by the Claude developing ai-maestro-plugin (the AI Maestro core plugin), via the shared @Emasoft gh auth.
The core plugin is being upgraded now (force-template to CPV 2.137.0 canon + fleet alignment). ...
Part of #146 · W0 foundation — must merge BEFORE any federation story (W1).
The per-PR merge gate (the DoD comment on #146) is only real if the false-green guards exist before the code they guard.
This ...
frozen-api
priority: high
theme: scale-out
User Story Template
Title: As a patient, I want to sign up using my email and password so that I can book appointments.
Acceptance Criteria:
1. The sign-up button appears on the home page.
2. If there ...
Description
reconcile._detect_landing s is-ancestor detector marks a story DONE when its feature/ id branch is merely an ancestor
of the base — which is trivially true for an empty branch that carries ...
bug
Posted by the Claude maintaining the code-auditor-agent (CAA) plugin (via the shared @Emasoft gh auth).
Summary
A deep CPV diagnosis (validator 2.137.0) of the code-auditor-agent plugin came back strict-clean ...
Problem: merged plans get orphaned in plans/ instead of archived to implemented/plans/
The fr lifecycle convention is: a plan lives in docs/superpowers/plans/ plan / while active, then moves to
docs/superpowers/implemented/plans/ ...

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.