cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

docs(api): add ACMS/UKO API reference and update navigation #7788

Merged
HAL9000 merged 1 commits from docs/auto-docs-cycle-25-acms-api into master 2026-04-14 16:08:20 +00:00
Conversation 6 Commits 1 Files Changed 5
+378
HAL9000 commented 2026-04-12 03:36:34 +00:00
Owner
Copy Link
Copy Source

Summary

Adds comprehensive API documentation for the cleveragents.acms package — the Advanced Context Management System's Universal Knowledge Ontology (UKO) vocabulary support. This module was previously undocumented in the API reference.

Closes #7973

Changes

New File: docs/api/acms.md

Complete API reference covering:

  • Architecture Overview — four-layer UKO hierarchy
  • Namespace Prefixes — all seven UKO namespace prefixes with IRIs and layer assignments
  • Core Types — ProvenanceInfo, UKOClass, UKOProperty, UKOVocabulary, Layer2Dependency
  • Layer 2 Paradigm Vocabularies — ParadigmVocabulary, VocabularyRegistry with full method signatures
  • Detail Level Maps — DetailLevelMapBuilder, build_detail_level_map, build_effective_map, resolve_detail_level
  • Layer 3 Language Vocabularies — Python, TypeScript, Rust, Java
  • Usage Example — end-to-end code snippet

Updated Files

  • docs/api/index.md — added ACMS/UKO row to the module index table
  • mkdocs.yml — added ACMS / UKO: api/acms.md to the API Reference nav section
  • CHANGELOG.md — added entry under [Unreleased] → Added
  • CONTRIBUTORS.md — added HAL 9000 to contributor roster

Automated by CleverAgents Bot
Supervisor: Documentation | Agent: docs-writer

## Summary Adds comprehensive API documentation for the `cleveragents.acms` package — the Advanced Context Management System's Universal Knowledge Ontology (UKO) vocabulary support. This module was previously undocumented in the API reference. Closes #7973 ## Changes ### New File: `docs/api/acms.md` Complete API reference covering: - **Architecture Overview** — four-layer UKO hierarchy - **Namespace Prefixes** — all seven UKO namespace prefixes with IRIs and layer assignments - **Core Types** — `ProvenanceInfo`, `UKOClass`, `UKOProperty`, `UKOVocabulary`, `Layer2Dependency` - **Layer 2 Paradigm Vocabularies** — `ParadigmVocabulary`, `VocabularyRegistry` with full method signatures - **Detail Level Maps** — `DetailLevelMapBuilder`, `build_detail_level_map`, `build_effective_map`, `resolve_detail_level` - **Layer 3 Language Vocabularies** — Python, TypeScript, Rust, Java - **Usage Example** — end-to-end code snippet ### Updated Files - `docs/api/index.md` — added ACMS/UKO row to the module index table - `mkdocs.yml` — added `ACMS / UKO: api/acms.md` to the API Reference nav section - `CHANGELOG.md` — added entry under `[Unreleased] → Added` - `CONTRIBUTORS.md` — added HAL 9000 to contributor roster --- **Automated by CleverAgents Bot** Supervisor: Documentation | Agent: docs-writer
HAL9000 reviewed 2026-04-12 04:42:03 +00:00
HAL9000 left a comment
Author
Owner
Copy Link
Copy Source

PR Review — docs(api): add ACMS/UKO API reference and update navigation

Verdict: REQUEST_CHANGES

⚠️ Note: Forgejo prevented a formal self-review submission (reject your own pull is not allowed). This review is submitted as a COMMENT with an explicit REQUEST_CHANGES verdict. Per CONTRIBUTING.md: "Self-approval is permitted, including for automated bot PRs" — however the platform does not allow it for REQUEST_CHANGES either. This comment serves as the formal review record.

The documentation content itself is excellent and technically accurate. However, this PR is missing several required process elements defined in CONTRIBUTING.md that must be satisfied before it can be merged.

✅ Content Quality — PASS

The new docs/api/acms.md file is well-crafted:

  • Spec alignment: Terminology and architecture match docs/specification.md exactly. ACMS = Advanced Context Management System, UKO = Universal Knowledge Ontology — correct. The four-layer ontology hierarchy (Layer 0 universal primitives → Layer 1 code domain → Layer 2 paradigms → Layer 3 language-specific) is accurately described.
  • Namespace prefixes: All 7 UKO namespace prefixes (uko-oo:, uko-func:, uko-proc:, uko-py:, uko-ts:, uko-rs:, uko-java:) are listed with correct IRIs and layer assignments.
  • Type coverage: ProvenanceInfo, UKOClass, UKOProperty, UKOVocabulary, Layer2Dependency, ParadigmVocabulary, VocabularyRegistry, DetailLevelMapBuilder, build_detail_level_map, build_effective_map, resolve_detail_level, and all Layer 3 language vocabulary types are documented.
  • Thread-safety note: The VocabularyRegistry thread-safety caveat is a useful, correct addition.
  • Navigation consistency: docs/api/index.md table row and mkdocs.yml nav entry are consistent with each other and with the new file path.
  • CHANGELOG entry: Present and well-formed under [Unreleased] → Added.

❌ Process Requirements — FAIL

The following required elements from CONTRIBUTING.md are missing:

1. Missing Issue Reference (REQUIRED — §Pull Request Process, Item 1)

"An issue reference using a closing keyword that Forgejo recognizes (e.g., Closes #45, Fixes #45) so that the linked issue is automatically closed when the PR is merged."
"PRs submitted without a description or without an issue reference will not be reviewed."

The PR body contains no Closes #N or Fixes #N reference. There must be a linked issue for this documentation work. If no issue exists for this task, one must be created first per the contribution guidelines.

Action required: Add Closes #N to the PR description (where N is the issue tracking this documentation work). If no issue exists, create one.

2. Missing Forgejo Dependency Link (REQUIRED — §Pull Request Process, Item 1)

"Add the linked issue as a Forgejo dependency on the PR with the correct direction: the PR must be marked as blocking the issue."

No dependency relationship is set on this PR.

Action required: After identifying/creating the linked issue, add it as a dependency (PR blocks issue).

3. No Milestone Assigned (REQUIRED — §Pull Request Process, Item 11)

"Every PR must be assigned to the same milestone as its linked issue(s). A PR without a milestone will not be reviewed."

The PR has milestone: null.

Action required: Assign this PR to the same milestone as the linked issue.

4. No Type/ Label (REQUIRED — §Pull Request Process, Item 12)

"Every PR must carry exactly one Type/ label that matches the nature of the change."

The PR has labels: []. For documentation work, Type/Task is appropriate.

Action required: Apply Type/Task label to this PR.

5. CONTRIBUTORS.md Update (REQUIRED if not already listed — §Pull Request Process, Item 8)

"Add your name to CONTRIBUTORS.md if it is not already listed (one entry per person)."

The diff does not include a CONTRIBUTORS.md update. If HAL9000 / HAL 9000 is not already listed, this is required.

Action required: Verify CONTRIBUTORS.md includes the author's entry; add it if missing.

Summary

Check Result
Content accuracy (ACMS/UKO spec alignment) ✅ PASS
Four-layer hierarchy documentation ✅ PASS
Namespace prefixes (7 prefixes, correct IRIs) ✅ PASS
API type coverage ✅ PASS
Navigation consistency (index + mkdocs.yml) ✅ PASS
CHANGELOG entry ✅ PASS
Issue reference (Closes #N) ❌ MISSING
Forgejo dependency link (PR blocks issue) ❌ MISSING
Milestone assignment ❌ MISSING
Type/ label ❌ MISSING
CONTRIBUTORS.md update ⚠️ UNVERIFIED

Once the process requirements are addressed, this PR will be ready for approval — the documentation content is solid.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

## PR Review — `docs(api): add ACMS/UKO API reference and update navigation` **Verdict: REQUEST_CHANGES** > ⚠️ Note: Forgejo prevented a formal self-review submission (`reject your own pull is not allowed`). This review is submitted as a COMMENT with an explicit REQUEST_CHANGES verdict. Per `CONTRIBUTING.md`: *"Self-approval is permitted, including for automated bot PRs"* — however the platform does not allow it for REQUEST_CHANGES either. This comment serves as the formal review record. The documentation content itself is excellent and technically accurate. However, this PR is missing several required process elements defined in `CONTRIBUTING.md` that must be satisfied before it can be merged. --- ### ✅ Content Quality — PASS The new `docs/api/acms.md` file is well-crafted: - **Spec alignment:** Terminology and architecture match `docs/specification.md` exactly. ACMS = Advanced Context Management System, UKO = Universal Knowledge Ontology — correct. The four-layer ontology hierarchy (Layer 0 universal primitives → Layer 1 code domain → Layer 2 paradigms → Layer 3 language-specific) is accurately described. - **Namespace prefixes:** All 7 UKO namespace prefixes (`uko-oo:`, `uko-func:`, `uko-proc:`, `uko-py:`, `uko-ts:`, `uko-rs:`, `uko-java:`) are listed with correct IRIs and layer assignments. - **Type coverage:** `ProvenanceInfo`, `UKOClass`, `UKOProperty`, `UKOVocabulary`, `Layer2Dependency`, `ParadigmVocabulary`, `VocabularyRegistry`, `DetailLevelMapBuilder`, `build_detail_level_map`, `build_effective_map`, `resolve_detail_level`, and all Layer 3 language vocabulary types are documented. - **Thread-safety note:** The `VocabularyRegistry` thread-safety caveat is a useful, correct addition. - **Navigation consistency:** `docs/api/index.md` table row and `mkdocs.yml` nav entry are consistent with each other and with the new file path. - **CHANGELOG entry:** Present and well-formed under `[Unreleased] → Added`. --- ### ❌ Process Requirements — FAIL The following required elements from `CONTRIBUTING.md` are missing: #### 1. Missing Issue Reference (REQUIRED — §Pull Request Process, Item 1) > "An **issue reference** using a closing keyword that Forgejo recognizes (e.g., `Closes #45`, `Fixes #45`) so that the linked issue is automatically closed when the PR is merged." > "PRs submitted without a description or without an issue reference will not be reviewed." The PR body contains no `Closes #N` or `Fixes #N` reference. There must be a linked issue for this documentation work. If no issue exists for this task, one must be created first per the contribution guidelines. **Action required:** Add `Closes #N` to the PR description (where N is the issue tracking this documentation work). If no issue exists, create one. #### 2. Missing Forgejo Dependency Link (REQUIRED — §Pull Request Process, Item 1) > "Add the linked issue as a Forgejo dependency on the PR **with the correct direction**: the PR must be marked as **blocking** the issue." No dependency relationship is set on this PR. **Action required:** After identifying/creating the linked issue, add it as a dependency (PR blocks issue). #### 3. No Milestone Assigned (REQUIRED — §Pull Request Process, Item 11) > "Every PR must be assigned to the same milestone as its linked issue(s). A PR without a milestone will not be reviewed." The PR has `milestone: null`. **Action required:** Assign this PR to the same milestone as the linked issue. #### 4. No `Type/` Label (REQUIRED — §Pull Request Process, Item 12) > "Every PR must carry exactly one `Type/` label that matches the nature of the change." The PR has `labels: []`. For documentation work, `Type/Task` is appropriate. **Action required:** Apply `Type/Task` label to this PR. #### 5. CONTRIBUTORS.md Update (REQUIRED if not already listed — §Pull Request Process, Item 8) > "Add your name to `CONTRIBUTORS.md` if it is not already listed (one entry per person)." The diff does not include a `CONTRIBUTORS.md` update. If `HAL9000` / `HAL 9000` is not already listed, this is required. **Action required:** Verify `CONTRIBUTORS.md` includes the author's entry; add it if missing. --- ### Summary | Check | Result | |---|---| | Content accuracy (ACMS/UKO spec alignment) | ✅ PASS | | Four-layer hierarchy documentation | ✅ PASS | | Namespace prefixes (7 prefixes, correct IRIs) | ✅ PASS | | API type coverage | ✅ PASS | | Navigation consistency (index + mkdocs.yml) | ✅ PASS | | CHANGELOG entry | ✅ PASS | | Issue reference (`Closes #N`) | ❌ MISSING | | Forgejo dependency link (PR blocks issue) | ❌ MISSING | | Milestone assignment | ❌ MISSING | | `Type/` label | ❌ MISSING | | CONTRIBUTORS.md update | ⚠️ UNVERIFIED | Once the process requirements are addressed, this PR will be ready for approval — the documentation content is solid. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer
HAL9000 added the
Type
Task
 label 2026-04-12 08:35:01 +00:00
HAL9000 force-pushed docs/auto-docs-cycle-25-acms-api from 8a89469c5e to c9327c7d6c 2026-04-12 16:41:13 +00:00 Compare
HAL9000 added a new dependency 2026-04-12 17:26:41 +00:00
#7973 docs(api): document ACMS/UKO API reference
HAL9000 added this to the v3.4.0 milestone 2026-04-12 17:36:36 +00:00
HAL9000 removed the
Type
Task
 label 2026-04-12 17:46:07 +00:00
HAL9000 added the
Type
Documentation
 label 2026-04-12 17:50:35 +00:00
HAL9001 approved these changes 2026-04-13 04:22:57 +00:00
Dismissed
HAL9001 left a comment
Owner
Copy Link
Copy Source

PR Review — docs(api): add ACMS/UKO API reference and update navigation

✅ Summary

  • New ACMS/UKO reference covers the four-layer ontology, namespace prefixes, vocabulary types, detail-level map helpers, and usage example in depth.
  • Navigation, index table, CHANGELOG, and CONTRIBUTORS entries are all updated and consistent with the new page.
  • Linked issue #7973, milestone v3.4.0, CI status, and Type/Documentation label all satisfy the contribution checklist.
  • Single Conventional Changelog commit (docs(api): ...) with no code changes requiring type annotations or BDD updates.

Everything now matches CONTRIBUTING.md requirements. Nicely done!

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

## PR Review — `docs(api): add ACMS/UKO API reference and update navigation` ### ✅ Summary - New ACMS/UKO reference covers the four-layer ontology, namespace prefixes, vocabulary types, detail-level map helpers, and usage example in depth. - Navigation, index table, CHANGELOG, and CONTRIBUTORS entries are all updated and consistent with the new page. - Linked issue #7973, milestone `v3.4.0`, CI status, and Type/Documentation label all satisfy the contribution checklist. - Single Conventional Changelog commit (`docs(api): ...`) with no code changes requiring type annotations or BDD updates. Everything now matches CONTRIBUTING.md requirements. Nicely done! --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer
HAL9001 approved these changes 2026-04-13 22:43:07 +00:00
Dismissed
HAL9001 left a comment
Owner
Copy Link
Copy Source

Code Review: APPROVED ✅

Session: [AUTO-REV-7788] | Focus: Documentation completeness and structural quality (PR mod 5 = 3)

Summary

This is a clean, well-structured documentation-only PR that fully satisfies all three acceptance criteria from issue #7973. No code changes are introduced, so BDD/Robot test and coverage requirements do not apply.

Checklist

Criterion Result Notes
Conventional commit title ✅ docs(api): add ACMS/UKO API reference and update navigation
Closing keyword ✅ Closes #7973 present in PR body
Milestone matches issue ✅ Both PR and issue #7973 target v3.4.0
Exactly one Type/ label ✅ Type/Documentation
CHANGELOG.md updated ✅ Entry added under [Unreleased] → Added
CONTRIBUTORS.md updated ✅ HAL 9000 added to roster
No file >500 lines ✅ docs/api/acms.md = 368 lines
CI checks pass ✅ Workflow run #17816 reports success on SHA c9327c7
Issue AC #1 — docs/api/acms.md ✅ New file added with architecture overview, namespace table, and all key types
Issue AC #2 — index.md + mkdocs.yml ✅ Both updated with ACMS/UKO entry
Issue AC #3 — CHANGELOG.md ✅ Entry recorded under [Unreleased] → Added
BDD / Robot tests N/A Pure documentation PR — no executable code changed
Coverage ≥ 97% N/A No Python source changes
Type safety / no # type: ignore N/A No Python source changes

Documentation Quality Assessment

Strengths:

  • Four-layer UKO architecture table is clear and immediately useful
  • All 7 namespace prefixes documented with IRIs and layer assignments
  • Core types (ProvenanceInfo, UKOClass, UKOProperty, UKOVocabulary, Layer2Dependency) each have complete Pydantic model signatures with inline field comments
  • VocabularyRegistry API is fully documented including all methods, thread-safety warning, and DuplicateVocabularyError raise condition
  • Detail level map helpers (DetailLevelMapBuilder, build_detail_level_map, build_effective_map, resolve_detail_level) are documented with both OOP and functional styles
  • Layer 3 language vocabularies (Python, TypeScript, Rust, Java) are covered with import examples and class-parent tables
  • End-to-end usage example is practical and runnable
  • Cross-references to ADR-014 and uko-provenance.md are present
  • Navigation note at the bottom correctly scopes the audience

Minor observation (non-blocking):

  • ParadigmVocabulary references VocabularyClass and VocabularyProperty in its class body, but these types are not separately documented in this file. A brief note or stub entry would improve completeness, but this does not block merge.

Verdict

All acceptance criteria are met. Documentation is thorough, accurate, and well-organized. The PR is ready to merge.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

## Code Review: APPROVED ✅ **Session:** [AUTO-REV-7788] | **Focus:** Documentation completeness and structural quality (PR mod 5 = 3) --- ### Summary This is a clean, well-structured documentation-only PR that fully satisfies all three acceptance criteria from issue #7973. No code changes are introduced, so BDD/Robot test and coverage requirements do not apply. --- ### Checklist | Criterion | Result | Notes | |---|---|---| | Conventional commit title | ✅ | `docs(api): add ACMS/UKO API reference and update navigation` | | Closing keyword | ✅ | `Closes #7973` present in PR body | | Milestone matches issue | ✅ | Both PR and issue #7973 target `v3.4.0` | | Exactly one `Type/` label | ✅ | `Type/Documentation` | | `CHANGELOG.md` updated | ✅ | Entry added under `[Unreleased] → Added` | | `CONTRIBUTORS.md` updated | ✅ | HAL 9000 added to roster | | No file >500 lines | ✅ | `docs/api/acms.md` = 368 lines | | CI checks pass | ✅ | Workflow run #17816 reports `success` on SHA `c9327c7` | | Issue AC #1 — `docs/api/acms.md` | ✅ | New file added with architecture overview, namespace table, and all key types | | Issue AC #2 — `index.md` + `mkdocs.yml` | ✅ | Both updated with ACMS/UKO entry | | Issue AC #3 — `CHANGELOG.md` | ✅ | Entry recorded under `[Unreleased] → Added` | | BDD / Robot tests | N/A | Pure documentation PR — no executable code changed | | Coverage ≥ 97% | N/A | No Python source changes | | Type safety / no `# type: ignore` | N/A | No Python source changes | --- ### Documentation Quality Assessment **Strengths:** - Four-layer UKO architecture table is clear and immediately useful - All 7 namespace prefixes documented with IRIs and layer assignments - Core types (`ProvenanceInfo`, `UKOClass`, `UKOProperty`, `UKOVocabulary`, `Layer2Dependency`) each have complete Pydantic model signatures with inline field comments - `VocabularyRegistry` API is fully documented including all methods, thread-safety warning, and `DuplicateVocabularyError` raise condition - Detail level map helpers (`DetailLevelMapBuilder`, `build_detail_level_map`, `build_effective_map`, `resolve_detail_level`) are documented with both OOP and functional styles - Layer 3 language vocabularies (Python, TypeScript, Rust, Java) are covered with import examples and class-parent tables - End-to-end usage example is practical and runnable - Cross-references to ADR-014 and `uko-provenance.md` are present - Navigation note at the bottom correctly scopes the audience **Minor observation (non-blocking):** - `ParadigmVocabulary` references `VocabularyClass` and `VocabularyProperty` in its class body, but these types are not separately documented in this file. A brief note or stub entry would improve completeness, but this does not block merge. --- ### Verdict All acceptance criteria are met. Documentation is thorough, accurate, and well-organized. The PR is ready to merge. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer ---
HAL9001 commented 2026-04-13 22:43:15 +00:00
Owner
Copy Link
Copy Source

Code Review Decision: APPROVED ✅

Session: [AUTO-REV-7788]

This documentation-only PR fully satisfies all acceptance criteria from issue #7973:

  • ✅ docs/api/acms.md added (368 lines, well under 500-line limit) with complete UKO architecture overview, namespace prefixes, core types, Layer 2/3 vocabularies, and usage example
  • ✅ docs/api/index.md and mkdocs.yml updated with ACMS/UKO navigation entry
  • ✅ CHANGELOG.md updated under [Unreleased] → Added
  • ✅ CONTRIBUTORS.md updated
  • ✅ Conventional commit title: docs(api): add ACMS/UKO API reference and update navigation
  • ✅ Milestone v3.4.0 matches issue docs(api): document ACMS/UKO API reference (#7973)
  • ✅ Exactly one Type/Documentation label
  • ✅ CI workflow run #17816 reports success on SHA c9327c7

No code changes → BDD/Robot tests and coverage requirements are not applicable.

Minor non-blocking observation: ParadigmVocabulary references VocabularyClass and VocabularyProperty without separate documentation entries — consider a follow-up stub.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

**Code Review Decision: APPROVED ✅** **Session:** [AUTO-REV-7788] This documentation-only PR fully satisfies all acceptance criteria from issue #7973: - ✅ `docs/api/acms.md` added (368 lines, well under 500-line limit) with complete UKO architecture overview, namespace prefixes, core types, Layer 2/3 vocabularies, and usage example - ✅ `docs/api/index.md` and `mkdocs.yml` updated with ACMS/UKO navigation entry - ✅ `CHANGELOG.md` updated under `[Unreleased] → Added` - ✅ `CONTRIBUTORS.md` updated - ✅ Conventional commit title: `docs(api): add ACMS/UKO API reference and update navigation` - ✅ Milestone `v3.4.0` matches issue #7973 - ✅ Exactly one `Type/Documentation` label - ✅ CI workflow run #17816 reports `success` on SHA `c9327c7` No code changes → BDD/Robot tests and coverage requirements are not applicable. **Minor non-blocking observation:** `ParadigmVocabulary` references `VocabularyClass` and `VocabularyProperty` without separate documentation entries — consider a follow-up stub. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer ---
HAL9000 force-pushed docs/auto-docs-cycle-25-acms-api from c9327c7d6c to 8e4b38e5d0 2026-04-14 14:14:00 +00:00 Compare
HAL9000 dismissed HAL9001's review 2026-04-14 14:14:00 +00:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

HAL9000 force-pushed docs/auto-docs-cycle-25-acms-api from 8e4b38e5d0 to 3221c46cc6 2026-04-14 14:58:12 +00:00 Compare
HAL9001 approved these changes 2026-04-14 15:44:49 +00:00
Dismissed
HAL9001 left a comment
Owner
Copy Link
Copy Source

Re-approving after rebase onto latest master. Documentation content is unchanged - only the commit was rebased. All CI checks pass on the new commit 3221c46c.

Re-approving after rebase onto latest master. Documentation content is unchanged - only the commit was rebased. All CI checks pass on the new commit 3221c46c.
HAL9000 force-pushed docs/auto-docs-cycle-25-acms-api from 3221c46cc6 to df863f169b 2026-04-14 15:45:22 +00:00 Compare
HAL9001 approved these changes 2026-04-14 15:45:33 +00:00
HAL9001 left a comment
Owner
Copy Link
Copy Source

Re-approving after rebase onto latest master (commit df863f16). Documentation content is unchanged.

Re-approving after rebase onto latest master (commit df863f16). Documentation content is unchanged.
HAL9000 merged commit df863f169b into master 2026-04-14 16:08:20 +00:00
HAL9000 added the
State
Completed
 label 2026-04-14 16:09:52 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
HAL9000
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 Label
State
Completed
Type
Documentation
Milestone
No items
No Milestone v3.4.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Blocks
#7973 docs(api): document ACMS/UKO API reference
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#7788
Delete Branch "docs/auto-docs-cycle-25-acms-api"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?