Add committed dashboard-copy parity test (automation vs repoman)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github, shell
- Domain
- testing-qa
Research direction
Start with the existing tests/test-vendor-engine.sh to match the shell test style. The new test should fetch automation's dashboard script and lib files with gh api at a pinned SHA kept as a constant, then diff them against the vendored copies in the automation-health-dashboard skill. Done means the test passes on identical copies, fails when either side changes alone, and has an offline escape hatch. The issue does not settle the cache design or the exact file list.
Written by the indexing model from the issue text.
Description
Re-filed from rossoctl/agent-skills#47 (originally opened by @rubambiza) after RepoMan was cloned into this repo. Original discussion/history lives there.
Still applies in repoman: only
tests/test-vendor-engine.shexists; no dashboard-copy parity check. Title updated from "automation vs agent-skills" to "automation vs repoman". Closely related to the standalone-skill resync (#5).
The automation-health-dashboard skill vendors a byte-for-byte copy of the
automation repo's dashboard script + lib set. The RepoMan Phase 5 spec
(§Testing, "Dashboard-copy parity") wants a committed parity assertion so
the copy cannot silently drift — a one-time manual check is exactly how it went
stale before (rossoctl/automation#100, surfaced again by clawgenti on PR #46).
Proposed approach: a committed test that fetches automation's copies via
gh api at a pinned ref/SHA (stored as a constant) and diffs them against the
in-repo copies, failing loudly in CI when either side changes without the
other. Preferred over a vendored snapshot, which is just a second manual copy
that can drift the same way. Costs: a CI network dependency (mitigate with a
short cache or a SKIP_PARITY_CHECK offline escape hatch) and a visible
single-line pinned-SHA bump whenever automation's dashboard changes
intentionally.
Deferred out of PR #46 (verbatim-resync scope); fits the RepoMan Phase 6
dashboard-hardening pass.
Assisted-By: Claude Code
Update: the two inherited github-api.sh correctness bugs that were briefly tracked here have been split out to rossoctl/automation#103 and fixed on the Phase 5 automation branch (re-synced here in f039911). This issue now covers only the committed copy-parity guard (Phase 6).
- Dominant language
- Shell
- Stars
- 7
- Forks
- 1
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/repoman
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
doc-drift
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Document the contributor workflow: repo topology + engine vendoringPossibly taken @jimcadden claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 3/5 Half a day Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
All issues in rossoctl/repoman
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
blocked
Difficulty 1/5 Under an hour Newbie friendliness 73/100
fullsend-ai/agents#1908 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
5700模组网络优先级问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
luainkernel/lunatik#2372 ·
Maintainers usually reply within 1 day