You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[cli] Documented scaffold steps leave the post-seed job idle and activity unlinked from streams #2591
Follow-up to #2587 (PRs #2586 and #2589). Target: 0.0.9 canary.3. This is wiring, not design.
A live check of main at 6766130, following the documented scaffold steps exactly: init with a service, plugin install workers --samples, plugin install streams --samples, aspire start, then db init, db generate and db seed. The design renders well (weekly chart, neutral colours, attributed activity), but two #2587 behaviours don't hold:
Post-seed job never runs. With workers and workers-api Running and Healthy, both jobs still show "idle · No executions yet" after db seed. The one idempotent post-seed sample execution from fix(cli): connect record activity and seeded sample execution #2589 doesn't happen on this path.
Activity isn't linked to streams. Events render from the record-changes fallback, but the panel also shows "Record activity is not linked from the record service to this stream resource" and suggests netscript plugin doctor. The documented steps never create the service-to-stream link, so the panel contradicts the events above it.
The CI scaffold.runtime gate likely wires these differently from the documented steps, which is why it passed.
Acceptance
The documented steps alone, with no extra flags or manual edits, produce at least one job execution after seed, and an Activity feed sourced from the linked stream with no "not linked" warning.
A runtime test follows exactly those documented steps, in that order, and asserts both. Break each (skip the handoff, drop the link) and watch the test go red.
If a step is missing from the docs, rather than from the code, fix the docs and the generator together.
use harness. Build issue 2591: the documented scaffold steps must produce a post-seed job execution and a stream-linked Activity feed. This is wiring, not design. Everything is approved by the owner; never wait for an answer. Follow-up PRs are pre-approved.
Golden rules, in order: (1) the idiomatic NetScript way (call the in-repo MCP find_guidance first: CLI scaffold, plugin install, workers lifecycle, streams linking, plugin doctor); (2) SOLID; (3) performance (no polling, no request-path work); (4) doctrine (generated carriers come only from their gen tasks).
Read issue 2591, issue 2587 and the PR 2589 body. Reproduce the bug first from a clean temp workspace using exactly the documented steps: init with a service, plugin install workers --samples, plugin install streams --samples, aspire start, db init, db generate, db seed. Find why the scaffold.runtime CI gate passes while the documented path does not, then fix the generator, the install steps or the docs so that the documented path alone gives at least one job execution after seed and an Activity feed sourced from the linked stream with no not-linked warning.
Gate: a runtime test that follows exactly the documented steps in order and asserts both. Break each (skip the seed handoff, drop the link) and watch it go red, then restore. Under Deno 2.9.7: scoped check, lint, fmt, focused tests, the carrier chain with every check task, and the scaffold.runtime e2e in CI at the final head. Public run dir: repo-relative paths only.
Process: draft PR with Refs #2591 (never Closes or Fixes). Merge origin/main on conflicts; never rebase or force-push. Do NOT merge: netscript main is on hold for the canary.2 cut. Post READY on issue 2591 with the full head sha once every required check is green or skipped by workflow policy, then STOP. Cockpit reviews cross-family and merges.
The documented scaffold flow now dispatches a real sample after database seed while the worker is already running, and shows Activity from the linked record stream without the not-linked warning. Workers observe atomic handoff publication through a filesystem watcher. plugin install --service users persists the service consumer and preserves it on reinstall; the executable walkthrough includes that link.
PostgreSQL scaffold.runtime: 124 passed, 0 failed, 0 skipped, one canonical pass with cleanup.
SQLite runtime: 116 passed, 0 failed, 0 skipped.
Static service/contracts/plugins: 8/5/18 passed, no failures or skips.
Missing seed handoff: expected job RED, real stream-backed Activity PASS.
Missing service link: real completed job PASS, expected link RED.
Restored documentation: completed execution f9b0d79e-f579-43dc-8860-c35f867598b6, real Activity event 8bdd2b01-9694-442a-bd4b-65573c4fbb08.
All three documented cases preserve the resident worker PID and pass exact-AppHost/container cleanup with no owned survivors. Disposable scratch remains available after runtime cleanup.
Deno 2.9.7 validation: 191 focused test/step results pass, independently rerun at this head; the 31-result cleanup repair subset also passes. Scoped check/lint/fmt cover all 21 changed TypeScript files, with the repaired runner rechecked. Final-head root check covers 4206 files, broader quality has a durable PASS receipt (scaffold-2591-final-head-quality), all four carrier generators leave no drift, and all 15 root check tasks pass. Source hashes verify 25/25. Assignment and report files are excluded from Git; deno.lock is unchanged.
Independent same-session cross-family implementation evaluation: PASS at the full head above. Review: #2592 (comment)
All required PR checks are green or skipped by existing workflow policy; the final snapshot has 4 SUCCESS / 23 SKIPPED. The separately dispatched exact-head runtime supplies live acceptance. The desktop job is green under the existing bounded #859 exception; its underlying native update callback limitation remains recorded, with no new waiver. Repo-wide unit lanes were policy-skipped and are not claimed as executed. Review-thread gate: 0 unanswered.
Public run evidence: .llm/runs/orch-divybot-6572256863--2591/. Its candidate snapshots retain earlier failed attempts; the final CI run and linked independent audit above are authoritative. No accepted product debt. The local reproduction AppHost was stopped; unrelated resources were left untouched.
PR remains draft, uses Refs #2591, and leaves the issue open. Do not merge during the canary.2 hold. Cockpit reviews and merges.
Activity
rickylabs commentedon Nov 2, 2026
/swarm
repo: rickylabs/netscript
harness: codex
tier: feature
role: implementer
profile: leaf
model: gpt-6.1-sol
effort: xhigh
max-tokens: 30m
timeout: 6h
approval: bypass
use harness. Build issue 2591: the documented scaffold steps must produce a post-seed job execution and a stream-linked Activity feed. This is wiring, not design. Everything is approved by the owner; never wait for an answer. Follow-up PRs are pre-approved.
Golden rules, in order: (1) the idiomatic NetScript way (call the in-repo MCP find_guidance first: CLI scaffold, plugin install, workers lifecycle, streams linking, plugin doctor); (2) SOLID; (3) performance (no polling, no request-path work); (4) doctrine (generated carriers come only from their gen tasks).
Read issue 2591, issue 2587 and the PR 2589 body. Reproduce the bug first from a clean temp workspace using exactly the documented steps: init with a service, plugin install workers --samples, plugin install streams --samples, aspire start, db init, db generate, db seed. Find why the scaffold.runtime CI gate passes while the documented path does not, then fix the generator, the install steps or the docs so that the documented path alone gives at least one job execution after seed and an Activity feed sourced from the linked stream with no not-linked warning.
Gate: a runtime test that follows exactly the documented steps in order and asserts both. Break each (skip the seed handoff, drop the link) and watch it go red, then restore. Under Deno 2.9.7: scoped check, lint, fmt, focused tests, the carrier chain with every check task, and the scaffold.runtime e2e in CI at the final head. Public run dir: repo-relative paths only.
Process: draft PR with Refs #2591 (never Closes or Fixes). Merge origin/main on conflicts; never rebase or force-push. Do NOT merge: netscript main is on hold for the canary.2 cut. Post READY on issue 2591 with the full head sha once every required check is green or skipped by workflow policy, then STOP. Cockpit reviews cross-family and merges.
rickylabs commentedon Nov 2, 2026
divybot: started. codex is working on this issue on n5-agents with gpt-6.1-sol.
rickylabs commentedon Nov 2, 2026
divybot: pull request opened: #2592
rickylabs commentedon Nov 2, 2026
READY — issue #2591
PR: #2592
Head:
140b79950281c80c22ba5cf3dac221c16a31841eThe documented scaffold flow now dispatches a real sample after database seed while the worker is already running, and shows Activity from the linked record stream without the not-linked warning. Workers observe atomic handoff publication through a filesystem watcher.
plugin install --service userspersists the service consumer and preserves it on reinstall; the executable walkthrough includes that link.Final-head acceptance: https://github.com/rickylabs/netscript/actions/runs/41425306150
scaffold.runtime: 124 passed, 0 failed, 0 skipped, one canonical pass with cleanup.f9b0d79e-f579-43dc-8860-c35f867598b6, real Activity event8bdd2b01-9694-442a-bd4b-65573c4fbb08.Deno 2.9.7 validation: 191 focused test/step results pass, independently rerun at this head; the 31-result cleanup repair subset also passes. Scoped check/lint/fmt cover all 21 changed TypeScript files, with the repaired runner rechecked. Final-head root check covers 4206 files, broader quality has a durable PASS receipt (
scaffold-2591-final-head-quality), all four carrier generators leave no drift, and all 15 root check tasks pass. Source hashes verify 25/25. Assignment and report files are excluded from Git;deno.lockis unchanged.Independent same-session cross-family implementation evaluation: PASS at the full head above. Review: #2592 (comment)
All required PR checks are green or skipped by existing workflow policy; the final snapshot has 4 SUCCESS / 23 SKIPPED. The separately dispatched exact-head runtime supplies live acceptance. The desktop job is green under the existing bounded #859 exception; its underlying native update callback limitation remains recorded, with no new waiver. Repo-wide unit lanes were policy-skipped and are not claimed as executed. Review-thread gate: 0 unanswered.
Public run evidence:
.llm/runs/orch-divybot-6572256863--2591/. Its candidate snapshots retain earlier failed attempts; the final CI run and linked independent audit above are authoritative. No accepted product debt. The local reproduction AppHost was stopped; unrelated resources were left untouched.PR remains draft, uses Refs #2591, and leaves the issue open. Do not merge during the canary.2 hold. Cockpit reviews and merges.
rickylabs commentedon Nov 2, 2026
⏱️ divybot: operator timeout of 6h0m0s exceeded; native stop unconfirmed after bounded retries; run ended. Retry requires a new /swarm comment.
rickylabs commentedon Nov 3, 2026
Completed in #2592.