253 Commits

Author	SHA1	Message	Date
brent.edwards	df8cd4c0a9	chore(merge): merge PR #7586 — fix bug-hunt-pool-supervisor tracking prefix ... Merged PR #7586 from branch improvement/agent-bug-hunt-pool-supervisor-tracking-prefix Resolved conflicts in: - .opencode/agents/bug-hunt-pool-supervisor.md: Accepted incoming version with improved tracking prefix AUTO-BUG-SUP and restructured tracking procedures - CHANGELOG.md: Accepted incoming version with clearer tracking fix documentation The PR fixes the tracking prefix inconsistency, changing from AUTO-BUG-POOL to AUTO-BUG-SUP for consistency with other agents, and improves the tracking issue format with better structured health reports and announcements.	2026-04-20 22:22:01 +00:00
brent.edwards	53d3c18c34	Merge remote-tracking branch 'origin/improvement/agent-ca-test-infra-improver-failure-handling' into chore/merge-batch-1	2026-04-20 15:05:09 -07:00
freemo	435e409df9	build: moved all sonnet agents to haiku	2026-04-18 12:33:27 -04:00
freemo	59a2a83328	build: fixed pr-merge filtering to avoid non-mergable PRs	2026-04-18 01:41:40 -04:00
freemo	bcf58f0703	build: being even more explicit about loading scripts	2026-04-17 18:26:54 -04:00
freemo	37402e83c2	build: fixed some typos regarding script loading via skills	2026-04-17 17:59:04 -04:00
freemo	7c13643441	build: final tweaks to get gpt5-nano working for pr-merge	2026-04-17 17:44:25 -04:00
freemo	4e7bb5ae4e	build: more explicit on how to run the script	2026-04-17 17:27:11 -04:00
freemo	47d630599a	build: further clarified how to get the PRs using the scripts	2026-04-17 17:07:58 -04:00
freemo	6153da8deb	build: trying to improve skill comprehension of scripts	2026-04-17 16:53:33 -04:00
freemo	e8f06fa433	build: made invocation of scripts more explicit	2026-04-17 16:32:37 -04:00
freemo	17bbe20376	Revert "build: adding auto-agents-system as a task as well as a skill." ... This reverts commit 5c8b5a84d2.	2026-04-17 16:28:28 -04:00
freemo	5c8b5a84d2	build: adding auto-agents-system as a task as well as a skill.	2026-04-17 16:19:00 -04:00
freemo	fe95acb856	build: added more clarification for loading scripts	2026-04-17 16:02:21 -04:00
freemo	6ed9dbc2e7	build: expanded capabilities (permissions) of the git rebaser subagent	2026-04-17 15:45:54 -04:00
freemo	555509c609	build: tweaked reasoning level on pr-merge related agents	2026-04-17 15:34:56 -04:00
freemo	aaeecd1616	build: reduced cost of models for merging by picking cheaper models	2026-04-17 15:26:49 -04:00
freemo	868fdeff8a	build: seperated out the actual rebase and conflict resolution to its own specialized subagent	2026-04-17 15:03:24 -04:00
freemo	d6fca18c01	build: broke the 4 stage pr merge cycle into a 6 stage cycle and eliminating PRs that arent stale and need review	2026-04-17 14:20:40 -04:00
freemo	11ba77cf73	build: fix to get mroe predicatable behavior out of pr-merge-worker	2026-04-17 13:35:25 -04:00
freemo	5762f92583	build: tweaked the pr-merge agents to ensure they use the skill scripts more consistently	2026-04-17 13:00:24 -04:00
freemo	afa4ebd19b	build: fixed up the systems skill so it now provides better access to information about scripts to ensure more consistent usage	2026-04-17 12:50:46 -04:00
HAL9000	9bff689212	chore(agents): fix bug-hunt-pool-supervisor tracking prefix AUTO-BUG-POOL → AUTO-BUG-SUP ... Complete the tracking prefix fix by updating all remaining references: - Embedded CREATE_TRACKING_ISSUE call (lines 195-196) - REVIEW_OWN_ANNOUNCEMENTS call (line 219) - CLOSE_ANNOUNCEMENT_ISSUE call (line 225) - Template header from 'Bug Detection Pool Status' to 'Bug Hunt Status' All 8 instances of AUTO-BUG-SUP are now consistent throughout the file. ISSUES CLOSED: #7523	2026-04-17 10:05:29 +00:00
hurui200320	1fda56b778	fix(cli): implement plan diff --correction to show real correction attempt diff ... Implement spec-compliant correction diff output for `agents plan diff --correction <CORRECTION_ATTEMPT_ID>`. Fixes the following issues from the cycle-1 PR review: - C1/M1: Replace direct `unit_of_work.correction_attempts` access with the proper `unit_of_work.transaction()` context manager, eliminating the AttributeError crash and the resource (session) leak. - C2: Add `unit_of_work: UnitOfWork | None = None` constructor parameter to `PlanApplyService` and wire it in `_get_apply_service()` via `container.unit_of_work()`, removing the illegal `get_container()` call inside the method body (ADR-003 DI violation). - C3: Replace metadata serialization stub with a three-section structured diff (Correction Diff summary, Comparison table, Patch Preview) as specified in §agents plan diff of the specification. - C4/M2: Add `features/plan_correction_diff.feature` with 6 BDD scenarios covering all 4 output formats plus plan-not-found and correction-not-found error paths. - C5: Update the three existing BDD scenarios that tested old stub behavior to mock `_get_apply_service()` and assert the new output. - C6: Rename branch to `bugfix/m4-plan-diff-correction-stub` per CONTRIBUTING.md convention. - C7: Amend commit message with body and ISSUES CLOSED footer. - C8: Narrow `except Exception` to `except CorrectionAttemptNotFoundError` to avoid masking programming errors. - M3: Add `robot/plan_correction_diff.robot` and `robot/helper_plan_correction_diff.py` integration test covering rich, plain, and JSON formats and the not-found error path. - M4: Type `_build_correction_diff_dict` parameter as `CorrectionAttemptRecord` instead of `Any`. - M5: Change `fmt: str` to `fmt: Literal["rich", "plain", "json", "yaml"]` on both `diff()` and `correction_diff()`, with a `cast()` call in the CLI layer where Typer supplies a plain `str`. - M6: Add `ValueError` guards for empty `plan_id` and `correction_attempt_id` at the top of `correction_diff()`. - M7: Add blank line between `diff()` and `correction_diff()` method definitions. - M8: Update PR description to reflect actual implementation. - m1: Remove unused `plan` variable in `correction_diff()`. - m2: Reduce three blank lines to two between top-level definitions in `plan_apply_service.py`. - n1: Remove trailing whitespace from blank line in `plan.py`. Quality gates: lint (ruff), typecheck (pyright strict), unit_tests (Behave 632 features / 0 failures) all pass. ISSUES CLOSED: #9085	2026-04-17 08:34:33 +00:00
freemo	ebf54c642c	Build: Attempt to prevent merge workers from waiting till merge completes	2026-04-17 01:23:28 -04:00
freemo	82591c1a86	Build: Trying to fix skill script not being called	2026-04-16 23:27:39 -04:00
freemo	9684d80637	Build: Enabling skill scripts	2026-04-16 23:01:57 -04:00
freemo	6dad967130	Build: fixed systems skill to link to the scripts from the main skill page	2026-04-16 22:41:42 -04:00
freemo	85c22aa7a8	Build: Fixed bug in permissions, sped up product-verifier slightly	2026-04-16 21:58:11 -04:00
freemo	5e3b4c9b68	build: fixed typo in permissions in pr-merge related agents	2026-04-16 20:21:59 -04:00
freemo	588199886e	build: wrong name for auto-agents system skill	2026-04-16 19:53:09 -04:00
freemo	438df82caa	build: changed pr-merge process (including supervisor) to use new skills and scripts	2026-04-16 19:10:04 -04:00
freemo	ac702cc375	build: Added script to initiate the merge	2026-04-16 18:50:59 -04:00
freemo	d3e0911f86	build: added script for rebasing on server to system skill	2026-04-16 18:17:15 -04:00
freemo	703cf13c01	build: removed rules skills, its in the system skill	2026-04-16 18:01:14 -04:00
freemo	a58d17416c	build: added scripts into auto-agents-system skill for getting the PR categories for merging.	2026-04-16 17:59:56 -04:00
freemo	0257841825	Revert "refactor(agents): migrate all agent definitions to use skills for universal rules" ... This reverts commit bb97f1450e.	2026-04-16 14:15:30 -04:00
freemo	bb97f1450e	refactor(agents): migrate all agent definitions to use skills for universal rules ... Replace ~600 chars of verbatim per-agent boilerplate with skill references. All 91 agents now load cleveragents-agent-rules for exhaustive pagination, label management, bot signatures, and credential flow rules. Adds explicit skill: "*": deny + targeted allows to every agent permission block, matching the existing bash: and task: deny-first convention. Tier selectors carry no skill permissions since they are pure pass-through with no skill references in their bodies. forgejo-label-manager also grants forgejo-api for its curl pattern reference.	2026-04-16 01:00:55 -04:00
freemo	dceb0e91d3	docs(skill): add cleveragents-agent-rules universal agent rules skill ... Introduces a new skill containing the complete specification for the five universal operational rules every agent must follow: exhaustive pagination protocol, label management via forgejo-label-manager, bot signature format, credential flow hierarchy, and localhost:4096 restriction.	2026-04-16 01:00:48 -04:00
clever-agent	93c349d531	Build: Stopped using codex for most of our agents	2026-04-16 00:51:51 -04:00
HAL9000	d167155e90	Build: Removed gemini as a model option	2026-04-15 23:43:29 -04:00
freemo	c9dc70004c	docs(skill): add full redundancy and self-healing documentation to cleveragents-system skill ... Add new references/redundancy/README.md (280 lines) covering: - Three-layer redundancy architecture overview (product-builder / watchdog / supervisors) with the key insight that each layer uses a different observation mechanism to prevent blind spots between layers - Layer 1 (product-builder): fast cycle (60s liveness), deep inspection (5-min message reading with anti-pattern catalogue: error loops, circular patterns, policy violations, context exhaustion), worker health check (pool count vs expected), hourly verification - Layer 2 (system-watchdog): independent 5-min audit using Forgejo tracking issue STALENESS rather than OpenCode session status — catches frozen-but-alive sessions that appear healthy to product-builder; session introspection for anti-pattern detection; clear role separation (watchdog detects, product-builder restarts) - Layer 3 (supervisor self-monitoring): per-cycle worker health checks, stuck detection (15-min threshold), completed vs crashed distinction, pool filling - State persistence as the foundation of self-healing: everything externalized to Forgejo (tracking issues, attempt comments, claim protocol, announcements) - Supervisor crash-recovery pattern: session crash → product-builder detects ≤60s → relaunch → READ_TRACKING_STATE first → light/moderate/full recovery based on offline duration → resume from recovered state - Worker crash-recovery pattern: crash → supervisor detects in next cycle → Forgejo evidence check → re-dispatch at same or escalated tier - Two independent health signals table: OpenCode (session presence/status, latency 60s) vs Forgejo (tracking staleness, latency 2×interval) — what each catches - Complete failure mode catalogue (13 failure types with: who detects it, how, recovery action, and whether recovery is automatic or requires human) - async-agent-monitor health classifications: healthy/stuck/idle/finished/errored with threshold and configurable idle_threshold_minutes parameter - Redundancy gaps and limitations: product-builder has no watcher; watchdog detects but cannot restart; worker downtime latency varies by supervisor sleep Expand SKILL.md (539 → 775 lines, 10 → 13 decision trees): - Significantly expand 'Is something wrong?' tree: now lists every failure type with which layer detects it, how detection works, and recovery action (supervisor missing, frozen, error loop, waiting for input, worker crashed, worker frozen, supervisor stopped dispatching, orphaned claim, CI violations, multiple supervisors down, product-builder crash) - Add new 'How does the system self-heal?' tree: full three-layer redundancy decision tree with per-layer mechanics (fast/deep/hourly cadences), the Forgejo persistence foundation, complete supervisor crash-recovery pattern, complete worker crash-recovery pattern, and the single-point-of-failure note - Update Key Numbers table: add worker health check and hourly cycle entries; clarify session health threshold is configurable; add watchdog staleness threshold (2×interval); add supervisor max downtime (≤60s); add worker re-dispatch latency (varies by sleep interval) - Update frontmatter description to cover self-healing and redundancy - Update reference index to describe the new redundancy reference file ISSUES CLOSED: #0	2026-04-15 20:18:54 +00:00
freemo	e1e65c85ae	docs(skill): final cleanup pass — remove remaining duplicated project knowledge, cross-reference other skills ... agent-registry/README.md: - Remove typecheck-fixer 'Never uses type: ignore' rule (contributing rule, lives in cleveragents-contributing not the system registry) - Remove coverage-improver '>=97%' threshold (project-specific threshold, lives in cleveragents-contributing) - Change new-issue-creator description from 'following CONTRIBUTING.md format' to 'following the project issue format' with cross-reference pointer - Remove subtask-loop trivial description; expand to show the full implement → test → quality gates → review loop it manages - Remove duplicate forgejo-label-manager entry ('See above.') — was listed twice in the utility subagents table - Add cross-reference note at top of Utility Subagents section: descriptions focus on system role; project-specific rules (testing philosophy, quality gates, commit standards, issue format) are in cleveragents-contributing - AUTO-IMP-SUP dispatch ordering: add inline cross-reference note pointing to cleveragents-contributing and cleverthis-guidelines for label definitions - AUTO-OWNR description: replace specific label names ('MoSCoW labels', 'Wont Do') with generic role description + cross-reference note SKILL.md: - Reference Index: fix tracking-system entry description — remove 'label rules' (those were removed from tracking-system last pass); replace with accurate description of what the file now covers (Automation Tracking and needs feedback labels as system-specific labels) No system-specific content was removed: all agent prefixes, the full announcement relevancy matrix, worker tag patterns, sleep intervals, worker count formulas, tier system mechanics, tracking system operations, credential propagation hierarchy, and claim/heartbeat/release protocol are fully preserved. ISSUES CLOSED: #0	2026-04-15 20:13:47 +00:00
freemo	e816e1af9e	docs(skill): final pass — expand relevancy matrix, remove duplicated knowledge, cross-reference other skills ... SKILL.md: - Expand 'Which announcements should I consume?' from a partial example (only showed IMP-SUP and said 'use agent-prefix-info for the rest') to the FULL canonical cross-agent attention table: all 17 supervisors plus product-builder, every source prefix with its minimum priority threshold and rationale, universal baseline rule, and rule-of-thumb note - 'How do I apply a label?' tree: replace detailed label scope breakdown (State/, Priority/, MoSCoW/, Type/) and detailed forgejo-label-manager internals with cross-references to cleveragents-contributing and cleverthis-guidelines; keep only system-critical labels (Automation Tracking, needs feedback, Blocked) and the forbidden operations list (which is an agent permission concern unique to this system) - 'How does a supervisor launch a worker?' Step 5: replace 'CONTRIBUTING.md rules (commit standards, testing, PR requirements)' with reference to the cleveragents-contributing skill, noting that product-builder pre-loads these via ref-reader and passes them in briefings - Quick Reference: add explicit pointers to cleveragents-contributing and forgejo-api skills for the label-related lines - Frontmatter description: rewrite Covers section to remove duplicated label scope and forgejo-api curl content; add explicit note that label rules and scopes live in cleveragents-contributing and cleverthis-guidelines, and that curl patterns are in the forgejo-api skill tracking-system/README.md: - Remove entire 'Label Rules (CRITICAL)' section (Never Create Labels, Only Org-Level Labels, Always Use forgejo-label-manager, scope conflict rules) — this is fully covered in cleveragents-contributing - Remove entire 'The forgejo-api Skill and Label Operations' section (paginated org label fetch loop, PUT replace-all curl, DELETE single label curl) — this belongs in the forgejo-api skill which forgejo-label-manager loads automatically - Replace both removed sections with a focused 'System-Specific Labels' section covering only what is unique to the system: Automation Tracking as the universal discovery mechanism and needs feedback as the human escalation signal that stops worker dispatch - Priority labels table: change from defining what each priority level IS (duplicates cleverthis-guidelines) to showing when to use each for autonomous system announcements specifically; add cross-reference note coordination/README.md: - Remove duplicated 'Announcement Relevancy Matrix Quick Reference' table (9 rows covering only some supervisors) — the full authoritative table is now in SKILL.md; replace with a two-sentence pointer to SKILL.md and agent-prefix-info for programmatic lookup ISSUES CLOSED: #0	2026-04-15 20:08:35 +00:00
freemo	2dbcdc80ae	docs(skill): add cleveragents-system self-reflection skill ... New skill covering the complete operational architecture of the CleverAgents autonomous development system — how it runs, not what it builds. SKILL.md (539 lines) with 9 decision trees: - 'What does this agent do?' — prefix-to-agent mapping for all 17+1 supervisors - 'Which supervisor owns this worker?' — reverse lookup from worker tags - 'How many workers can this supervisor run?' — N_FULL/N_HALF/N_QUARTER formula with concrete examples at N=4, N=8, N=16 - 'How does a supervisor launch a worker?' — full dispatch flow including tier selector indirection, model inheritance, and credential inclusion - 'Do I need to launch something asynchronously?' — when/why to use prompt_async vs synchronous calls; why only async-agent-manager calls localhost:4096 - 'How do I apply a label to an issue or PR?' — forbidden operations list; forgejo-label-manager delegation; org-level vs repo-level; never create - 'How do I create a tracking issue or announcement?' — CREATE_TRACKING_ISSUE invariants; READ-then-CREATE startup order; announcement lifecycle - 'Which announcements should I consume?' — full relevancy matrix per agent type - 'How does state recovery work on startup?' — mandatory READ-then-CREATE protocol with urgency tiers based on offline duration - 'Which model tier should I use?' — escalation decision logic with comment parsing - 'How do credentials get to workers?' — env var hierarchy; why workers never read env vars; two bot accounts (primary + reviewer) - 'Is something wrong with the system?' — diagnostic patterns Complete supervisor registry table (17 supervisors + product-builder) with prefixes, agent definitions, worker counts, sleep intervals, and tracking prefixes. Key Numbers table (25 entries covering all timeouts, thresholds, and intervals). Reference files (1,292 lines across 6 files): agent-registry/README.md — full agent hierarchy diagram, all 17 pool supervisor detailed entries (purpose, worker count, sleep, worker tag pattern, special notes), worker-to-supervisor mapping table, utility subagent catalog (35+ entries), shared prompt fragment catalog. async-operations/README.md — why prompt_async exists (fire-and-forget vs blocking); complete OpenCode Server API reference (list sessions, create session, prompt_async, get status, get messages, get specific session, delete session) with curl examples and response shapes; full session naming convention with all supervisor and worker tag patterns in a table; common operations (starting supervisors/workers, checking status, detecting stuck sessions, cleanup); error handling policy (retry 3×). tracking-system/README.md — status vs announcement issue distinction; the one-at-a-time invariant; cycle number uniqueness; rolling average interval formula (0.90×old + 0.10×actual); CREATE_TRACKING_ISSUE step-by-step process; mandatory startup recovery protocol (READ then CREATE, with wrong-order warning); discovery patterns; announcement lifecycle; priority labels for announcements and when to use each; label rules (NEVER create; org-level only; always use forgejo-label-manager; forbidden Forgejo MCP tools list); forgejo-api skill curl patterns for label operations; complete automation-tracking-manager operations table. tier-system/README.md — four model tiers (haiku/codex/sonnet/opus) with model IDs, cost ranks, and use cases; how tier selectors work (pass-through inheritance mechanism, full call chain diagram); progressive escalation decision table; reading escalation history from attempt comments; human escalation trigger (Opus×3 same-problem) and steps; default model assignments for all agents grouped by model; runtime Gemini 2.5 Pro overrides. credential-flow/README.md — all environment variables with required/optional/ default columns; auto-detection of FORGEJO_URL/OWNER/REPO from git remote; credential hierarchy diagram; two bot accounts (primary vs reviewer) and why; worker credential rules (NEVER read env vars; everything from prompt); what a supervisor must include in every worker prompt; CA_MAX_PARALLEL_WORKERS formula with examples at N=1/4/8/16; security notes. coordination/README.md — claim protocol (CLAIM/HEARTBEAT/RELEASE comment prefixes); claim lifecycle; expiry (2 hours without heartbeat); availability check algorithm; exact comment formats for all three types; PR work conflict matrix (code-change vs merge-attempt vs review); session-level deduplication via tag search (primary mechanism); system-watchdog monitoring of violations; startup deduplication by product-builder; bot signature formats; announcement relevancy matrix quick reference table. ISSUES CLOSED: #0	2026-04-15 20:00:13 +00:00
freemo	47b4c5fbfb	docs(skill): final pass — 2 new trees, expanded trees, reference file completions ... SKILL.md (1,878 → 2,099 lines, 23 → 25 decision trees): New 'Is my work done?' tree — comprehensive Definition of Done checklist synthesising all requirements across implementation, three-level testing (unit/integration/benchmarks), coverage ≥ 97%, five CI quality checks, commit anatomy (atomic, body, footer), documentation (changelog, docstrings, CONTRIBUTORS.md), PR fields (description, dep direction, Epic scope, milestone, Type label), CI checks, and issue state transitions. New 'What design pattern should I use?' tree — all 24 patterns from CONTRIBUTING.md categorised across Creational (Factory, Abstract Factory, Builder, Prototype, Singleton, Object Pool, DI), Structural (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy, Module), Behavioral (Chain of Responsibility, Command, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, Visitor, Null Object), and Architectural (Repository, Unit of Work, Service Layer, MVC, CQRS, Event Sourcing, Specification). Every pattern includes a when-to-use description and a CleverAgents-specific example. Expand 'Am I about to write code?' — link to new patterns tree. Expand 'Am I writing tests?' — add And/But/Outline Gherkin keywords with examples, add Scenario Outline explanation, add naming good/bad examples with anti-pattern list, expand integration test guidance with what good integration tests exercise (CLI, DB, filesystem, service layer), expand Hypothesis section with 6 specific use cases and recommended strategies to build. Expand 'Am I about to commit?' — improve commit body guidance with a worked example showing what to write (context, why this approach, risks, caveats). Expand 'Am I triaging?' — add Epic/Legendary triage rules (no point estimates, no milestone assignment, sign-off labels required for closure). Add two branches to master decision tree for new trees. Reference files: references/testing/README.md (187 → 296 lines): - Add Gherkin Quality Guidelines section: Given/When/Then semantics table, Scenario Outline explanation with example, naming rules with good/bad table, common anti-patterns (implementation details, multiple behaviors, missing Then) - Add Property-Based Testing (Hypothesis) section: when-to-use table with 6 specific CleverAgents use cases, recommended strategies to build, integration with Behave step definitions with worked example references/langchain-langgraph/README.md (307 → 375 lines): - Add RxPY Reactive Streams section: Subject vs BehaviorSubject vs ReplaySubject decision table with when-to-use and code examples, key operators table with use cases and code examples, backpressure management patterns (debounce vs throttle_first with examples), and clear list of what RxPY is NOT for references/toolchain/README.md (271 → 272 lines): - Add Hypothesis to tool table (property-based testing, nox -s unit_tests) references/ci-cd/README.md (124 → 131 lines): - Fix project-specific version number in release example (v3.6.0 → generic v<MAJOR>.<MINOR>.<PATCH>) - Add release failure recovery procedure (verify secrets → build locally → delete tag → fix → re-tag) ISSUES CLOSED: #0	2026-04-15 19:40:35 +00:00
freemo	05e4f7446c	docs(skill): expand cleveragents-contributing SKILL.md — 5 new trees, all trees deepened ... Add 5 new decision trees: 'Should this be an Issue, Epic, or Legendary?' — hierarchy decision with one-commit test, demonstrable-capability test, strategic-pillar test, promotion/demotion rules, and quick self-test questions. 'Is this ticket well-scoped?' — all 11 quality criteria from CONTRIBUTING.md (Atomicity, Single Commit, Single Responsibility, Assignability, Verifiability, Self-Containment, Implementation Independence, Subtask Decomposition, Leaf Node, Mandatory Parent, Finite Completion) each with pass/fail test. 'What ticket state should this be in?' — full lifecycle state machine (Unverified → Verified → In progress → Paused → In review → Completed → Wont Do) with who can perform each transition and what labels are required. 'Am I triaging a ticket?' — maintainer triage 7-step process (duplicate check, validity assessment, completeness check, label assignment, milestone assignment, parent linking, bug companion TDD issue check). 'What branch name should I use?' — branch naming rules with all prefixes (feature/mN-, bugfix/mN-, tdd/mN-), source of milestone number N, kebab- case rules, traceability requirement (shared suffix between tdd/ and bugfix/ branches), and examples. Expand existing trees: 'Am I creating an issue?' — add 11 quality criteria summary, better acceptance criteria examples (good vs bad), note on Metadata section verbatim requirements. 'Am I about to write code?' — add SOLID principle explanations per letter, add WIP management section (git stash vs draft commits), add ADR step detail. 'Am I about to commit?' — add cosmetic-first-then-functional guidance, expand commit hygiene section with interactive rebase detail and goal of clean history (no wip commits). 'Am I submitting a PR?' — add post-submission CI failure handling (new commit not force-push), add major-change review handling (address every comment). 'Am I reviewing a PR?' — add blocking vs suggestion vs question comment distinction with examples, add approve-with-suggestions pattern, add no-wip- commits check in commit quality section. 'Am I writing tests?' — add integration vs e2e distinction (integration = real services; e2e = real LLM API keys), add Gherkin quality guidelines (Given/When/Then semantics, scenario naming, one behavior per scenario), add Hypothesis property-based testing section, expand test failure remediation to include real-bug-triggers-TDD-workflow path. 'Am I looking at a CI failure?' — add integration_tests failure diagnosis, add guidance for when unit test failure reveals a real bug (triggers full TDD workflow), expand benchmark-regression failure guidance. 'Am I documenting something?' — add CHANGELOG entry format (good vs bad examples), add ADR document structure (Title/Status/Context/Decision/ Consequences/Alternatives). 'Am I writing LangChain/LangGraph code?' — add RxPY reactive streams section (Subject, BehaviorSubject, ReplaySubject, operators, backpressure). 'Am I releasing a new version?' — add 'when to bump' section noting most PRs don't need bumps, add release failure recovery procedure (delete tag, fix, re-tag). Update master decision tree to add 5 new branches. Update Key Numbers table: add benchmark regression threshold (10%), cyclomatic complexity limit (>10), Hypothesis entry, benchmark regression threshold, issue quality criteria count, bug priority rule, TDD assignee preference. Update frontmatter to document new coverage. ISSUES CLOSED: #0	2026-04-15 19:32:10 +00:00
freemo	5a24b5bdf2	docs(skill): add cleveragents-spec skill from docs/specification.md ... New skill covering every architectural concept, entity, workflow, CLI command, and design decision from docs/specification.md (47,181 lines read in full). Explains WHAT the system is intended to build. SKILL.md (1,282 lines) — 18 decision trees: - 'What am I working on?' master routing tree - 'What is a Plan?' — 4 phases, reversion rules, hierarchy, decision tree - 'How does a plan run?' — step-by-step Action→Strategize→Execute→Apply - 'What is a Decision?' — 10 types, data model, dual tree+DAG structure, timing by phase, decision recording protocol - 'How do I correct a plan?' — revert vs append modes, Strategize vs Execute correction mechanics, affected subtree computation - 'What is an Invariant?' — 4 scopes, precedence chain (plan>action> project>global), non-overridable globals, Invariant Reconciliation Actor - 'What is an Actor?' — LLM vs graph types, Jinja2+env-var preprocessing, specialized roles (strategy/execution/estimation/invariant) - 'What is a Tool?' — 4 sources, capability metadata, 4-stage lifecycle, resource bindings and slots, anonymous tools, metadata overrides - 'What is a Validation?' — Tool subtype, always read-only, required vs informational modes, 3 attachment scopes, wrapping existing tools - 'What is a Skill?' — composition patterns, includes, tool overrides - 'What is a Resource?' — physical vs virtual, 34+ built-in types, DAG, type inheritance, 5-sandbox strategies, 6-level execution env routing, devcontainer auto-discovery and lazy activation - 'What is a Project?' — resource linking, multi-project plans, context config, execution environment - 'Which automation profile applies?' — 8 built-in profiles, 11 flags, Safety Profile, Automation Guard, Semantic Escalation, progressive trust - 'How does naming work?' — namespace format, types, ULID vs name identity - 'Which CLI command do I use?' — every command group with key flags - 'What is the architecture?' — 4 layers, 2 deployment modes, A2A protocol (full method routing, error codes, streaming), DI container - 'What is the ACMS?' — UKO, CRP, 10-slot pipeline, hot/warm/cold tiers - 'Which milestone am I in?' — v3.2.0–v3.8.0 status + cross-milestone invariants - Key Numbers table (35 entries) Reference files (1,974 lines across 9 files): - plan-lifecycle: phase mechanics, decision tree schema, checkpoint triggers, child plan execution modes, merge strategies, plan identity fields - entities: data models for Plan, Decision, Action, Session, Invariant, AutomationProfile, SafetyProfile, AutomationGuard, Namespace - architecture: 4-layer diagram, deployment modes, complete A2A method routing tables (standard + plan + registry + context + sync + health), streaming events, authentication, error taxonomy, full tech stack - automation-profiles: threshold table for all 8 built-in profiles, use cases, Semantic Escalation algorithm, custom profile YAML - actors-tools-skills: Actor/Tool/Validation/Skill YAML schemas with complete annotated examples, Jinja2 filter reference, LSP integration detail, LSPToolAdapter, actor context precedence - resources: complete resource type hierarchy (all 34+ types), sandbox strategies, type inheritance rules, execution environment routing, devcontainer integration, CLI usage - acms: UKO 4-layer ontology, CRP, 10-slot Context Assembly Pipeline with per-slot component names, hot/warm/cold eviction rules, skeleton compression, context view configuration - milestones: v3.2.0–v3.8.0 deliverables, architectural constraints, and definitions of done; cross-milestone quality gates and invariants - cli-commands: complete CLI reference for all command groups with all flags: plan, action, session, project, actor, skill, tool, validation, resource, invariant, automation-profile, lsp, config, utility ISSUES CLOSED: #0	2026-04-15 19:19:11 +00:00
freemo	38a2773261	docs(skill): expand cleveragents-contributing SKILL.md with 7 new trees and deep expansions ... Add 7 new decision trees covering gaps found in CONTRIBUTING.md audit: 'Am I creating an issue?' — full issue anatomy: mandatory Metadata section (exact commit message first line + branch name), Subtasks checkbox format with example, Definition of Done section, label rules (State/Unverified +Type+Priority; MoSCoW by owner only), Ref field rules, parent and blocking link mechanics via Forgejo dependencies, bug issues companion TDD issue rule. 'Am I about to write code?' — spec-first mandate (read docs/specification.md before any code), ADR process for architectural changes, branch must match issue Metadata, test-first requirement, SOLID + arg validation + type annotations requirements, prohibited list (# type: ignore, half-done work, mocks in src/, if-testing guards). 'Am I about to commit?' — self-review diff (git add -p), atomicity rules (one logical change, no cosmetic+functional mixing, code-move then modify), completeness rules (tests + docs + changelog + ancillary files in same commit), bisect-friendly / revertibility requirements, prescribed commit first line verbatim from issue Metadata, Commitizen usage, pre-commit hook rules, commit hygiene (topic branches, interactive rebase before merging). 'Am I submitting a PR?' — all 12 PR requirements numbered, with critical dependency direction rule (PR→blocks→issue; reversed = deadlock with full explanation), closing keywords, one Epic per PR, milestone + Type/ label, after-submission state transitions, complete merge checklist. 'Am I reviewing a PR?' — eligibility and approval rules, CI gate check, all 6 reviewer criteria (correctness, spec alignment, test quality, type safety, readability, performance, security, style, documentation, commit quality), requesting changes protocol, maintainer override rule. 'Am I documenting something?' — single canonical surface rule, traceability (module.class.method + commit hash; never file:linenum), same-commit rule, code-level docstring requirements, spec.md authority. 'Am I writing error handling?' — mandatory argument validation pattern (before ANY other logic) with Python code example, exception propagation rules (never suppress, never bare except, never return None on error), fail-fast principles, AssertionError for TDD expected-fail steps. Expand existing trees: - 'Am I writing tests?': add multi-level testing mandate (unit + integration + benchmarks required for every task), what tests must cover (error paths, edge cases, failure modes), test failure remediation rules - 'Which nox session?': clarify format vs format --check difference - 'Am I looking at a CI failure?': add quality/complexity failure diagnosis, common causes per job type, more detail on coverage and unit_tests failures - 'Am I writing LangChain/LangGraph code?': clarify MemorySaver requirement, memory class selection (Buffer vs Entity), format prohibition reasoning - 'Which directory?': add /benchmarks/ to directory tree Update master decision tree with 6 new branches for new trees. Update Key Numbers table with 4 new rows. Update frontmatter description to cover all new topics. Override highlights table: add commit first line and PR dep direction rows. ISSUES CLOSED: #0	2026-04-15 19:00:54 +00:00
freemo	82471f87f0	docs(skill): add cleveragents-contributing project-specific skill ... New skill covering all CONTRIBUTING.md project-specific rules that supplement or override the generic cleverthis-guidelines skill. Prominently declares override precedence at the top of SKILL.md and in every reference file — this skill's rules apply unconditionally when they conflict with the general skill. SKILL.md (839 lines) contains: - Override notice table comparing cleverthis-guidelines vs this project for 18 specific topics (framework, directories, tool names, etc.) - Master decision tree routing all project-specific situations - 9 detailed decision trees: file placement (exact directories), tests (Behave/Robot Framework rules), TDD bug fix workflow (full 6-step with branch naming), TDD issue-capture test (exact three-tag system with AssertionError enforcement), nox session reference (all sessions + CI job mappings + required-for-merge), CI failure diagnosis (per-job remediation), plan CLI (v3 vs legacy, ULID, storage backends), LangChain/LangGraph code (TypedDict, MemorySaver, BaseLanguageModel, FakeListLLM, canonical node pattern), Python imports (top-of-file, TYPE_CHECKING exception), dev env setup (complete tool inventory), and release process (backwards compat policy, Docker, secrets) - Key Numbers table with 33 project-specific values Reference files (1254 lines total): - testing/README.md: Behave rules, Robot Framework, TDD tag system with full examples and validation rules, AssertionError requirement, coverage threshold, mock placement, LangGraph testing, ASV benchmarks - ci-cd/README.md: all 13 CI jobs with nox session mappings, 3 workflow triggers, 5 required-for-merge checks, secrets table, caching policy, nightly quality sweep, branch protection - toolchain/README.md: complete nox session catalogue, Pyright prohibition on # type: ignore, ruff config, Hatch, pyproject.toml as single source, pre-commit setup, Commitizen, Python import rules with examples, error handling patterns with Python code - langchain-langgraph/README.md: TypedDict state, verb-based node naming, MemorySaver, conditional edges, BaseLanguageModel abstraction, prompt templates, sync+async requirement, output parsing, env var configuration, LangSmith disabled by default, retry decorators, canonical node template, FakeListLLM testing, state/workflow/streaming/memory test patterns - file-organization/README.md: exact directory map, per-directory rules and prohibitions, docs/specification.md authority, BDD step-file naming rules - cli-workflow/README.md: v3 vs legacy comparison table, ULID format, why mixing is impossible (separate storage backends), error diagnosis for common failure modes, manual migration steps, backwards compat policy ISSUES CLOSED: #0	2026-04-15 18:50:51 +00:00