land: area/dispatch 386cf14bbe (dispatch)

This commit is contained in:
thePR0M3TH3AN committed 2026-10-19 15:52:15 -04:00
commit fa538097bd
12 files changed
+126 -21

No files matched your search

@@ -0,0 +1 @@
Goal: TODO backlog progress, bug fixes, robustness and usability. Scope: dispatch triage and proposed first team. Non-goals: product edits, worker launch before approval, deploys, spending, production data. Done: goal recorded, baseline measured, concrete first-team proposal presented.
@@ -0,0 +1 @@
Use the existing backlog as the starting point; verify stale reports. Keep the initial team as small as evidence permits. No product edits by dispatch. Conservative operating limits are manager defaults, not attributed owner quotes.
+2 -5
View File
@@ -1,8 +1,5 @@
# TODO — what each area did NOT finish
One section per area. Each session updates its own section before it stops: what is
half-done, where it is, and what the next step is. Newest first inside a section.
## dispatch
## <area id>
- YYYY-MM-DD: <what is unfinished> — <where (branch, file, SHA)> — next: <step>
- 2026-10-19: dispatch-1 startup goal and one-worker proposal prepared. Baseline at d9059116: lint 11/11, unit run completed 219 files before profile-modal suite timed out at 60s; isolated unrestricted rerun reproduced timeout; 205 files remain untested. fleet/TEAM-PROPOSAL.md proposes one client-reliability worker for this blocker, with queued torrent-probe lifetime as a later candidate. Await first-worker approval before adding/launching it. No product edits or workers started.
+11 -16
View File
@@ -1,30 +1,25 @@
# Program — the owner's priorities and rulings
Kept by the session manager. Short on purpose: the backlog holds the tasks, RESUME-BRIEF.md
what is mid-flight. Every ruling is DATED and QUOTES the owner; session-manager calls are
marked vetoable.
Last updated: YYYY-MM-DD
Last updated: 2026-10-19
## Current milestone
TODO: one paragraph.
Work through the existing TODO backlog and fix reproducible bugs that make the client less robust or usable. Validate old reports at current HEAD before assigning them; deliver small, checked changes through local unstable.
## Priorities (owner's order)
## Priorities
1. TODO
2. TODO
1. Owner direction: TODO backlog progress, bug fixes, robustness, and usability.
2. Session-manager sequencing (vetoable): prioritize reproducible failures in core user flows and small changes with clear completion checks.
## Rulings log (newest first)
<!-- Format:
### YYYY-MM-DD HH:MM — <short title>
> "<the owner's exact words>" — owner
Applies to: <areas>. Recorded by: <session>.
### 2026-10-19 — Initial goal
> "lets try to work our way through some of the issues in the TODO backlog and find and bugs and generaly make the client more robust and usable. ." — owner
Applies to: all areas. Recorded by: dispatch.
### YYYY-MM-DD HH:MM — <short title> (session manager call, VETOABLE)
What was decided and why, in two lines. The owner overrides by saying so.
-->
### 2026-10-19 — Conservative startup limits (session manager call, VETOABLE)
No deploys, spending, production data, real-wallet operations, or scheduler activation. Present the first team for owner approval before starting workers.
## Standing rules
+9
View File
@@ -0,0 +1,9 @@
{
"id": "dispatch-1",
"area": "dispatch",
"status": "in-progress",
"title": "Record owner goal, establish baseline, and prepare first worker proposal",
"blockedOn": null,
"addedOn": "2026-10-19",
"filedAt": "d90591163f3db6ff99c1cfad6b736bbb1ee98a59"
}
+24
View File
@@ -0,0 +1,24 @@
# bitvid fleet goal
Recorded 2026-10-19.
## Owner direction
> "lets try to work our way through some of the issues in the TODO backlog and find and bugs and generaly make the client more robust and usable. ." — owner
## Working goal
Work through the existing TODO backlog, find and fix bugs, and make the client more robust and usable. Revalidate older reports against current unstable before assigning work. Prefer small fixes to user-facing failures with reproducible evidence and regression protection.
## Success criteria
- Each selected item has a current reproduction or a documented already-fixed result.
- Fixes preserve playback, magnet safety, signer requirements, and existing test integrity.
- Relevant checks and full required gates pass; report counts and unverified behavior.
- Completed changes land through the local unstable queue before backlog closure.
## Operating limits
- No deploys, spending, production data, or real-wallet operations; conservative session-manager defaults, not additional owner rulings.
- First worker launch requires the owner's approval of the proposed team.
- No scheduler or cron activation is implied by fleet startup.
+10
View File
@@ -0,0 +1,10 @@
# Fleet log
## 2026-10-19 — Initial startup
- Owner goal recorded: TODO backlog progress, bug fixes, robustness and usability. Startup SHA d9059116.
- Installed 441 locked packages. Lint passed all 11 checks; initial sandbox git-grep EPERM resolved by an unrestricted rerun.
- Full bounded unit baseline: exit 1; 219 files completed, profile-modal controller timed out at 60s, 205 files untested. Isolated unrestricted rerun: same timeout (exit 1). Cause unclassified; no full-suite pass claimed.
- Proposed one Codex client-reliability worker to diagnose/fix the profile-modal hang without weakening assertions or masking it with forced exits. The queued torrent-probe lifetime issue from TODO #34 is a subsequent unassigned candidate.
- Open GitHub PRs: 0; local landing queue initially 0. No workers, roster additions, product edits, or schedules started.
- Needs owner: approval of the concrete first-worker proposal in TEAM-PROPOSAL.md. Browser, Amber, live-site, and remaining unit files unverified.
+36
View File
@@ -0,0 +1,36 @@
# Proposed first team — 2026-10-19
Status: awaiting owner approval. No worker area registered or launched.
## Team
- dispatch: triage TODOs, verify evidence and landings, keep the team small; no product code.
- client-reliability: one Codex worker on the configured project-default model. First item: diagnose and fix the profile-modal suite hang that prevents a complete validation baseline, then return to one bounded client bug at a time.
## First item: restore meaningful profile-modal validation
Evidence at d9059116:
- Full unit baseline with `UNIT_TEST_TIMEOUT_MS=60000 npm test`: exit 1. 219 files completed with exit 0; file 220, tests/profile-modal-controller.test.mjs, timed out after 60s. 205 files were not reached.
- Isolated rerun outside the sandbox, same runner/filter and 60s bound: exit 1, same timeout. This is reproducible outside the sandbox, but its cause is unclassified.
- Isolated output last starts the show()/hide() focus/wallet scenario; use readable reporter output to identify the blocked await or retained resources. This clue is not a root-cause claim.
- Lint passed all 11 checks outside the sandbox. Public open PRs: 0; local landing queue initially empty; roster has only dispatch.
- Pre-launch TODO #11 calls for reliable tests; #2 explicitly requests additional profile-pane history wiring coverage. Do not expand into #2 until the first item is complete.
Ownership: tests/profile-modal-controller.test.mjs and narrow profile-modal lifecycle/helper code needed for the diagnosed defect, plus a focused regression and Test Integrity Note. Do not edit js/app.js, global test discovery, unrelated test files, signers, storage credentials, payments, or styling. Request a scope adjustment if the evidence points elsewhere.
Done:
1. Classify the hang as client behavior, harness behavior, or resource cleanup; reproduce the real boundary before fixing it.
2. Preserve all assertions and their intended behavior. No retries, extra sleeps, timeout increases, quarantine, deletion, or forced successful exits. Use proper cleanup and deterministic boundary mocks as indicated by evidence.
3. Pin the root cause with a scenario regression and a deliberately broken variant that fails; include the required Test Integrity Note.
4. Run the isolated suite and full unit suite to natural completion, required lint, and relevant build/browser checks if product code changes. Report exact counts and any remaining environmental blockers.
5. Commit with backlog id, merge unstable, check the merged tree, and submit through landq. Close only with durable landed status plus unstable ancestry.
## Next candidate, unassigned
TODO #34 Stage 3: prune obsolete queued torrent source-health work when its last card/grid owner disappears. js/gridHealth.js has no queue ownership/cancellation handle, and observer disposal has no unregister callback for queued probes. A dependency-free probe of its actual ProbeQueue class retained one waiting job and ran it once after the blocker released; cancellation API was absent. This demonstrates queue behavior, not browser CPU or an end-to-end navigation reproduction. Preserve shared live-card checks, priority, deduplication, concurrency limits, and hidden-card reveal. Reassess after the validation gate is usable.
## Boundaries
No deploys, spending, production data, real-wallet operations, or schedules. Older backlog fixes awaiting real-phone/Amber or live-site evidence remain open. No additional workers proposed now.
@@ -0,0 +1,9 @@
# Dispatch startup baseline — d9059116
- Initial `npm test`: exit 1, first file could not import nostr-tools (dependencies absent). No client correctness conclusion.
- Initial `npm run lint`: exit 127, stylelint absent.
- `npm ci --ignore-scripts --cache /tmp/bitvid-dispatch-npm-cache --no-audit --no-fund`: exit 0, installed 441 packages. No package/lockfile edits requested.
- `npm run lint` after install: exit 2, lint:css passed, lint:hex stopped at `spawnSync git EPERM`; sandbox restriction. Unrestricted rerun in progress.
- `UNIT_TEST_TIMEOUT_MS=60000 npm test`: running; retain per-file bound rather than wait indefinitely on a hanging suite.
- Public GitHub open PR list: 0. Local landing queue: 0, no drain running. Fleet backlog: 0 dispatch items.
- Not verified: browser behavior, real signers, production behavior, full baseline completion. No workers started.
@@ -0,0 +1,10 @@
# Startup verification — d9059116
- `npm ci --ignore-scripts --cache /tmp/bitvid-dispatch-npm-cache --no-audit --no-fund`: exit 0; 441 packages installed.
- `npm run lint` outside sandbox: exit 0, all 11 lint checks. Earlier sandbox run stopped at git-grep EPERM (exit 2); pre-install runs lacked dependencies.
- `UNIT_TEST_TIMEOUT_MS=60000 npm test`: exit 1; 219 test files exited 0; tests/profile-modal-controller.test.mjs timed out at 60000ms as file 220 of 425; 205 untested. Count is files, not individual assertions.
- `UNIT_TEST_TIMEOUT_MS=60000 node scripts/run-unit-tests.mjs profile-modal-controller.test.mjs` outside sandbox: exit 1, same 60000ms timeout. No test code changed. Root cause not yet diagnosed.
- Actual ProbeQueue class, concurrency 1: 1 waiting job, 1 eventual start, no cancel method; exit 0. Isolated queue observation only, not navigation/CPU measurement.
- GitHub public API: 0 open PRs. Fleet initial landing queue: 0; no drain. Initial worker roster: dispatch only.
- `git diff --check`: exit 0 for tracked documentation changes.
- Not verified: 205 remaining unit files, browser QA, real signers, live-site behavior, build/release qualification. No product code or tests changed.
@@ -0,0 +1,5 @@
- [x] Read startup rules and owner direction.
- [x] Write fleet/GOAL.md and PROGRAM.md.
- [ ] Inspect TODO candidates and existing fleet backlog.
- [ ] Run baseline tests and lint; log results.
- [ ] Prepare first-team scope and request launch approval.
@@ -0,0 +1,8 @@
- [x] Record owner goal and limits.
- [x] Inspect TODO candidates and current fleet state.
- [x] Measure baseline and reproduce profile-modal timeout outside sandbox.
- [x] Prepare concrete one-worker proposal.
- [ ] Commit and land startup documentation.
- [ ] Obtain approval before registering or launching the first worker.
Blocked/questions: first-worker launch awaits owner approval; 205 unit files remain untested behind the profile-modal timeout.