A merge of nine sets of code. #101

Merged

brent.edwards merged 58 commits from develop-20260217 into master 2026-02-19 01:59:57 +00:00

Conversation 0 Commits 58 Files changed 83 +14510 -404

brent.edwards commented 2026-02-18 02:48:54 +00:00

Member

Copy link

No description provided.

brent.edwards added 47 commits 2026-02-18 02:48:54 +00:00

docs(skill): add skill YAML schema and examples c41581b7c4

Merge branch 'master' into feature/m3-skill-schema 08ad4ea683

style(skill): apply ruff auto-formatting to skill schema files 6d7b759f25

feat(cli): add skill commands c562557da8

test(skill): add robot skill resolver smoke tests f0815dd126

test(cli): expand lifecycle command coverage b8d2bfe252

test(persistence): add plan/action persistence suites f912a136b7

Merge branch 'master' into feature/m3-skill-schema 53c41f904f

test(session): add robot session model smoke tests 4f32daa740

Merge branch 'master' into feature/m3-skill-cli 49362381bd

build(merge): merge with master 81e4ffe92a

build(merge): merge with master 5f77dd92cd

test(db): add resource registry robot smoke test 5d2e70cff0

test(tool): add robot tool model smoke tests 3d2cd05f56

fix(test): commit edge row so delete step sees it in its own session ... a7ed08a4f3

The "Deleting a resource with edges is rejected" scenario was failing
because the ResourceEdgeModel row was flushed but never committed.
Since ResourceRepository.delete() obtains its own session from the
factory, the uncommitted edge was invisible and ResourceHasEdgesError
was never raised.

fix(test): commit edge row so delete step sees it in its own session ... da40bff33d

The "Deleting a resource with edges is rejected" scenario was failing
because the ResourceEdgeModel row was flushed but never committed.
Since ResourceRepository.delete() obtains its own session from the
factory, the uncommitted edge was invisible and ResourceHasEdgesError
was never raised.

feat: merge branch 'master' into feature/m3-skill-cli cdbd0bdd23

fix(test): commit edge row so delete step sees it in its own session ... 9db88a9541

The "Deleting a resource with edges is rejected" scenario was failing
because the ResourceEdgeModel row was flushed but never committed.
Since ResourceRepository.delete() obtains its own session from the
factory, the uncommitted edge was invisible and ResourceHasEdgesError
was never raised.

feat: merge branch 'master' into feature/m3-session-domain-robot 6c7bcab01e

fix(resource_repository_steps.py): add missing commit() statement d24079f129

feat: Merge branch 'master' into feature/m1-resource-db-robot-tests 2840514729

fix(resource_repository_steps.py): add missing commit() statement d950d48aa9

fix(resource_repository_steps.py): add missing commit() statement bd647d58cf

fix(test): resolve AmbiguousStep collision, invalid ULIDs, and edge commit ... ea7fcc0ba0

Three issues prevented the behave suite from running:

1. plan_persistence_steps.py and plan_repository_steps.py both defined
   @then('the retrieved plan description should be "..."'), causing an
   AmbiguousStep error that broke all ~50 feature files. Renamed the
   persistence step to "the persisted plan description should be".

2. The three-level hierarchy scenario used plan IDs containing O, I,
   and L which are excluded from the ULID charset. Replaced with valid
   characters (O->0, I->0, L->K).

3. resource_repository_steps.py flushed but never committed the edge
   row, so the delete method's separate session could not see it.

feat(session): add session persistence and repositories 47cad3c77b

feat: merge branch 'master' into feature/m3-skill-domain-robot b1c011702f

fix(test): commit edge row so delete step sees it in its own session ... 9e9f229b3a

The "Deleting a resource with edges is rejected" scenario was failing
because the ResourceEdgeModel row was flushed but never committed.
Since ResourceRepository.delete() obtains its own session from the
factory, the uncommitted edge was invisible and ResourceHasEdgesError
was never raised.

feat: merge branch 'master' into feature/m3-skill-schema 8416962bea

style(format): 1 file reformatted 1fbc062b48

style(ruff-format): ruff format run ... c8fa6f716d

One file repaired.

Merge branch 'master' into feature/m1-cli-tests 60d10cef7c

feat: merge branch 'master' into feature/m1-persistence-tests b528cde8e7

feat: merge branch 'master' into feature/m3-session-persistence 066e3c248c

feat: merge branch 'master' into feature/m3-skill-schema c985b3435e

feat: merge branch 'master' into feature/m3-tool-domain-robot 686c834602

test(cov): add skill CLI and service coverage scenarios ... 3598924d6f

Add 19 behave scenarios covering uncovered paths in skill_service.py
and cli/commands/skill.py to bring coverage above the 97% threshold:
- show with includes, MCP servers, agent_skills, inline tools, Referenced By
- tools with mixed MCP/inline sources
- list with non-local namespaces
- remove without --yes (abort path)
- update with dependent skills (Affected Actors panel)
- service edge cases: skill_count, empty names, source filtering, no config_path
- add with missing-description YAML (validation failure)

feat: merge branch 'master' into feature/m3-skill-cli 4a200faf11

feat: merge branch 'master' into feature/m3-skill-domain-robot 5ceca82e49

style(ruff-format): fix one unformatted file d476e45fba

Merge branch 'feature/m3-skill-cli' into develop-20260217 e6e8eecd1e

Merge branch 'feature/m1-cli-tests' into develop-20260217 b6c1c72d43

Merge branch 'feature/m1-persistence-tests' into develop-20260217 ... 6f09f23d29

# Conflicts:
#	docs/development/testing.md

Merge branch 'feature/m3-session-persistence' into develop-20260217 a9ee5fbc0e

Merge branch 'feature/m3-session-domain-robot' into develop-20260217 ... 4e3150bd50

# Conflicts:
#	implementation_plan.md

Merge branch 'feature/m1-resource-db-robot-tests' into develop-20260217 0a7a8d15be

Merge branch 'feature/m3-tool-domain-robot' into develop-20260217 a2ec1ccc44

Merge branch 'feature/m3-skill-domain-robot' into develop-20260217 629f286bd3

brent.edwards referenced this pull request 2026-02-18 02:49:45 +00:00

feature/m3-skill-cli #92

brent.edwards referenced this pull request 2026-02-18 02:50:05 +00:00

test(cli): expand lifecycle command coverage #95

brent.edwards referenced this pull request 2026-02-18 02:50:20 +00:00

test(persistence): add plan/action persistence suites #96

brent.edwards referenced this pull request 2026-02-18 02:50:36 +00:00

test(session): add robot session model smoke tests #97

brent.edwards referenced this pull request 2026-02-18 02:50:51 +00:00

test(db): add resource registry robot smoke test #98

brent.edwards added 5 commits 2026-02-18 12:19:19 +00:00

Merge branch 'master' into develop-20260217 24866b2244

Merge branch 'master' into develop-20260217 f5e28d5196

Merge branch 'master' into develop-20260217 ... 7f8cc7bf73

# Conflicts:
#	docs/reference/database_schema.md
#	implementation_plan.md
#	src/cleveragents/infrastructure/database/models.py
#	src/cleveragents/infrastructure/database/repositories.py

Merge master into develop-20260217 52f74f3ddb

fix: align tool registry coverage and resource links 8445db3858

brent.edwards added 1 commit 2026-02-18 16:12:34 +00:00

feat: merge branch 'master' into develop-20260217 be99ecb8b4

brent.edwards added 2 commits 2026-02-18 23:13:53 +00:00

fix(test): resolve CI test failures from session isolation and subprocess timeouts ... b50987731a

- Fix resource_repository Behave scenario 'Resolve by ULID returns the
  resource' by propagating res_type_name through context instead of
  relying on fragile list_types() across SQLAlchemy sessions
- Increase subprocess timeouts in Robot Framework integration tests to
  prevent SIGTERM kills under parallel execution load (10s->30s, 20s->60s,
  30s->60s across 7 robot files)

Merge branch 'master' into develop-20260217 ... 2dfad7ec71

# Conflicts:
#	implementation_plan.md

brent.edwards added 1 commit 2026-02-19 00:58:15 +00:00

Merge branch 'master' into develop-20260217 ... 9802424a41

# Conflicts:
#	robot/database_integration.robot

brent.edwards added 2 commits 2026-02-19 01:41:26 +00:00

Merge branch 'master' into develop-20260217 99f2f66a38

fix(test): increase subprocess timeouts in cli.robot and cli_core.robot ... e4705822b1

- Add timeout=60s to all Run Process calls in cli.robot (previously had
  no timeout, causing hangs under CI parallel load)
- Increase cli_core.robot timeouts from 30s to 60s to match other robot
  files
- Relax performance assertions from <30s to <60s to account for Python
  cold-start overhead under pabot parallel execution

brent.edwards merged commit 93f96a074e into master 2026-02-19 01:59:57 +00:00

brent.edwards deleted branch develop-20260217 2026-02-19 01:59:58 +00:00

brent.edwards referenced this pull request from a commit 2026-02-19 01:59:59 +00:00

Merge pull request 'A merge of nine sets of code.' (#101) from develop-20260217 into master

freemo added this to the v3.0.0 milestone 2026-02-23 17:25:50 +00:00

freemo added the

State

Completed

label 2026-03-04 00:59:50 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

auto/needs-reevaluation

Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  

controller-managed

Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  

auto/blocked-by-deps

PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  

auto/ci-timeout

Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  

auto/claimed-implementer

Currently being processed by an implementer worker.

  

auto/claimed-merge

Currently being processed by the merge driver.

  

auto/claimed-reviewer

Currently being processed by a reviewer worker.

  

auto/driver-down

Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  

auto/invariant-violation

Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  

auto/last-attempt-tier-0

In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-1

In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-2

In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  

auto/last-attempt-tier-min

In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  

Automation Tracking

Tracking issues used by the AI Automation system for agents to communicate and report.

  

auto/needs-conflict-resolution

Rebase conflict needs LLM conflict-resolver.

  

auto/needs-implementer

Failing CI needs implementer attention.

  

auto/postmortem

Documenting a driver incident or rollback.

  

auto/ready-to-merge

Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  

auto/restart-throttled

Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  

auto/revert

Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  

auto/sentinel

Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  

auto/stale-inactivity

No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  

auto/unstable

Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs Feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

CI Blocker

Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Automation

Any edits or discussion about the AI automated coding system.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Refactor

A code change that restructures existing code without changing its external behavior.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

auto/needs-reevaluation

controller-managed

auto/blocked-by-deps

auto/ci-timeout

auto/claimed-implementer

auto/claimed-merge

auto/claimed-reviewer

auto/driver-down

auto/invariant-violation

auto/last-attempt-tier-0

auto/last-attempt-tier-1

auto/last-attempt-tier-2

auto/last-attempt-tier-min

Automation Tracking

auto/needs-conflict-resolution

auto/needs-implementer

auto/postmortem

auto/ready-to-merge

auto/restart-throttled

auto/revert

auto/sentinel

auto/stale-inactivity

auto/unstable

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

v3.0.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

cleveragents/cleveragents-core!101

No description provided.