Compare commits
1 Commits
burn/1459-
...
fix/1413
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
3fbcdd606a |
31
docs/issue-1413-verification.md
Normal file
31
docs/issue-1413-verification.md
Normal file
@@ -0,0 +1,31 @@
|
||||
# Issue #1413 Verification
|
||||
|
||||
Status: already implemented on `main`
|
||||
|
||||
## Acceptance criteria check
|
||||
|
||||
1. ✅ `deploy.sh` comment for `nexus-main` uses port `8765`
|
||||
- Evidence: `deploy.sh:3`
|
||||
2. ✅ `deploy.sh` comment for `nexus-staging` uses port `8766`
|
||||
- Evidence: `deploy.sh:4`
|
||||
3. ✅ `docker-compose.yml` confirms those bindings
|
||||
- Evidence: `docker-compose.yml:9` is `"8765:8765"`
|
||||
- Evidence: `docker-compose.yml:15` is `"8766:8765"`
|
||||
|
||||
## Why no code fix was needed
|
||||
|
||||
The issue describes stale comments (`4200` / `4201`), but the current `main` branch already contains the corrected comments:
|
||||
|
||||
```text
|
||||
# Usage: ./deploy.sh — rebuild and restart nexus-main (port 8765)
|
||||
# ./deploy.sh staging — rebuild and restart nexus-staging (port 8766)
|
||||
```
|
||||
|
||||
## Value added in this PR
|
||||
|
||||
- adds `tests/test_deploy_script_ports.py` so future drift between `deploy.sh` comments and `docker-compose.yml` is caught automatically
|
||||
- documents the verification outcome here so the issue can be closed without reimplementing an already-merged fix
|
||||
|
||||
## Recommendation
|
||||
|
||||
Close issue #1413 as already implemented.
|
||||
@@ -1,140 +0,0 @@
|
||||
# timmy-home Backlog Triage Report
|
||||
|
||||
**Generated:** 2026-04-15
|
||||
**Issue:** the-nexus #1459
|
||||
**Source:** Timmy_Foundation/timmy-home
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
| Metric | Count |
|
||||
|--------|-------|
|
||||
| Total open items | 231 |
|
||||
| Open issues | 228 |
|
||||
| Open PRs | 3 |
|
||||
| Issues older than 30 days | 0 |
|
||||
|
||||
The backlog has grown from 220 (per #1127 triage) to 228. However, no issues are older than 30 days — this is a recent accumulation, not legacy rot.
|
||||
|
||||
---
|
||||
|
||||
## Distribution by Assignee
|
||||
|
||||
| Agent | Issues | % of Total | Assessment |
|
||||
|-------|--------|-----------|------------|
|
||||
| Timmy | 76 | 33% | Heaviest load — needs prioritization |
|
||||
| ezra | 39 | 17% | Moderate — batch pipeline work |
|
||||
| allegro | 28 | 12% | Moderate — fleet/infrastructure |
|
||||
| hermes | 19 | 8% | Orchestration tasks |
|
||||
| gemini | 15 | 7% | Review/docs |
|
||||
| Rockachopa | 14 | 6% | Architecture decisions |
|
||||
| claude | 9 | 4% | Code review |
|
||||
| claw-code | 7 | 3% | Code generation |
|
||||
| perplexity | 6 | 3% | Research |
|
||||
| codex-agent | 6 | 3% | Automation |
|
||||
| **unassigned** | **~9** | **4%** | Needs owners |
|
||||
|
||||
---
|
||||
|
||||
## Distribution by Label
|
||||
|
||||
| Label | Count | Action |
|
||||
|-------|-------|--------|
|
||||
| batch-pipeline | 19 | Merge-ready training data — auto-merge candidates |
|
||||
| claw-code-in-progress | 8 | Verify status — may be stale |
|
||||
| fleet | 8 | Infrastructure — review by allegro |
|
||||
| kimi-done | 8 | Verify completion — close if truly done |
|
||||
| epic | 7 | Track progress — break into smaller issues if stalled |
|
||||
| progression | 7 | Fleet progression — monitor but don't close |
|
||||
| architecture | 4 | Needs review by Rockachopa |
|
||||
| study | 3 | Research — assign to perplexity |
|
||||
| phase-* | 5 | Long-term progression — leave open |
|
||||
| No label | ~140+ | Needs categorization |
|
||||
|
||||
---
|
||||
|
||||
## Triage Actions
|
||||
|
||||
### 1. Auto-Merge Candidates (19 issues)
|
||||
|
||||
The 19 `batch-pipeline` issues are training data generation tasks. If their PRs pass tests, merge:
|
||||
|
||||
```
|
||||
Label: batch-pipeline
|
||||
Action: Check each for open PRs. Merge if green.
|
||||
Risk: Low — data-only changes
|
||||
```
|
||||
|
||||
### 2. Stale Status Checks (16 issues)
|
||||
|
||||
Verify these labels reflect current state:
|
||||
|
||||
```
|
||||
Label: claw-code-in-progress (8)
|
||||
Action: Check if work is actually in progress. Close stale ones.
|
||||
|
||||
Label: kimi-done (8)
|
||||
Action: Verify completion. Close if truly done or re-assign if not.
|
||||
```
|
||||
|
||||
### 3. Unassigned Issues (~9)
|
||||
|
||||
```
|
||||
Action: Assign to appropriate agent or close if no longer relevant.
|
||||
Priority: High — unassigned issues accumulate fastest.
|
||||
```
|
||||
|
||||
### 4. Epic Tracking (7 issues)
|
||||
|
||||
```
|
||||
Label: epic
|
||||
Action: Review progress. Break stalled epics into smaller actionable items.
|
||||
```
|
||||
|
||||
### 5. No-Label Issues (~140+)
|
||||
|
||||
```
|
||||
Action: Apply labels for categorization.
|
||||
Priority: Medium — improves searchability and routing.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Recommendations
|
||||
|
||||
### Immediate (this week)
|
||||
|
||||
1. **Close done-done issues**: Run through `kimi-done` and `claw-code-in-progress` labels. Close anything completed.
|
||||
2. **Assign unassigned**: Route ~9 unassigned issues to agents.
|
||||
3. **Auto-merge training data**: The 19 `batch-pipeline` PRs are low-risk merges.
|
||||
|
||||
### Short-term (this month)
|
||||
|
||||
4. **Label the label-less**: Apply `batch-pipeline`, `bug`, `feature`, `process` labels to ~140+ unlabeled issues.
|
||||
5. **Epic decomposition**: Break stalled epics into P0/P1/P2 issues with clear owners.
|
||||
6. **Stale PR cleanup**: The 3 open PRs should be reviewed or closed.
|
||||
|
||||
### Long-term
|
||||
|
||||
7. **Backlog cap**: Set a soft cap (e.g., 150 open issues). When exceeded, mandatory triage before new issues.
|
||||
8. **Triage cadence**: Weekly automated triage via cron job.
|
||||
9. **Agent load balancing**: Timmy has 76 issues (33% of total). Redistribute.
|
||||
|
||||
---
|
||||
|
||||
## Health Assessment
|
||||
|
||||
| Factor | Score | Notes |
|
||||
|--------|-------|-------|
|
||||
| Freshness | Good | No issues older than 30 days |
|
||||
| Labeling | Poor | ~60% of issues have no labels |
|
||||
| Assignment | Fair | 96% assigned, but Timmy is overloaded |
|
||||
| Staleness | Good | `claw-code-in-progress` needs verification |
|
||||
| Velocity | Unknown | Need merge-rate data |
|
||||
|
||||
**Overall: Yellow.** The backlog is fresh but growing. Label hygiene and load balancing are the biggest gaps.
|
||||
|
||||
---
|
||||
|
||||
*Generated by backlog triage. Ref: the-nexus #1459.*
|
||||
25
tests/test_deploy_script_ports.py
Normal file
25
tests/test_deploy_script_ports.py
Normal file
@@ -0,0 +1,25 @@
|
||||
from pathlib import Path
|
||||
|
||||
|
||||
NEXUS_ROOT = Path(__file__).resolve().parent.parent
|
||||
|
||||
|
||||
def test_deploy_sh_header_comments_match_live_ports():
|
||||
deploy_sh = (NEXUS_ROOT / "deploy.sh").read_text()
|
||||
assert "(port 8765)" in deploy_sh, "deploy.sh should document nexus-main on port 8765"
|
||||
assert "(port 8766)" in deploy_sh, "deploy.sh should document nexus-staging on port 8766"
|
||||
assert "4200" not in deploy_sh, "stale 4200 comment should not remain in deploy.sh"
|
||||
assert "4201" not in deploy_sh, "stale 4201 comment should not remain in deploy.sh"
|
||||
|
||||
|
||||
def test_deploy_sh_comments_match_docker_compose_bindings():
|
||||
deploy_sh = (NEXUS_ROOT / "deploy.sh").read_text().splitlines()
|
||||
compose = (NEXUS_ROOT / "docker-compose.yml").read_text()
|
||||
|
||||
main_comment = next(line for line in deploy_sh if "nexus-main" in line and "port" in line)
|
||||
staging_comment = next(line for line in deploy_sh if "nexus-staging" in line and "port" in line)
|
||||
|
||||
assert '"8765:8765"' in compose, "docker-compose should expose nexus-main on 8765"
|
||||
assert '"8766:8765"' in compose, "docker-compose should expose nexus-staging via host port 8766"
|
||||
assert "8765" in main_comment, "nexus-main deploy comment should cite 8765"
|
||||
assert "8766" in staging_comment, "nexus-staging deploy comment should cite 8766"
|
||||
Reference in New Issue
Block a user