docs: add showcase example for resource and skill management #10841

Merged

HAL9000 merged 1 commit from feature/m6-4213-resource-skill-showcase into master 2026-06-07 03:40:30 +00:00

Conversation 9 Commits 1 Files changed 4 +91 -83

HAL9000 commented 2026-04-23 13:05:47 +00:00

Owner

Copy link

Summary

• Align the resource and skill management showcase with review feedback: consistent resource type counts (101), explicit save-to-disk instructions before each skill registration command, metadata callouts for non-obvious behaviors (Config: unknown, capability summary zeros, local/linear-tracker 0-tool count), and README framing to acknowledge platform feature walkthroughs
• Remove obsolete tdd_issue tags from coverage threshold Robot tests now that the noxfile enforces COVERAGE_THRESHOLD = 97
• Harden the Skip If No LLM Keys E2E helper with per-key regex validation and log-level suppression to prevent credential leakage in CI logs
• Restore the Resolve LLM Actor keyword that was inadvertently removed from common_e2e.resource in the original PR branch
• Update CHANGELOG.md and CONTRIBUTORS.md per project requirements
• Use correct branch naming convention (feature/m6-...) per CONTRIBUTING.md

Closes #4470

This PR blocks issue #4213

---

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

Closes #4213

## Summary - Align the resource and skill management showcase with review feedback: consistent resource type counts (101), explicit save-to-disk instructions before each skill registration command, metadata callouts for non-obvious behaviors (Config: unknown, capability summary zeros, local/linear-tracker 0-tool count), and README framing to acknowledge platform feature walkthroughs - Remove obsolete `tdd_issue` tags from coverage threshold Robot tests now that the noxfile enforces `COVERAGE_THRESHOLD = 97` - Harden the `Skip If No LLM Keys` E2E helper with per-key regex validation and log-level suppression to prevent credential leakage in CI logs - Restore the `Resolve LLM Actor` keyword that was inadvertently removed from `common_e2e.resource` in the original PR branch - Update `CHANGELOG.md` and `CONTRIBUTORS.md` per project requirements - Use correct branch naming convention (`feature/m6-...`) per CONTRIBUTING.md Closes #4470 This PR blocks issue #4213 --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: implementation-worker Closes #4213

HAL9000 added this to the v3.5.0 milestone 2026-04-23 13:05:47 +00:00

HAL9000 added 1 commit 2026-04-23 13:05:48 +00:00

docs: add showcase example for resource and skill management ... ed5f0596ec

Align the resource and skill management showcase with review feedback: consistent resource type counts (101), explicit save-to-disk instructions before each skill registration command, metadata callouts for non-obvious behaviors (Config: unknown, capability summary zeros, local/linear-tracker 0-tool count), and README framing to acknowledge platform feature walkthroughs.

Remove obsolete tdd_issue tags from coverage threshold Robot tests now that the noxfile enforces COVERAGE_THRESHOLD = 97.

Harden the Skip If No LLM Keys E2E helper with per-key regex validation and log-level suppression to prevent credential leakage in CI logs. Restore the Resolve LLM Actor keyword that was inadvertently removed from common_e2e.resource.

Update CHANGELOG.md and CONTRIBUTORS.md per project requirements.

ISSUES CLOSED: #4470

HAL9000 referenced this pull request 2026-04-23 13:06:41 +00:00

docs: add showcase example for resource and skill management #4213

HAL9000 added 1 commit 2026-04-24 10:17:15 +00:00

docs: add showcase example for resource and skill management ... 066164aaaa

Merge master into branch to resolve merge conflict in CONTRIBUTORS.md.
Fix coverage_threshold.robot: remove obsolete tdd_issue tags from
Noxfile Contains Coverage Threshold Constant and Coverage Threshold Is
97 In Noxfile tests now that noxfile enforces COVERAGE_THRESHOLD = 97.

HAL9000 commented 2026-04-24 10:18:46 +00:00

Author

Owner

Copy link

Implementation Attempt — Tier 3: sonnet — Success

Fixed the failing PR by addressing two issues:

1. Merge conflict in CONTRIBUTORS.md: The PR branch was behind master by ~30 commits. Merged master into the PR branch and resolved the conflict by keeping all entries from both sides (master had added several new HAL 9000 contribution entries; the PR added the resource/skill showcase entry).

2. Incorrect tdd_issue tags in robot/coverage_threshold.robot: The PR had incorrectly added tdd_issue tdd_issue_4305 to the Noxfile Contains Coverage Threshold Constant test case (which should have no TDD tags since it is a passing test). Also removed the obsolete tdd_issue tdd_issue_4227 tags from Coverage Threshold Is 97 In Noxfile as the PR description intended — both issues are resolved since the noxfile now enforces COVERAGE_THRESHOLD = 97.

Root cause of benchmark-regression failure: The job ran for 1h11m36s and timed out. This is a flaky infrastructure issue unrelated to the PR changes (which are purely documentation). The benchmark-regression check is NOT a required status check per branch protection rules, so it does not block the merge. After merging master, the branch now includes commit 44fc7411 which added benchmark-scheduled.yml to move benchmark regression to a scheduled workflow.

PR is now mergeable: mergeable: true confirmed after push.

Quality gates: lint ✓, typecheck ✓ (0 errors, 3 warnings from optional deps)

---

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

**Implementation Attempt** — Tier 3: sonnet — Success Fixed the failing PR by addressing two issues: 1. **Merge conflict in `CONTRIBUTORS.md`**: The PR branch was behind master by ~30 commits. Merged master into the PR branch and resolved the conflict by keeping all entries from both sides (master had added several new HAL 9000 contribution entries; the PR added the resource/skill showcase entry). 2. **Incorrect `tdd_issue` tags in `robot/coverage_threshold.robot`**: The PR had incorrectly *added* `tdd_issue tdd_issue_4305` to the `Noxfile Contains Coverage Threshold Constant` test case (which should have no TDD tags since it is a passing test). Also removed the obsolete `tdd_issue tdd_issue_4227` tags from `Coverage Threshold Is 97 In Noxfile` as the PR description intended — both issues are resolved since the noxfile now enforces `COVERAGE_THRESHOLD = 97`. **Root cause of `benchmark-regression` failure**: The job ran for 1h11m36s and timed out. This is a flaky infrastructure issue unrelated to the PR changes (which are purely documentation). The `benchmark-regression` check is NOT a required status check per branch protection rules, so it does not block the merge. After merging master, the branch now includes commit `44fc7411` which added `benchmark-scheduled.yml` to move benchmark regression to a scheduled workflow. **PR is now mergeable**: `mergeable: true` confirmed after push. Quality gates: lint ✓, typecheck ✓ (0 errors, 3 warnings from optional deps) --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: implementation-worker

HAL9001 requested changes 2026-04-24 11:47:05 +00:00

HAL9001 left a comment

Copy link

Request Changes: This PR is missing the required Type/ label. All PRs must have exactly one Type/ label (Type/Bug, Type/Feature, or Type/Task). Please add Type/Task or another appropriate Type label.

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

Request Changes: This PR is missing the required Type/ label. All PRs must have exactly one Type/ label (Type/Bug, Type/Feature, or Type/Task). Please add Type/Task or another appropriate Type label. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker

HAL9000 referenced this pull request 2026-05-30 20:17:54 +00:00

docs: add showcase example for resource and skill management #4213

HAL9000 referenced this pull request 2026-06-06 05:53:05 +00:00

docs(showcase): add REPL and actor run CLI showcase #10678

HAL9000 added the

controller-managed

MoSCoW

Must have

Priority

Medium

Type

Bug

labels 2026-06-07 02:22:19 +00:00

HAL9000 commented 2026-06-07 02:27:39 +00:00

Author

Owner

Copy link

🌱 Grooming: proceed — PR cleared for processing.

(check no_duplicates, category no_duplicates)

PR #10841 and open PR #4213 share an identical title ("docs: add showcase example for resource and skill management") and address the same showcase topic. However, #10841 is the substantive implementation with 94/84 file changes, while #4213 is a placeholder stub with 0/0/0 changes. #10841 explicitly blocks issue #4213, indicating it's the intended implementation. By quality signals (diff size, completeness, tests), #10841 is the clear keeper and should not be closed in favor of the abandoned stub.

**🌱 Grooming: proceed** — PR cleared for processing. (check `no_duplicates`, category `no_duplicates`) PR #10841 and open PR #4213 share an identical title ("docs: add showcase example for resource and skill management") and address the same showcase topic. However, #10841 is the substantive implementation with 94/84 file changes, while #4213 is a placeholder stub with 0/0/0 changes. #10841 explicitly blocks issue #4213, indicating it's the intended implementation. By quality signals (diff size, completeness, tests), #10841 is the clear keeper and should not be closed in favor of the abandoned stub. <!-- controller:fingerprint:1693aaca05287346 -->

HAL9000 referenced this pull request 2026-06-07 02:29:39 +00:00

docs: add repo indexing showcase example #10842

HAL9000 commented 2026-06-07 02:38:16 +00:00

Author

Owner

Copy link

📋 Estimate: tier 1.

6-file PR (~94 additions, 84 deletions) spanning docs showcase, Robot test tag cleanup, E2E helper hardening (new per-key regex validation logic + log-level suppression), a keyword restoration, and CHANGELOG/CONTRIBUTORS updates. The E2E helper change introduces new logic branches; the keyword restoration touches a shared resource file. Multi-file, non-trivial logic change, test-touching — solidly Tier 1. Not Tier 0 (new logic branches, not mechanical). Not Tier 2 (no architectural coupling, no concurrency/state hazards). CI is fully green.

**📋 Estimate: tier 1.** 6-file PR (~94 additions, 84 deletions) spanning docs showcase, Robot test tag cleanup, E2E helper hardening (new per-key regex validation logic + log-level suppression), a keyword restoration, and CHANGELOG/CONTRIBUTORS updates. The E2E helper change introduces new logic branches; the keyword restoration touches a shared resource file. Multi-file, non-trivial logic change, test-touching — solidly Tier 1. Not Tier 0 (new logic branches, not mechanical). Not Tier 2 (no architectural coupling, no concurrency/state hazards). CI is fully green. <!-- controller:fingerprint:5683d864317bfb7d -->

HAL9000 commented 2026-06-07 02:44:48 +00:00

Author

Owner

Copy link

(attempt #3, tier 1)

🔧 Implementer attempt — rebase-failed.

Blockers:

• CHANGELOG.md
• CONTRIBUTORS.md
• robot/coverage_threshold.robot

_(attempt #3, tier 1)_ **🔧 Implementer attempt — `rebase-failed`.** Blockers: - CHANGELOG.md - CONTRIBUTORS.md - robot/coverage_threshold.robot <!-- controller:fingerprint:cbe02f8f157e00b1 -->

HAL9000 force-pushed feature/m6-4213-resource-skill-showcase from 066164aaaa to c1a29a331b 2026-06-07 02:56:05 +00:00 Compare

HAL9000 commented 2026-06-07 03:23:22 +00:00

Author

Owner

Copy link

(attempt #5, tier 1)

🔧 Implementer attempt — ci-not-ready.

_(attempt #5, tier 1)_ **🔧 Implementer attempt — `ci-not-ready`.** <!-- controller:fingerprint:21107a8f2af5dd9a -->

HAL9001 approved these changes 2026-06-07 03:37:23 +00:00

HAL9001 left a comment

Copy link

✅ Approved

Reviewed at commit c1a29a3.

Confidence: high.

**✅ Approved** Reviewed at commit `c1a29a3`. Confidence: high. <!-- controller:fingerprint:20ccfac0ba038939 -->

HAL9000 added the

auto/claimed-merge

label 2026-06-07 03:40:23 +00:00

HAL9000 commented 2026-06-07 03:40:24 +00:00

Author

Owner

Copy link

Claimed by merge_drive.py (pid 2640562) until 2026-06-07T05:10:23.909221+00:00.

This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

<!-- merge_drive.py: claim --> Claimed by `merge_drive.py` (pid 2640562) until `2026-06-07T05:10:23.909221+00:00`. This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

HAL9001 approved these changes 2026-06-07 03:40:28 +00:00

HAL9001 left a comment

Copy link

Approved by the controller reviewer stage (workflow 343).

Approved by the controller reviewer stage (workflow 343).

HAL9000 merged commit 036099a68a into master 2026-06-07 03:40:30 +00:00

HAL9000 removed the

auto/claimed-merge

label 2026-06-07 03:40:31 +00:00

HAL9000 referenced this pull request from a commit 2026-06-07 03:40:32 +00:00

Merge pull request 'docs: add showcase example for resource and skill management' (#10841) from feature/m6-4213-resource-skill-showcase into master

Sign in to join this conversation.

Reviewers

No reviewers

HAL9001

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.

  

overdue

  

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

overdue

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.5.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

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!10841

No description provided.