Skip to content

self-development: Fix configuration alignment issues#453

Merged
gjkim42 merged 1 commit intomainfrom
axon-self-update-20260227-0600
Feb 27, 2026
Merged

self-development: Fix configuration alignment issues#453
gjkim42 merged 1 commit intomainfrom
axon-self-update-20260227-0600

Conversation

@axon-agent
Copy link

@axon-agent axon-agent bot commented Feb 27, 2026

🤖 Axon Agent @gjkim42

Summary

Focused review of Configuration Alignment across self-development workflow files. Three concrete issues found and fixed:

  • Fix priorityLabels typos in axon-workers.yaml: Two label names were misspelled (priority/imporant-soon and priority/import-longterm), which meant the spawner could not match issues with priority/important-soon or priority/important-longterm labels for correct priority ordering. Verified against actual repository labels.
  • Sync agentconfig.yaml with CLAUDE.md conventions: The shared AgentConfig only had identity and basic standards but was missing key project conventions from CLAUDE.md — Makefile targets, testing requirements, logging conventions, and commit message rules. All coding agents now receive these instructions automatically.
  • Add missing ttlSecondsAfterFinished and podOverrides to axon-triage.yaml: This was the only TaskSpawner without a TTL or resource constraints, causing completed triage Task objects to accumulate indefinitely and triage pods to run without resource limits.

Evidence

  • gh label list confirms the correct labels are priority/important-soon and priority/important-longterm
  • CLAUDE.md contains Makefile targets, logging, testing, and commit conventions not present in agentconfig.yaml
  • All other TaskSpawners (axon-workers, axon-fake-strategist, axon-fake-user, axon-self-update) have both ttlSecondsAfterFinished and podOverrides; axon-triage was the only one missing them

Test plan

  • Verify axon-workers TaskSpawner correctly orders issues by priority after label fix
  • Confirm agents pick up the new Project Conventions from agentconfig.yaml
  • Check that triage tasks are cleaned up after TTL expiration

Summary by cubic

Aligned self-development configs to fix priority handling, enforce triage cleanup, and standardize agent behavior with shared project conventions. This improves task ordering, cluster hygiene, and developer consistency.

  • Bug Fixes

    • kelos-workers: corrected priorityLabels to priority/important-soon and priority/important-longterm so issues are ordered correctly.
    • kelos-triage: added ttlSecondsAfterFinished (3600) and pod resource requests/limits (CPU, memory, ephemeral storage) to prevent completed task buildup and enforce limits.
  • New Features

    • AgentConfig: added Project Conventions from CLAUDE.md (Makefile targets, testing, logging, commit rules) so all agents follow the same standards.

Written for commit 4f95872. Summary will update on new commits.

Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

- Fix two typos in axon-workers.yaml priorityLabels:
  "priority/imporant-soon" -> "priority/important-soon"
  "priority/import-longterm" -> "priority/important-longterm"
  These typos meant issues with important-soon and important-longterm
  priorities were not being correctly ordered by the workers spawner.

- Add Project Conventions section to agentconfig.yaml syncing it with
  CLAUDE.md: Makefile targets, testing, logging, and commit message
  conventions are now available to all agents via the shared AgentConfig.

- Add missing ttlSecondsAfterFinished and podOverrides to
  axon-triage.yaml for consistency with other TaskSpawners. Without a
  TTL, completed triage Task objects accumulate indefinitely.
@gjkim42 gjkim42 force-pushed the axon-self-update-20260227-0600 branch from bbea784 to 4f95872 Compare February 27, 2026 15:54
@gjkim42 gjkim42 merged commit b07ac3f into main Feb 27, 2026
6 checks passed
@gjkim42 gjkim42 deleted the axon-self-update-20260227-0600 branch February 27, 2026 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant