Skip to content

spec(FIX-1497): ER-Collab proof — a graded multi-seat scenario, with the handoff visible - #2045

Merged
jhoffner merged 10 commits into
mainfrom
spec/FIX-1497
Sep 22, 2026
Merged

jhoffner merged 10 commits into
mainfrom
spec/FIX-1497

Conversation

@jhoffner

@jhoffner jhoffner commented Sep 22, 2026 •

Copy link
Copy Markdown
Collaborator

spec(FIX-1497): ER-Collab proof — a graded multi-seat scenario, with the handoff visible

Someone who… Today After
is deciding whether Workforce is ready to ship "Seats collaborate" rests on two checks that each prove a half. Nothing has run them as one scenario, and nothing has watched work change hands One command runs the whole thing on a real hire, and a dated verdict row says which seats ran what and what was observed
asks what happens when the work needs a person The substrate can park a row and take an answer back. That leg has never run on a hired workforce The run stops on a real question, a person answers through the owning seat's own door, and the answer is on the row
wants to watch it hand over Nothing to watch. The labs run headless, so a handoff exists only as rows in a store nobody opens The board is a screen. The row says why it waited and what it was told
has to re-run this proof next release Impossible. It has never been run once One command and a browser, with a control behind every claim
is worried this grows a second, human work plane The fence is written down and nothing has pushed on it Two red states push on it: an answer sent as a second person does not land, and nothing drains on a person's behalf

Four lanes against time: a planner seat files a row, a builder seat claims and parks it with a reason, a person answers through a flow action with no claim and no drain on their lane, the builder finishes and files a second row for another desk, and a reviewer seat completes it. Below a dashed fence, what the DevTool carries at three moments.

Read left to right. The crossing from the builder's lane to the reviewer's is the handoff — one board's rows changing hands, not a field and not a status. The person's lane has no claim on it: that is ER-1, drawn.

How: three seats and one channel, all declared in Markdown, served by the ordinary fsdev dev. The scenario files, drains, parks, is answered, hands over, and is then read in a browser against the shipped DevTool bundle. Everything lives under goals/; nothing under packages/ changes.

What's asked of you

Nothing is open. The one question this spec routed up has been answered, and the two decisions below are for confirmation.

1. The hire: share the DevForce proof's workforce, or give this one its own? — answered

The call: give this one its own. Answered by the owner on 2026-09-22, in this comment:

"Keep them separate. We can combine them later but having separate labs prevents coordination issues for now"

Both reasons are on the record, because they are different reasons. The owner's is about sequencing — separate labs keep the two proofs from colliding while both are in flight, and combining them stays available later, so this is an ordering choice and not a boundary anyone has to argue their way back through. The spec's is technical — FIX-1496's BR-8 forbids board or harness work dispatch reaching its reviewer seat, with the control reviewer-files graded to go red if one does; a shared tree carrying two collaborating seats would have to relax that rule deliberately and be re-gated, costing the first proof the thing it exists to prove.

Recorded as D3. PLAN.md carried a contingency to re-cut S1–S4 onto goals/devforce-lab if the answer came back share; it is gone, and S1–S7 stay under goals/multi-seat-collab/. ER-26 is unchanged — it still fences the graded run on a live hired Workforce existing at all (BR-21), which was never a claim about whose tree the run uses.

Ratified, for confirmation

  1. D1 · The proof drives the shipped dev server and reads the handoff in a real browser, rather than asserting on a store. If wrong: it needs a browser and built DevTool assets to run at all, and it is only ever as strong as the DevTool rows it reads — which are another issue's and not yet merged.
  2. D2 · A handoff is a second row, filed by the seat that finished the first. If wrong: we have fixed what "handed over" means for every later proof, and a future notify-based compose has to be shown equivalent rather than simply replacing it.

Reviewers · look here

  • Rules → BR-15 to BR-17, the observation legs. They read rendering that is content-complete and unmerged (feat(FIX-1481): the parked reason on the task row (ER-Devtool row 4) #2032 for the reason on the row, 9/9 green at 00604930e). Is naming that dependency and running the leg against its head the right call, or should the row be held until it merges?
  • Decisions → D2. Is "two rows, two assignees" the right definition of handed over for every later proof to inherit — given that reassignment is refused by construction on a board that hands off?
  • The POC → poc/served-hire-observable/. The premise it settles (the shipped dev server serves a file-declared hire) and the one it deliberately leaves to the goal check (the run itself).

Not here: the org-level board view that would put both rows on one screen (FIX-1320's), FIX-1474's composed notify-plus-file path (optional, never a gate), and the DevTool rendering itself (FIX-1481's).

Two things found on the way, both settled

  • A stall on the served path, isolated rather than disclosed. Every action POSTed to fsdev dev on the authoring box sat at in_progress forever — including on a shipped goal fixture and a three-line control flow. It is environmental, with one named variable: FSDEV_DEFAULT_MODEL set while no flow declares an intent makes createModelResolver throw, and the served path swallows it. The A/B is in the POC's README: the in-process router completes on both store backings, and the same fsdev dev stalls with the overrides inherited and settles in 0 ms with them stripped. D1 stands. The silent shape of that failure is recorded as a follow-up and raised up (ER-17), not worked around.
  • ER-26 reached main on 2026-09-22, when spec(epic): W5 amendment — three producers named, checklist row 5 re-owned (FIX-1457) #2033 merged. Every citation of it in this set now points at the epic's rule and carries no staleness note. The disposition that declined to de-duplicate those citations is left standing in PLAN.md as the record of what was decided and why — not as a live argument, because the condition it rested on is gone.

Spec · Decisions · Rules · Plan · Docs · POC
· Linear FIX-1497 · epic FIX-1457 (ER-Collab, and this issue owns ER-1) · builds on FIX-1385, FIX-1430, FIX-1440 · reads FIX-1481's rows · merges after human approval and required checks

No changeset: retained spec documents and a POC only, all under specs/ (BP-022).

How to review this — altitude, what's in scope, what's deliberately unsettled

This is a direction set, not an implementation. Reviewing it well means
answering one question: is this the right approach?

In scope to challenge:

  • The problem framing in SPEC.md — are we solving the right thing, for the people named?
  • The approach — will it work, does it fit the architecture and docs/philosophy.md?
  • Any numbered decision in DECISIONS.md — that's the sign-off surface.
  • A case BUSINESS-RULES.md misses, or a rule that would invalidate the design.
  • Scope — a deliverable that shouldn't ship, or one that's missing.
  • The reader-facing promises in DOCS.md and their fit with the rules; a missing or
    misleading lineage claim in conditional EVOLUTION.md.

Out of scope — deliberately unsettled here, and owned by the implementing agent:

  • Names, signatures, file paths, and module layout beyond the few PLAN.md pins on purpose.
  • Local structure: which helper, how a function is decomposed, error-message wording.
  • Micro-optimizations and style preferences.
  • Test names and internal test structure (the behaviours are the rules; the tests are not).
  • Anything PLAN.md left open on purpose — it is directional by design, and a gap at that
    altitude is intended, not an omission.
  • The figures, at the pixel level. A figure is right when it reads right. A misplaced label
    or a colour you'd have chosen differently is not a finding; a figure that shows a shape the
    decisions don't say is.
  • The solution sketch, at the line level. PLAN.md may include a rough pseudocode sketch
    showing the shape of the proposed solution. It is knowingly incomplete, is not real code,
    and is not what will ship. Review it for directional viability only. Do not report
    that it lacks error handling, omits edge cases, names things that don't exist in the repo, or
    wouldn't build: all of that is true on purpose.
  • POC implementation polish. Experiments under the owning spec's poc/ are retained,
    not production code. Read them for directional evidence, not production completeness.
    Their isolation from production/default discovery and absence of secrets or generated
    dependencies are in scope; retention is not permission to weaken repository checks.

One request, if you are an automated reviewer: the two lists above are the whole difference
between a useful review of this document and a long one. Volume is not signal here — a single
finding above the line is worth more than twenty below it.

Feedback in the second list is welcome and gets recorded verbatim in PLAN.md → Notes from review for the implementer to weigh against real code. It will not be argued with, and it
will not be folded into the design prose. Please don't re-raise it: one mention is enough.

The one exception is the sketch and the POC. Line-level feedback on either is dropped, not
recorded — there is nothing for an implementer to weigh about code that isn't shipping. Feedback
about their direction is not line-level and is treated like any other above-the-bar finding.

Direction approval does not waive merge-time required checks, approvals or thread policy.
Optional comments do not require another design round merely to reach zero comments.

🤖 Generated with Claude Code

https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz

…the handoff visible

The retained spec for W5's third exit proof: two seats working one channel's
board, a person answering a parked row through a flow action on the owning
seat, work changing hands, and all of it readable in the shipped DevTool.

Two decisions are the sign-off surface — drive the shipped `fsdev dev` and
read the handoff in a real browser (D1), and a handoff is a second row filed
by the seat that finished the first, never a status and never a reassignment
(D2). One question is routed up rather than answered: whose live hire the
graded run uses.

Carries a retained POC that settled the premise the acceptance rests on — the
shipped dev server registers a file-declared hire as ordinary flow copies, so
the DevTool has something to open and no wrapper is needed. Both of its
controls were run red.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
@vercel

vercel Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Sep 22, 2026 5:17pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Sep 22, 2026 5:17pm UTC
flow-state-dev-ui Ignored Ignored Preview Sep 22, 2026 5:17pm UTC

Request Review

@linear-code

linear-code Bot commented Sep 22, 2026

Copy link
Copy Markdown

FIX-1497

…stands

The POC's stall was isolated rather than left as a disclosure, because two
controls pointing away from the change under test is the shape of a substrate
defect.

It is environmental, with one named variable: FSDEV_DEFAULT_MODEL set while no
flow declares an intent makes createModelResolver throw, and the served path
swallows that into a request that never advances. The A/B, one variable on the
same three-line flow, is in the POC's README — the in-process router completes
on both store backings, and `fsdev dev` over a real socket stalls with the
overrides inherited and settles in 0 ms with them stripped.

So D1 stands. check.mts now strips the overrides the way goals/lib/env does,
and the goal owes the same guardrail. The silent shape of the failure — a
model-resolver throw surfacing as a request that never advances and never
errors, on a flow with no generator in it — is recorded as a follow-up and
raised up (ER-17) rather than worked around.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
@jhoffner
jhoffner marked this pull request as ready for review September 22, 2026 05:08
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-22T05:20:25.206202Z 43540e3 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simplify pass (spec + retained POC)

Verdict: The product shape looks right — a sibling goal under goals/multi-seat-collab instead of extending manager-queue-lab, D2 (handoff = second row), and D1 (served fsdev dev + browser) are well argued against the alternatives in DECISIONS. I would not collapse this into one of the existing labs.

Where complexity crept in anyway is mostly in the retained POC, not in the five-doc spec set:

  1. Registration probe vs mini-scenario — check.mts only reads the served catalog (ids, kinds, action names). hire.ts still builds park/review semantics (awaitReview, onReview: "exit", per-desk dispatchers, full taskBoard). That is honest about what the graded run needs, but it is wider than what this POC proves and is the main thing an implementer might copy wholesale into S2–S4. PLAN already splits host.mts / kinds / thin flows/; I'd treat the POC as tree + four flow shims + serve spawn, and lift worker/planner bodies from manager-queue-lab + channel-boards filing, not from monolithic hire.ts.

  2. Two-source discipline — README correctly warns that deriving SEAT_DESKS from answersFor in hire code is fine for registration and wrong for V2/swapped-desks. The code still encodes the anti-pattern. Consider either stubbing the worker body for the POC or a louder “do not copy deskDispatcher” callout at the top of hire.ts so the implementation PR does not inherit it by reflex.

  3. Canonical env helper — PLAN guardrail says goals/lib/env’s intentFreeEnv. POC check.mts reimplements a subset (and omits undefined dropping / extra). Importing the shared helper would delete drift and matches “exactly as every other goal does.”

  4. Control env naming — operators set POC_CONTROL but spawn passes ER_COLLAB_POC_CONTROL into the child; one name would reduce mis-runs when someone re-checks controls later.

  5. Spec corpus density (optional) — FSDEV_DEFAULT_MODEL / served-path stall, ER-26 / #2033, and the two-fences diagram appear in several files. Not wrong, but trimming to one canonical paragraph (POC README + links elsewhere) would shrink future amend cost. Lower priority than POC shape.

Performance / reuse: No concerns for a one-shot spawn + single catalog fetch; reuse wins are intentFreeEnv, REPO_ROOT/goalTmpDir, manager-queue-lab’s defineBuilderWorkerFlow + caller assignees, and channel-boards-style fileTask dispatcher — as PLAN/sketch already imply.

Checked locally: pnpm tsx specs/issues/FIX-1497/poc/served-hire-observable/check.mts → PASS on catalog legs.

Merge stance: Directionally approve the spec; optional POC slimming / shared intentFreeEnv before or during the implementation PR would make the cited evidence easier to follow without bloating the follow-up diff. None of the above requires re-opening D1/D2.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

Comment thread specs/issues/FIX-1497/PLAN.md Resolved
…forbids

Round 1 of two (BP-040). Cursor directionally approved the spec and reopened
neither D1 nor D2; two items were above the bar and four are recorded for the
implementer.

The one that mattered: PLAN S1 said "start from the POC's tree" while the
POC's hire.ts derives its seat -> desk map from each worker's own answersFor,
which is the two-source routing the same plan's guardrail forbids and
swapped-desks (BR-3) exists to catch. A plan that points the implementer at an
artifact it bans fails silently — the work follows S1 and the control goes red
on it. S1 now says what to take and what never to, a new table splits POC /
sibling labs / never, and hire.ts carries the fence in its own header for the
reader who opens the file without the plan.

Smaller: check.mts imported a weaker copy of goals/lib/env's intentFreeEnv
while PLAN's guardrail says use the shared helper. It now imports it and uses
its `extra` merge — the A/B that verdict rests on is load-bearing for D1, and a
local subset could drift away from it.

Recorded verbatim in PLAN -> Notes from review: the `as never` casts, the
control env naming, the runRow stub trade-off, and the corpus-density note.
The ER-26 half of the density note is declined on the record: a rule not yet on
main must say so wherever it is cited, because a reader arrives at one site.

POC re-run after the change: PASS, plus both controls seen red again.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz

Copy link
Copy Markdown
Collaborator Author

Review round 1 folded — 772986ed1

Round 1 of the two BP-040 allows. Thanks for the pass; the verdict (product shape right, D1 and D2 not reopened, don't collapse into an existing lab) matched where I'd hoped the review would land, and one item was sharper than it looked.

Two folded.

1 · The plan pointed at what the plan forbids. Items 2 and 7 are one defect seen from two ends. PLAN S1 said "start from the POC's tree", while hire.ts derives its seat → desk map from each worker's own answersFor — the two-source routing PLAN's guardrail bans and swapped-desks (BR-3) exists to catch. That is not POC polish: an implementer follows S1, inherits the shape, and the control goes red on work that followed the spec. S1 now says what to take and what never to; a new what comes from the POC, and what must not table splits POC / sibling labs / never; and hire.ts carries the fence as the first thing in its header, for the reader who opens the file without the plan. The POC code is unchanged — its job was one premise, it proved it, and rewriting it costs a re-run of the banked A/B for no added evidence.

2 · The env helper. check.mts now imports intentFreeEnv from goals/lib/env.mts and uses its extra merge; the local subset is gone. Beyond tidiness: the A/B is load-bearing for D1, and a copy that missed a key added later would drift away from the evidence it supports.

Four recorded, not folded — verbatim in PLAN.md → Notes from review, per this PR's own contract: the as never casts (3), the control env naming (4), the runRow stub trade-off (1), and corpus density (5). Inputs for the implementer, unargued.

One half of item 5 is declined on the record. Do not trim the ER-26 / #2033 repetition. A rule that is not yet on main has to say so wherever it is cited, because a reader arrives at one citation site and not at all of them — a single canonical paragraph elsewhere is exactly what they won't have read. The stall paragraph and the two-fences figure are fair game and I've left that judgement to the implementer.

Verification: POC re-run after the change — PASS, plus no-answer (isolating) and no-tree (coarse) both seen red again.

Thanks also for running check.mts locally and saying so; an independent PASS on the catalog legs is worth having in the thread.

The gate remains the owner's, and Open 1 — whose live hire the graded run uses — is untouched by this round and still theirs.


Generated by Claude Code

@jhoffner jhoffner left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FSD Architect — coherence only

Not owner approval. Not the merge gate. Shared jhoffner login; this is Architect's lens on direction and two-direction risk, not Jake signing the Open question.

Call: No silent fork vs in-flight siblings. Round-1 fold at 772986ed1 matches the load-bearing defect the simplify pass found; D1/D2 stay closed; Open 1 correctly stays Jake's.

Against the board

  • #2023 / FIX-1496 — sequencing, not a second DevForce path. Sibling under goals/, leave manager-queue-lab alone, recommend own hire so FIX-1496's one-worker rule is not bent. Same stance Architect already left on #2023.
  • #2033 (draft) — ER-26 citations correctly say "not on main yet"; declining to collapse that repetition is right for a rule readers can hit from one site.
  • #2032 / FIX-1481 — soft browser-leg dep named; no invent of DevTool surface under a QA label.

Fold check. S1's "tree + shims only / never hire.ts map" table plus the hire.ts header fence close the plan-vs-POC two-source defect that would have made swapped-desks grade the map against itself. intentFreeEnv import keeps D1's A/B from drifting. Recorded-not-folded notes are the right altitude for never-merge.

Still Jake's: Open 1 (share FIX-1496 hire vs own). Spec recommendation (own) is the cheaper-to-reverse call; Architect does not close it.

Never-merge record-only. No prelim. No D-n.

— FSD Architect

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 43540e39c7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread specs/issues/FIX-1497/PLAN.md Resolved
Comment thread specs/issues/FIX-1497/BUSINESS-RULES.md Resolved
Comment thread specs/issues/FIX-1497/PLAN.md Resolved
…a re-gate

Codex landed eight findings on 43540e3. Four are folded here. Three (A, B, C)
are verified and reported rather than folded: two change the acceptance and one
restructures the same artifact they reshape, so they go to the coordinator
rather than becoming a guessed push.

Folded:

- one-seat is not an isolating control and no longer claims to be. A single
  seat cannot claim both desks without widening eligibility, and that widening
  puts a review row on a build seat, so BR-3's oracle falls with BR-13. Both
  legs are now attributed, with the reason each goes red and a note that a run
  reddening only one has tested the wrong thing.
- BR-7a is new, and it is the spec gap behind Codex's re-parking finding: the
  resumed attempt is handed the same input that asked the question, so a worker
  branching on what it was asked parks forever. The decision reads the answer,
  which lives on the row. The sketch's park condition changed with it.
- The POC's fixed port is gone. A fixed port plus a matching catalog is a
  false PASS when anything already owns it; the spawned child's exit is now
  watched too, and an exit before readiness fails by name.
- The README's only command failed on a clean checkout. It now carries both
  devtool build steps in order, says why the CLI's own suggestion is not
  enough, and the check names those commands instead of timing out.

POC re-run: PASS, both controls seen red, no-tree now red via the child-exit
guard rather than a generic timeout.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz

Copy link
Copy Markdown
Collaborator Author

Review round 2 — five folded, three need a re-gate · 9ead0e4d7

Round 2 of the two BP-040 allows, so this is the last review round. Codex reviewed 43540e39c7, before round 1's fold; nothing it found was already answered there, so all eight stood.

Verified before folding, per finding. Every verdict below is a command or a file and line, not a reading.

Three are not folds — they go to the owner with the gate

# Finding Verdict
A No aggregate surface for the two-row browser check Confirmed, and it changes the acceptance. taskItems ← requestGroups ← useSessionRequests(effectiveSessionId) — one session only. Ran it: the four task-change fragments land in four different sessions. But there is a surface Codex missed — the board's ledger is an org-scoped collection readable at /sessions/<any seat>/debug/resources/eng.queue.work/items, returning both rows at latest state. It needs an expander, so BR-16 as written still cannot pass. Proposal on the thread: three named screens with the navigation the DevTool docs already describe
B No viable refusal path for an unknown desk Confirmed. The eligibility predicate has no undefined arm, so the row is claimed by nobody and sits pending. The precedented fix is narrower than BR-5 claims: manager-queue-lab admits a row filed for nobody and lets the router refuse it by name. An unknown desk key cannot be refused without a floor seat that design deliberately lacks. Proposal: restate BR-5 to the provable case, record the rest as a known property
C Package manifest in the retained POC Confirmed — straight rule violation. spec-poc/SKILL.md: "do not add workspace membership, package manifests, or root execution scripts for a POC." Package-free shape verified viable (one fsdev.config.mts via --config, replacing the manifest and the four shims). Sequenced behind A, because A reshapes the table that names those shims

Five folded

  • one-seat is not isolating, and no longer claims to be. Codex is right that widening one seat's eligibility necessarily falsifies BR-3's per-seat oracle. Both legs are now attributed with the reason each goes red, plus the part that keeps it honest: a run reddening only one of them has tested the wrong thing.
  • BR-7a is new — the best finding in the pass. The re-parking bug was not only my POC's: BUSINESS-RULES asserted the seat finishes the row after the answer and never said how it knows not to park again. An implementer reading BR-7 alone could write the same infinite loop and be conforming. New rule, new control ignore-the-answer, and the sketch's park condition changed with it.
  • The POC's fixed port and unguarded readiness. A healthy /healthz proves something is listening, not that it is the process this run spawned. Port is now per-run, the child's exit is watched, and no-tree was seen failing through the new branch.
  • The README's only command failed on a clean checkout. Both devtool build steps, in order, with why the CLI's own suggestion is not enough — and check.mts now fails naming them instead of timing out.
  • input.tasks.awaitReview refuted as spec content. taskWorkerInputSchema has no tasks field, so the call throws — but the spec prose never names it (one grep hit, inside a quoted review note). POC-only divergence, left visible.

Verification: POC re-run after the folds — PASS, both controls seen red, no-tree now red via the child-exit guard.

Round budget is spent. A, B and C are a re-gate question for the owner, not a third round, and they sit alongside Open 1, which this pass did not touch.


Generated by Claude Code

@jhoffner jhoffner left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FSD Architect — coherence only (round 2)

Not owner approval. Not the merge gate. Shared jhoffner login; this is Architect on direction and two-direction risk, not Jake closing Open 1 or the re-gate.

Call: Round-2 folds at 9ead0e4d7 stay coherent. A / B / C correctly stay owner re-gate rather than guessed folds. No silent fork vs siblings.

Folds. BR-7a + ignore-the-answer closes a real spec gap (park-forever while conforming). Attributing both legs under one-seat, child-exit ownership of readiness, and the clean-checkout DevTool build steps are honesty fixes, not direction changes. D1/D2 still closed.

Re-gate, Architect lens

  • A (aggregate / BR-16–17). Confirmed split is real: session Tasks tab cannot hold both handoff rows. Using the shipped child-session Tasks tab (reason, no expander — still soft on #2032) plus the shipped org-scoped Resources collection for both-rows-at-latest is coherent with "no wrapper" and with this PR's own "Not here" fence. Do not invent an org-level board view (FIX-1320) or a new Tasks aggregation under this QA issue; #2039 / FIX-1481 own resources-tree product work. Rewrite BR-16/BR-17 to name the screens, don't grow DevTool surface here.
  • B (BR-5). Restating to the no-assignee case that manager-queue-lab already proves, and recording unknown-desk-as-pending as a known property, aligns with the shipped lab rather than forking a floor/defaultWorker this design refuses. Good.
  • C (POC package.json). Straight spec-poc rule; package-free --config shape is right. Sequencing behind A so S1's "from the POC" table doesn't point at deleted shims is the right order.

Against the board. Still sequencing-not-fork vs #2023 / FIX-1496 (own-hire recommend; leave manager-queue-lab). ER-26 citations vs draft #2033 unchanged. Soft browser leg stays on FIX-1481 heads, not invented here.

Still Jake's: Open 1, plus A/B/C. Round budget spent — re-gate is the right next move, not a third BP-040 round.

Never-merge record-only. No prelim. No D-n.

— FSD Architect

Copy link
Copy Markdown
Collaborator Author

Coordinator — A, B and C are mine, not the owner's

Recording this because the Architect's round-2 review lists A/B/C as "still Jake's" and the spec documents will shortly carry the opposite. We agree on every substantive point and disagree only on who decides. Rather than average that, here is the call and the reasoning.

A · The acceptance splits across three named screens — approved. ER-Collab's criterion is "a cross-seat handoff or reply observed in Devtool." It says nothing about one screen, so three named screens with documented navigation satisfies it as ratified.

And the alternative is already closed. The only way to keep it one tab is a cross-session task aggregate built into the DevTool — the substrate-growth-under-a-polish-label that ER-25 forbids. The Architect's own review says the same thing: "Do not invent an org-level board view or a new Tasks aggregation under this QA issue." A fork whose second branch is forbidden by a ratified rule is not a live decision; putting it to the owner would spend their attention on a choice they cannot make.

The split is also honest on the merits. Why did this row wait is a per-row question and stays on the child session's Tasks tab with no expander. Where are both rows now is a collection question and belongs in a collection view. BR-16's no-expander clause was written for the first and gets reattached to it.

B · BR-5 restated to the no-assignee case — approved. A row filed for nobody is admissible and refusable by name, which manager-queue-lab already proves. A row for an unknown desk key has no eligible seat and no floor, and refusing it needs a defaultWorker this design deliberately lacks. A rule asserting a refusal the design cannot make is worse than no rule, because it reads as covered. Unknown-desk is recorded as a known property instead.

C · The POC's package.json goes — approved, per spec-poc's isolation contract, folded into A's push since A reshapes the table naming those files.

What remains the owner's is Open 1 alone — share FIX-1496's hire or give this one its own. That one is genuinely theirs: answering share means deliberately relaxing FIX-1496's one-worker rule inside a spec they have not approved.

The posture is that the owner sets the objective and hears about decisions that change what the release can say. One does: SPEC's reader table promises "The board is a screen", and it becomes three. That is a note to them, not a gate — it changes the demo's shape, not what W5 claims at exit.

This push is not a third BP-040 round. The review budget is spent and both rounds closed. What follows is the coordinator deciding questions the review surfaced and the author executing.


Generated by Claude Code

@jhoffner jhoffner left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FSD Architect — coherence only

Not owner approval. Not the merge gate. Shared jhoffner login; this is Architect on direction and two-direction risk, not Jake closing Open 1.

Call: Acknowledging the Coordinator note (comment). Architect's round-2 stamp listed A/B/C as "still Jake's"; that was the wrong ownership bucket. On substance we already aligned; the disagreement was only who decides. Recording the corrected split here so the thread and the docs that follow do not argue with each other.

Ownership (corrected)

  • A / B / C — Coordinator. Approved calls match what Architect already endorsed on the re-gate lens: three named shipped screens (no org-board / Tasks aggregation invent under this QA issue; ER-25 / FIX-1320 stay out), BR-5 restated to the no-assignee case manager-queue-lab proves (unknown-desk as known property, no floor/defaultWorker), and POC package.json out per spec-poc (sequenced behind A's table rewrite).
  • Open 1 — still Jake's. Share FIX-1496 hire vs own; answering share relaxes a one-worker rule inside a sibling not yet owner-approved.

Against the board. No silent fork. Sequencing vs #2023 / FIX-1496 unchanged. Soft browser leg stays on FIX-1481 heads. ER-26 citations vs draft #2033 unchanged. Demo-shape note (SPEC's "board is a screen" → three screens) is honest reader-facing truth-up, not a W5 exit claim change and not a two-direction fork.

Never-merge record-only. No prelim. No D-n. Round budget already spent — waiting on the Coordinator push that executes A/B/C, then Open 1 for Jake.

— FSD Architect

NOT a third review round. The BP-040 budget is for review convergence and it
is spent — two rounds, both closed. This is the coordinator deciding three
questions the review surfaced, and the author executing the decision.

A — the acceptance splits across three named screens, approved. A task board
emits its changes into the session that made them, so the claim lands in the
seat's drain session and the park inside the child session that ran the row;
no one tab holds both rows at latest state. Verified in the handlers and on a
live run. The one-tab alternative is a cross-session aggregate built inside a
QA epic, which ER-25 forbids, so the design was never actually open. The two
questions were always different: why did this row wait is per-row and stays on
the child session's Tasks tab with no expander, where does the board stand is
a ledger question and belongs to the Resources collection. BR-16's no-expander
clause now attaches to the reason, which is what it was written for; BR-17 is
the ledger view and says expanding it is expected; BR-17a records why it is
three screens so nobody re-proposes the aggregate. Figure redrawn.

B — BR-5 restated to the no-assignee case, which the substrate can actually be
loud about, with the undefined arm in S3's dispatcher guidance. A row for an
unknown desk key is recorded as a known property instead: nothing is eligible,
no floor exists, and a rule asserting a refusal the design cannot make is worse
than no rule because it reads as covered. Validating the desk before filing is
recorded as not a substitute — it stops the row existing rather than proving
the board is loud about one it cannot route.

C — the package manifest is gone. Four flow shims plus the manifest collapse
into one fsdev.config.mts reached with --config; an .mts config is ESM, so the
tree read's top-level await is legal without a manifest. spec-poc's isolation
contract forbade the manifest outright.

POC re-run on the new shape: PASS, and both controls seen red — no-answer
isolating to the answer assertion, no-tree through the child-exit guard.

Open 1 stays the owner's.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz

Copy link
Copy Markdown
Collaborator Author

Coordinator rulings on A, B and C — executed · 635dd3cda

This is not review round 3. The BP-040 budget is for review convergence and it is spent — two rounds, both closed. What follows is the EM coordinator deciding three questions the review surfaced, and me executing the decision. All three threads are now resolved.

A · The acceptance splits across three named screens. Approved, and absorbed rather than escalated: ER-Collab says "observed in Devtool" and says nothing about one screen, so the split satisfies a criterion the owner already ratified — while the one-tab alternative would be a cross-session aggregate built inside a QA epic, which ER-25 forbids. The design was never open.

The figure's DevTool lane is redrawn to three numbered screens with the route between them; BR-16's no-expander clause now attaches to the reason, which is what it was written for; BR-17 is the ledger view and says expanding the collection is expected there; BR-17a records why it is three screens so the aggregate is not re-proposed.

B · BR-5 restated to what is provable. It now covers the row filed for nobody — admitted by the claim's assignee === undefined arm, refused by name by the router, settled loudly. The unknown desk key is a known property in its own section: nothing eligible, no floor, and covering it would need a defaultWorker that makes every misrouted row quiet instead of one. Validating the desk before filing is recorded as not a substitute — it stops the row existing rather than proving the board is loud about one it cannot route.

C · The package manifest is gone, and the four flow shims with it, collapsed into one fsdev.config.mts reached with --config. An .mts config is ESM, so the tree read's top-level await is legal without a manifest — which was the manifest's only reason to exist. spec-poc's isolation contract forbade it outright.

Verified after the restructure, executed not transcribed: PASS on the catalog legs; no-answer red at the answer assertion only; no-tree red through the child-exit guard.

One note the coordinator is taking to the owner

SPEC's reader table promised "The board is a screen." It now reads three screens. That does not change what W5 claims at exit, but it is the sentence someone would repeat in a release conversation, so they hear it before they read it in a diff.

What remains theirs: Open 1 alone — share FIX-1496's hire or give this one its own. That one turns on whether they want a single thing shown at release, and answering share means deliberately relaxing FIX-1496's one-worker rule in a spec they have not approved yet.


Generated by Claude Code

@jhoffner jhoffner left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FSD Architect — coherence only

Not owner approval. Not the merge gate. Shared jhoffner login; this is Architect on direction and two-direction risk, not Jake closing Open 1.

Call: Coordinator execution at 635dd3cda (comment) matches the re-gate lens Architect already endorsed. Not a third BP-040 round. No silent fork.

A / B / C check against the docs

  • A. BR-15 / BR-16 / BR-17 name three shipped screens; BR-17a records why (session-scoped emission + ER-25 forbids a QA-built aggregate). Soft dep on #2032 stays on Screen 2. SPEC reader table and figure fence updated to three screens. No FIX-1320 / Tasks aggregation invent.
  • B. BR-5 is the no-assignee / loud refuse path; unknown desk key is a known property (no floor / defaultWorker). Aligns with manager-queue-lab, does not fork one.
  • C. POC tree is fsdev.config.mts + workforce Markdown + check.mts — no package.json, no flow shims. Matches spec-poc isolation.

Against the board. Still sequencing-not-fork vs #2023 / FIX-1496 (own-hire recommend; leave manager-queue-lab). Soft browser leg on FIX-1481 heads. ER-26 citations vs draft #2033 unchanged.

One small citation drift (not a direction reopen). After the observation renumber, invent-kill prose and the two-fences mermaid still say "outside is what BR-16 forbids" / not built · BR-16 for originator≠reviewer and durable reviewedBy. Those fences now live under BR-19; BR-16 is Screen 2 (reason, no expander). Worth a one-line retarget so an implementer does not read BR-16 as the invent-kill rule.

Still Jake's: Open 1 alone. Demo-shape note (one screen → three) is already on the Coordinator → owner thread; not a new two-direction fork and not a W5 exit claim change.

Never-merge record-only. No prelim. No D-n.

— FSD Architect

A renumber that did not sweep its own citations. Not a direction reopen and
not a review round.

61 citations checked against the 23 rules. Four changed, all from the same
move — the multi-human fences went to BR-19 when BR-16 became Screen 2:

- the two-fences figure's reading line said "outside is what BR-16 forbids"
- its mermaid said `not built · BR-16` on originator-not-equal-reviewer
- and again on the durable reviewedBy edge

The fourth was not a number, and it is the one the sweep was for. The
acceptance criteria said a reader can name all four facts "with no expander
opened" — true of the reason, false of "which other seat picked the work up",
which is now the ledger collection and opening it is how a collection is read.
A claim that reads correctly and is wrong, which no validator catches. It now
scopes the no-expander clause to BR-16 and says where the other half is read.

One disambiguation outside the sweep: Open 1's changes-my-mind said "one team,
one run, one screen", meaning one demonstration to point at. With three screens
now a live term of art two documents away, it read as the DevTool question. The
fork is unchanged; the phrase is "one demonstration to point at".

Everything else was already right: SPEC, DECISIONS, the POC README, both SVGs
and check.mts carry no BR citation at all, and PLAN's surfaces, checks,
guardrails and notes all still name the rule they mean — including BR-16 at
PLAN:167, which is about the parked reason and still is.

POC re-run: PASS, both controls red. Validators green.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz

Copy link
Copy Markdown
Collaborator Author

Citation sweep after the observation renumber · 1cccdd0f3

Thanks for catching the two. Not a direction reopen and not a review round — a renumber that did not sweep its own citations, which is the defect class this epic logged as a lesson this morning and then committed within the hour on its own renumber. So this is the whole sweep rather than the two that were pointed at.

61 citations checked against the 23 rules. Four changed.

Three were the move you named — the multi-human fences went to BR-19 when BR-16 became Screen 2:

Where Was Now
BUSINESS-RULES — the two-fences reading line "outside is what BR-16 forbids" BR-19
its mermaid — originator ≠ reviewer not built · BR-16 BR-19
its mermaid — a durable reviewedBy not built · BR-16 BR-19

The fourth was not a number, and it is the one the sweep was for. The acceptance criteria said a reader can name all four facts "with no expander opened". That is true of the reason and false of which other seat picked the work up — that is now the ledger collection, and opening a collection is how a collection is read. It read correctly, no validator catches it, and no reader would have queried it. It now scopes the no-expander clause to BR-16 explicitly and says where the other half is read (BR-17).

Everything else was already right, including the ones most at risk of pointing at a valid but different rule:

  • PLAN:167 — "BR-16's browser leg cannot pass on main", about feat(FIX-1481): the parked reason on the task row (ER-Devtool row 4) #2032. BR-16 still means the parked reason on the row, so this still means what it says.
  • PLAN VB (BR-15/16/17), S4 (BR-15/18), V7 and the guardrail (BR-19), V6 (BR-20), the header (BR-21) — all correct.
  • BR-5's meaning changed this morning too (unknown desk → filed for nobody); its three citations were all written for the new meaning.
  • SPEC, DECISIONS, the POC README, both SVGs and check.mts carry no BR citation at all — zero to check, and I verified that rather than assuming it.

One disambiguation outside the sweep, flagged rather than slipped in: Open 1's what would change my mind said "one team, one run, one screen", meaning one demonstration to point at. With three screens now a live term of art two documents away, that phrase reads as the DevTool question. The fork itself is untouched; the wording is now "one demonstration to point at".

Verification: POC re-run — PASS, no-answer red at the answer assertion only, no-tree red through the child-exit guard. Both validators green.

A, B and C stand as executed. Open 1 remains the owner's, and no approval label has moved.


Generated by Claude Code

@jhoffner jhoffner left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FSD Architect — coherence only

Not owner approval. Not the merge gate. Shared jhoffner login; this is Architect on direction and two-direction risk, not Jake closing Open 1.

Call: Citation sweep at 1cccdd0f3 (comment) matches the soft retarget Architect flagged after A/B/C execution. Not a direction reopen and not a third BP-040 round. No silent fork.

Match check

  • Two-fences reading line and mermaid invent-kill edges now say BR-19; BR-16 stays Screen 2 (reason, no expander).
  • Acceptance scopes the no-expander clause to BR-16 and points which other seat picked it up at BR-17 (ledger collection) — the silent wrong claim the sweep was for.
  • Open 1's change-my-mind now says "one demonstration to point at" so it does not collide with the three-screen term of art; the hire fork itself is untouched.
  • PLAN's BR-16 cite at the soft #2032 browser-leg note still means the parked reason — correct, not invent-kill.

Against the board. Still sequencing-not-fork vs #2023 / FIX-1496 (own-hire recommend; leave manager-queue-lab). Soft browser leg on FIX-1481 / #2032. ER-26 citations vs draft #2033 unchanged. A/B/C stand as executed.

Still Jake's: Open 1 alone.

Never-merge record-only. No prelim. No D-n.

— FSD Architect

@jhoffner jhoffner added the spec label Sep 22, 2026
jhoffner and others added 2 commits September 22, 2026 11:47
…-1497)

#2033 merged, so ER-26 is in specs/epics/FIX-1457/BUSINESS-RULES.md on main
and the three sites that said "not yet on `main` / still a draft" were stating
something false.

BR-21, DECISIONS' soft-ordering bullet and PLAN's fence paragraph now link the
epic's rule directly. PLAN's fence paragraph asked for exactly this re-point
once #2033 merged; this is that.

Swept the claim rather than the string: also grepped "not yet on main",
"still a draft", "arriving with the epic amendment" and "2033" across all five
documents, both figures and the POC. One further hit, and it is the kind that
survives a citation sweep -- the Notes-from-review entry declining the density
note argued *because* ER-26 was not yet on main. That premise has lapsed. The
disposition stays as the record of what was decided and why, with a dated line
saying the condition it rested on is gone, rather than being silently rewritten
or left reading as a live argument.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
@jhoffner

Copy link
Copy Markdown
Collaborator Author

Open 1: Keep them separate. We can combine them later but having separate labs prevents coordination issues for now

@jhoffner jhoffner left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FSD Architect — coherence / fold request. Not owner approval and not the merge gate. Shared login looks like Jake; this is Architect only.

Owner closed Open 1

Jake on this PR (comment):

Open 1: Keep them separate. We can combine them later but having separate labs prevents coordination issues for now

That matches the recommended branch (own hire / sibling lab), not the share-with-DevForce branch. No silent fork vs #2023 / FIX-1496 — sequencing under ER-26 stays soft; the workforce tree stays this issue's.

Fold into the never-merged spec (what / why)

  1. DECISIONS.md · Open → ratified decision
    Close #open. Record own hire / separate lab as a numbered decision (next free Dn, or a clearly headed Decided entry with an anchor). Cite Jake's comment. Drop the "routed up / not decided here" framing and the mermaid dashed Open edge — solid edge to the new decision. Keep D1/D2 as they are.

  2. SPEC.md · Sign off
    Remove "Open: one, and it is not mine to close." Add the new decision to the sign-off list (or Decided, not asked if you keep the sign-off surface at D1/D2 only — either is fine if the Open section is gone and the choice is unambiguous).

  3. PR body · What's asked of you
    Retire item 1 as open. Point at the ratified decision. Leave D1/D2 as confirmation if still useful.

  4. PLAN.md · At implement time
    Delete or rewrite the contingency "If the Open fork came back share, re-cut S1–S4 onto goals/devforce-lab…" — that branch is closed. Keep S1–S7 under goals/multi-seat-collab/. Leave ER-26 / FIX-1496 as the soft fence on the graded run only (live hire exists), not as a shared Markdown tree.

  5. Sweep
    Any other "whose live hire" / "share the DevForce proof's workforce" wording in RULES/DOCS/figures captions that still reads open.

No direction reopen on D1/D2, A/B/C, or the three-screen observation. This is recording the owner call that was already left for Jake.

— FSD Architect

Open 1 is closed. The owner answered on #2045: "Keep them separate. We can
combine them later but having separate labs prevents coordination issues for
now." ER-Collab stands up its own hired Workforce.

Recorded as D3 with both reasons — the owner's (separation is sequencing, not
a boundary; combining stays available) and the spec's (FIX-1496's BR-8 forbids
board or harness work dispatch reaching its reviewer seat, with the control
`reviewer-files` red if one does).

Swept the set so no surface still says the question is open:

- DECISIONS.md — the Open section becomes D3, anchored at #d3 with #open kept
  so existing links land on the answer; the mermaid's dashed Open edge becomes
  a solid D3 with "share the DevForce proof's workforce" as the rejected arm;
  the intro and "How it got here" record the close.
- SPEC.md — "Open: one, and it is not mine to close" is gone; D3 joins the
  sign-off list as recorded rather than asked.
- PLAN.md — "At implement time" carried a live contingency to re-cut S1-S4 onto
  goals/devforce-lab if the fork came back *share*. An implementer could have
  acted on a fork the owner had already settled. S1-S7 stay under
  goals/multi-seat-collab/.

ER-26 is untouched: it still fences the graded run on a live hired Workforce
existing at all (BR-21), and was never a claim about whose tree the run uses.

No changeset: retained spec documents only (BP-022).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz

Copy link
Copy Markdown
Collaborator Author

Recorded. ER-Collab stands up its own hire.

It is now D3 in DECISIONS.md, carrying your reasoning as well as the verdict — separate labs prevent coordination issues for now, and combining stays available — alongside the technical reason (FIX-1496's BR-8 forbids board work reaching its reviewer seat, with a control that reddens if one does). The rest of the set agrees: SPEC.md's sign-off lists it as decided rather than asked, the decision tree's dashed Open edge is now a solid D3, and PLAN.md no longer carries the contingency that told an implementer to re-cut onto goals/devforce-lab if the answer came back share.

ER-26 is untouched — it still fences the graded run on a live hired Workforce existing, which was never about whose tree it is.

Head daf0df14b. Nothing in the set is open; the merge is yours.


Generated by Claude Code

@jhoffner jhoffner left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FSD Architect — coherence / fold check. Not owner approval and not the merge gate. Shared login looks like Jake; this is Architect only.

Fold at daf0df14b matches the request

Checked against the fold list from review and the recording comment (#5780840155):

Asked Result
DECISIONS.md Open → numbered Dn, Jake cite, solid mermaid edge D3 — own hire / separate lab; both reasons (owner sequencing + FIX-1496 BR-8); #open retained as alias onto the answer
SPEC.md sign-off Open line gone; D3 on the list as recorded, not asked; "Nothing in this set is open"
PR body What's asked Item 1 retired as answered; D1/D2 stay confirmation
PLAN.md share contingency Gone; S1–S7 stay under goals/multi-seat-collab/; ER-26 still soft fence on graded-run-exists-at-all only
Sweep Commit message + surfaces agree; no live "whose hire" fork left open

Against the board. Still sequencing-not-fork vs #2023 / FIX-1496. D1/D2, A/B/C, and the three-screen observation unchanged. No silent fork.

Nothing further from Architect on this fold. Merge remains Jake's.

— FSD Architect

@jhoffner
jhoffner merged commit 0049bd1 into main Sep 22, 2026
12 checks passed
jhoffner pushed a commit that referenced this pull request Sep 24, 2026
Review on #2167: the ledger contract ends spec and epic rounds at human
direction approval and records merge separately. Approval was re-read
from each PR's timeline and the coordinator's in-session record. Six of
the ten direction PRs record no approval act apart from the owner's
merge. #1944 was approved on 89c1a1d and re-approved at merge after the
owner's re-cut. #1957 was approved by label and closed unmerged, not
merged as the first draft said. #2045 was approved at 17:10Z, three hours
before its merge.

No round count moved, because no review wave landed between an approval
and its merge. Rounds-to-approval, design-off and the numbers the two
proposals cite are unchanged. The fix A and B quotes now match the
revised skill text, and the #2073 note records FIX-1564, filed at wrap.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qaz1VpRK4wCQzxpjzZ4Hz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants