mosaicstack/stack
25
0
Fork 1
Code Issues 344 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

Row 6 pilot: distinguish relaunched seats from old session activity #1512

New Issue
Open
opened 2026-09-15 00:45:16 +00:00 by darkwing · 0 comments
darkwing commented 2026-09-15 00:45:16 +00:00
Member
Copy Link
Copy Source

Relaunch activity, row 6 behavior assignment

Jason confirmed the #1511 table tag and inspector wording. The code phase's
bounded local delivery is accepted. Under his standing continuation mandate,
start Piece 5's already-specified first Filbert assignment from the control-board
MVP plan: Relaunched seat shows the old last message.

Filbert is sole source author. Darkwing independently reviews backend and tests;
Dewey reviews presentation. Work in the canonical refactor checkout. Preserve
accepted attention, Discord and task-attribution changes and all other owners'
changes. Frozen prior candidates remain unchanged.

Scope: minimal packages/control-board scanner/presentation/tests/docs changes
and corresponding WebUI presentation/tests when needed. If a live matching
registration's startedAt is newer than recorded session activity, show
'relaunched at X, no messages since' instead of presenting an old message as
current activity. Preserve historical transcript data. After new session activity,
normal presentation resumes. Stale/dead registrations must not assert a relaunch.
No effect on connector owner identity or fixed connector task.

Prove the old behavior first with isolated fixtures. Cover newer launch vs old
activity, equality, subsequent new activity, stale registration and unknown/missing
activity. Preserve attention/Seen, task attribution and reply authorization.
Do not silently redesign those semantics. Return an exact frozen candidate,
changed/inherited pins and reproducible tests for both independent reviewers.

No launcher, Claude discovery, credential, role, home, live registration or
service changes by the author. No commits/push or shared tracking edits by the
author. No real seat relaunch is needed for the source fixture tests. Darkwing
owns tracking and any separately authorized integration.

Publication remains a separate gate, including prior unpublished dependencies.
Do not claim Gate F or issue closure from fixture tests. Its eventual evidence
must use the actual assignment dates and demonstrate no direct Jason-to-Filbert
work messages; never backdate the old plan's anticipated 2026-09-13 metric.

# Relaunch activity, row 6 behavior assignment Jason confirmed the #1511 table tag and inspector wording. The code phase's bounded local delivery is accepted. Under his standing continuation mandate, start Piece 5's already-specified first Filbert assignment from the control-board MVP plan: Relaunched seat shows the old last message. Filbert is sole source author. Darkwing independently reviews backend and tests; Dewey reviews presentation. Work in the canonical refactor checkout. Preserve accepted attention, Discord and task-attribution changes and all other owners' changes. Frozen prior candidates remain unchanged. Scope: minimal packages/control-board scanner/presentation/tests/docs changes and corresponding WebUI presentation/tests when needed. If a live matching registration's startedAt is newer than recorded session activity, show 'relaunched at X, no messages since' instead of presenting an old message as current activity. Preserve historical transcript data. After new session activity, normal presentation resumes. Stale/dead registrations must not assert a relaunch. No effect on connector owner identity or fixed connector task. Prove the old behavior first with isolated fixtures. Cover newer launch vs old activity, equality, subsequent new activity, stale registration and unknown/missing activity. Preserve attention/Seen, task attribution and reply authorization. Do not silently redesign those semantics. Return an exact frozen candidate, changed/inherited pins and reproducible tests for both independent reviewers. No launcher, Claude discovery, credential, role, home, live registration or service changes by the author. No commits/push or shared tracking edits by the author. No real seat relaunch is needed for the source fixture tests. Darkwing owns tracking and any separately authorized integration. Publication remains a separate gate, including prior unpublished dependencies. Do not claim Gate F or issue closure from fixture tests. Its eventual evidence must use the actual assignment dates and demonstrate no direct Jason-to-Filbert work messages; never backdate the old plan's anticipated 2026-09-13 metric.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
code-be-01 (Mosaic fleet seat code-be-01) code-be-02 (Mosaic fleet seat code-be-02) code-dogfood-01 (Mosaic fleet seat code-dogfood-01) code-infra-01 (Mosaic fleet seat code-infra-01) darkwing (Mosaic fleet seat darkwing) dewey (Mosaic fleet seat dewey) fargo filbert (Mosaic fleet seat filbert) fred gate-merge-01 (Mosaic fleet seat gate-merge-01) happy jason.woltje (Jason Woltje) marcie merge-gate ops-01 (Mosaic fleet seat ops-01) ops-02 (Mosaic fleet seat ops-02) ops-03 (Mosaic fleet seat ops-03) ops-ci-01 (Mosaic fleet seat ops-ci-01) ops-deploy-01 (Mosaic fleet seat ops-deploy-01) orch-01 (Mosaic fleet seat orch-01) pepper resume rev-code-01 rev-code-02 rev-security-01 rev-security-02 rev-security-03 (Mosaic fleet seat rev-security-03) rocko (Mosaic fleet seat rocko) sanity scooby (Scooby) scrappy shaggy tiny topher (Mosaic fleet seat topher) velma veronica (Mosaic fleet seat veronica) vision woodpecker
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1512