Repository navigation
chore: reconcile open PRs and implementation issue status #607
Description
Decision
R1 — DEC-ROLEWEAVE-607-001 — 2026-10-18T09:10:16.7534667Z.
The product owner requested a review of all open RoleWeave pull requests and issues, authorized justified closures and eligible merges, and confirmed a single-responsibility boundary: general execution/review in RoleWeave; reusable business cases in workbench-examples; enterprise facts, ontology and evidence in Enterprise Context. This is a maintenance inventory, not permission to bypass CI, independent review or branch protection.
Acceptance
- AC-001: inspect all 12 open pull requests against main 471beb3 and their review records; retain a decision and evidence link for each.
- AC-002: retire absorbed or unsuitable implementation branches without losing the underlying unmet requirement; do not classify incomplete behavior as delivered.
- AC-003: inspect all open issue records, close only evidence-backed completed outcomes and preserve remaining dependencies or product acceptance gates.
- AC-004: prepare the generic bounded repair improvement in feat(goals): carry human rejection into bounded task repairs #606 and merge only after required checks and independent exact-head approval. Do not add pilot business code to RoleWeave or modify unrelated local work.
Pull request decisions
| PR | Decision | Evidence / remaining work |
|---|---|---|
| #563 | Close as absorbed | Main already pins Vitest 4.1.11 and includes the same source-map/toolchain regression through #564. Current root install audits clean; focused regressions pass 2/2. Manifest differences from the old head are newer version metadata and dayjs, not missing repair. |
| #505 | Close as absorbed | Knowledge lifecycle code is on main through #523; #564 adds expectedVersion writes. Focused server/IPC regressions pass 24/24. Keep lifecycle/i18n requirements separately audited in #347. |
| #560 | Retire draft implementation; retain #558 | The draft has acknowledged destructive Markdown round trips, language-dependent source paths, no durable acceptance authority and no real bridge validation. Main #559/#564 already own acceptance. Future document authoring must integrate existing goal/acceptance state instead of adding a parallel Space acceptance store. |
| #524 | Retire outdated first-run implementation; retain #519/#395 | No current deployment identity contract is accepted. The reviewed branch still has blocking findings and conflicts with current empty first-launch behavior. Preserve the product request; a future implementation must use a real deployment identity and current shell. |
| #536 | Retain, blocked | Fixture-only marketplace preview; existing review identifies a partial PATCH regression, fork/check limitation and conflict with current main. Not a working marketplace or hiring integration. #535/#544 remain open. |
| #507 | Retain draft | Send-time advisory has unresolved review findings, conflicts and no authority to replace human approval. |
| #506 | Retain, needs integration | Independently reviewed aging advice is useful but conflicts with current approval surfaces; any updated SHA needs new review and CI. |
| #504 | Retain, needs integration | Ready-host advice is optional; reconcile current Agent connection/experimental settings without changing bindings or permissions. |
| #502 | Retain, needs integration | Processing receipts remain a useful separate outcome; reconcile current reports and preserve no-auto-resolve semantics. |
| #493 | Retain approved design | Design-only negotiation channel, not implemented runtime. Reconcile docs with existing group/relay/goal contracts before a replacement revision. #452 remains open. |
| #492 | Retain, needs integration | Dismissal advice cannot itself authorize reassignment; reconcile current org controls, then obtain exact-head review. |
| #491 | Retain, blocked | Current review requests changes; old macOS session-race failure and fork/check limitations must be revalidated against current main. |
Issue audit
#347 and #511 are CLOSED as completed: current main has safe knowledge lifecycle, localization, inline source/live/reading editor, serialized autosave, version conflicts, retained drafts and link navigation. Fresh regression checks passed, ACCEPT and requirement-decision:v1 records were posted, and the original requirements remain in the accepted issue bodies.
Retain #110: its scope includes Intel Mac, signing, installation/update and external-memory acceptance beyond the shipped unsigned arm64/Windows release. #136 and #604 remain separate signing/publication gates.
Retain #485: its own product decision explicitly requires a real compatible-provider receipt; loopback coverage and merged #488 do not satisfy entitlement/product acceptance.
Retain #333/#363/#516: current project boards and progress do not establish all requested graph, Gantt, group binding or host-step/reconnect acceptance. #333 records React Flow as the chosen graph direction; do not create a second graph model in this cleanup.
Retain #36/#328 and the memory family #327/#348-#356: existing file browsing, notes and bounded context do not establish all enterprise asset, durable-memory, knowledge-review or ontology-runtime requirements. Cross-repository responsibilities must be clarified without implementing a second enterprise data service inside RoleWeave.
Retain #68: the source still intentionally dual-writes groupRef. Retain the remaining proposal/feature records until their individual acceptance or explicit retirement decisions exist. A checked implementation count is not customer acceptance.
Validation and limits
Read-only inventory captured outside the repository, including all issue bodies and PR reviews. Existing main verify/security/scorecard workflows are successful at 471beb3. Fresh targeted documentation/toolchain checks: 26 passed (16 docs server, 8 docs IPC, 2 toolchain). New repair/acceptance checks: 17 passed. Full local gate and #606 CI results will be appended. No customer data or credentials are used.
Revision history
- R1: owner-authorized review inventory and evidence-backed disposition; follow-up results are appended before completion.
Historical October 18 CI and merge handoff
Historical checkpoint: PR #608 was at 1a4702f; see the October 21 receipt for the current head and gates. All 11 executed checks passed, including both complete Node 24 jobs, CodeQL, dependency review, scorecard, both staging smokes, both native installers and layout parity.
- Verify: https://github.com/bytefolk/roleweave/actions/runs/39114619446
- Security: https://github.com/bytefolk/roleweave/actions/runs/39114619319
- Scorecard: https://github.com/bytefolk/roleweave/actions/runs/39114619323
No independent approval is recorded. Bindy-lbb and sun-970 have been requested through the standard review mechanism. GitHub reports REVIEW_REQUIRED; auto-merge is disabled. Author self-approval or administrator bypass would violate the inherited contribution/engineering policy, so no merge was attempted without the required review. After an eligible reviewer approves this exact head, re-read the head/base/checks and squash-merge using --match-head-commit. Do not publish a desktop release as part of this change.
Maintenance disposition: four original PRs closed (#563/#505 absorbed; #560/#524 retired implementations with requirements retained), two completed implementation issues closed (#347/#511), eight original PRs and 39 original issues retained with reasons in #607. Current totals are 9 open PRs and 41 open issues, including new #606/#607/#608. #606 and #607 remain open because the merge gate is outstanding.
Responsibilities remain: general execution/review in RoleWeave; reusable business implementations in workbench-examples; enterprise facts, ontology and evidence in Enterprise Context. The first real factory pilot remains receivables reconciliation and customer follow-up with human confirmation; no customer data, financial writes or automatic messages were introduced here.
Earlier follow-up — 2026-10-21
#616 merged with independent review at main 7373da8; #615 accepted. #608 current head fc12e8d passes its complete local gate (3054 pass, 0 fail, 3 existing conditional skips, audit 0), with hosted checks and independent review pending. #614 author updated to ecd4c81; fresh validation is recorded in its review. Current inventory: 7 open PRs, 42 open issues. See appended follow-up receipt for remaining PR dispositions and existing requirements. Historical counts and CI above are retained for audit only.
Historical state after #614 — 2026-10-21
#614 merged at main 2dc7764; #613 accepted with its complete ledger. #608 current head d45cff4 has a fresh full local gate (3071 pass, 0 fail, 3 existing conditional skips, audit 0); new hosted CI and independent non-author review pending. Earlier head/count records are historical only. Current inventory: 6 open PRs, 41 open issues. Existing hourly follow-up remains active for #608; other PR/issue disposition and single-responsibility boundaries are unchanged.
Historical state after #506 — 2026-10-21
Main advanced to 8930e45 through independently approved #506. #608 current head 85a6d24 has a fresh install/full local gate (3082 pass, 0 fail, 3 existing conditional skips, audit0); new-head hosted checks and independent review pending. Current inventory 6 PRs/40 issues, including new #618 for existing #617; earlier counts/states are historical. See latest appended receipt for exact evidence and boundaries. #606/#607 remain open until the normal approved #608 merge and final ledger.
Historical state after #618 — 2026-10-21
Main c569aa8 includes approved #618. #608 current head d506942 has fresh install/full local check: 3097 pass, 0 fail, 3 existing conditional skips, audit0. Current-head hosted CI and independent review pending. #617 is closed; new #624/#623 are separate release inventory, with no release approval asserted here. Current counts: 6 PRs/40 issues. Historical head/count sections above are retained as audit history; latest appended receipt is authoritative for this follow-up.
Historical state after #620 / 0.6.0 baseline — 2026-10-21
Main33140136 includes task briefing/collaboration and release baseline. #608 current head cdf8998 preserves both main and repair, with a reproduced/fixed retry identity-order regression (before:200 instead of409; focused57/57PASS). Final full gate3131PASS/0FAIL/3existing skips/audit0. New-head hosted checks and non-author approval pending. Current inventory5PRs/39issues. Exact receipt and logs above; prior head/count sections are historical. #606/#607 remain open until normal approved #608 merge and final acceptance ledger.
Current merge gate after #626 / #628 — 2026-10-21
#608 current head: a4176fc. Base main: fe03db9. Approved main #626 composer changes and #628 atomic image-attachment pipeline were integrated with ordinary merges and fast-forward pushes; only #626's changelog conflicted, and both Unreleased sections were preserved. The shared execution diff remains the repair import plus post-retry binding guard; no new task/context/data store.
Complete local gate passed separately after each source update: #626 integration 3131 PASS; final #628 integration 3140 PASS, 0 FAIL, 3 existing conditional skips, audit 0 (scripts 233 / UI 53 / server 1013 / renderer 1270 / desktop 571). Final log: work/roleweave-maintenance-20261018/608-post628-check.log; previous log: 608-post626-check.log. Both commits were tested without changing source mid-run. Final diff check is clean.
New-head hosted CI and independent non-author approval remain pending. Earlier CI is historical only. Reviewer requests remain; no self-approval, protection change or administrator bypass. #606/#607 remain open and hourly follow-up remains active. Routine main synchronization does not by itself require a user notification. Older candidate/count/evidence sections above are retained as history, not current merge authorization.
Activity
PeterGuy326 commentedon Oct 18, 2026
Execution receipt — 2026-10-18
Current open counts include the two new tracking issues (#606/#607) and PR #608. Maintenance #607 remains open while its merge gate is outstanding. This record does not promise a real factory deployment or autonomous verification; those remain separate case/pilot acceptance.
PeterGuy326 commentedon Oct 18, 2026
Current-head CI and merge handoff
PR #608 is frozen at 1a4702f. All 11 executed checks passed, including both complete Node 24 jobs, CodeQL, dependency review, scorecard, both staging smokes, both native installers and layout parity.
No independent approval is recorded. Bindy-lbb and sun-970 have been requested through the standard review mechanism. GitHub reports REVIEW_REQUIRED; auto-merge is disabled. Author self-approval or administrator bypass would violate the inherited contribution/engineering policy, so no merge was attempted without the required review. After an eligible reviewer approves this exact head, re-read the head/base/checks and squash-merge using --match-head-commit. Do not publish a desktop release as part of this change.
Maintenance disposition: four original PRs closed (#563/#505 absorbed; #560/#524 retired implementations with requirements retained), two completed implementation issues closed (#347/#511), eight original PRs and 39 original issues retained with reasons in #607. Current totals are 9 open PRs and 41 open issues, including new #606/#607/#608. #606 and #607 remain open because the merge gate is outstanding.
Responsibilities remain: general execution/review in RoleWeave; reusable business implementations in workbench-examples; enterprise facts, ontology and evidence in Enterprise Context. The first real factory pilot remains receivables reconciliation and customer follow-up with human confirmation; no customer data, financial writes or automatic messages were introduced here.
PeterGuy326 commentedon Oct 19, 2026
Maintenance execution receipt — 2026-10-19
This supersedes the earlier current-head/count handoff without altering the original unmet requirements.
docs/design/memory-controls-v1.mdexplicitly says design proposal only/no runtime. Need Gate D0, MEM-1 and RW-1; permissioned pin/disable/inspect/forget, truthful failure and accessibility.memory-plane-v1.mdexplicitly says R1 design/no runtime. Latest audit states needs-design, no frozen acceptance packet or product acceptance; child/upstream split and Gate D0 remain necessary.@fullstack-ai-infra/ui@0.2.0. RoleWeave desktop/UI manifests, peer range, lockfile, imports and dedupe still use the old package identity. No approved/published new coordinate exists to consume.apply.tsstages mcp.json and policy grants. Latest decision keeps this as upstream runtime tracker, not duplicate UI work. Fresh DE#219 is open with actual-local MCP E3 still required.PeterGuy326 commentedon Oct 20, 2026
Follow-up receipt — 2026-10-21 (Asia/Shanghai)
Current main: 7373da8. Open inventory after #616 merge: 7 PRs and 42 issues.
This follow-up closes no unmet feature merely to lower issue counts. Existing product HOLD, upstream rollout, real-provider, signing and enterprise-context boundaries from the prior detailed audit still apply. #606/#607 remain open until the normal #608 merge and final acceptance ledger.
PeterGuy326 commentedon Oct 20, 2026
Follow-up after #614 merge — 2026-10-21 (Asia/Shanghai).
#614 was independently re-approved on ecd4c81 after all 11 hosted checks passed and squash-merged to main 2dc7764. Its completed branch was deleted only after verifying it still pointed to that reviewed head. #613 now has the ACCEPT, requirement-decision:v1 and accepted R1 body/history records; no reopening or expanded entitlement claim.
#608 is updated by a normal conflict-free main merge to d45cff4. Full final-source local gate rerun: 3071 passed, 0 failed, 3 existing conditional skips, audit 0 (scripts 233 / UI 53 / server 972 / renderer 1245 / desktop 568). Prior fc12e8d hosted checks all passed, but do not cover the new head. Current-head CI and non-author approval remain pending. Existing Bindy-lbb/sun-970 review requests and hourly follow-up are retained; no admin bypass or self-approval.
Current inventory: 6 open PRs, 41 open issues. Earlier remaining-PR dispositions are unchanged; no unmet requirement is closed as a side effect. #606/#607 remain open until #608 merges and its acceptance ledger is complete.
PeterGuy326 commentedon Oct 21, 2026
Follow-up after main advanced through #506 — 2026-10-21 (Asia/Shanghai).
#506 is MERGED at 8930e45. Exact reviewed head bb38788 had independent PeterGuy326 approval and 11 successful hosted checks. This supersedes the earlier conflict-blocked PR inventory. #466 is closed with a delivery note; broader #422 product acceptance remains separate, and this audit does not infer real-customer acceptance.
#608 was consequently behind main. Integrated main with an ordinary conflict-free merge and fast-forward push to 85a6d24. A fresh npm ci and entire npm run check on that source pass: 3082 passed, 0 failed, 3 existing conditional skips; audit 0. Components: scripts233/UI53/server981/renderer1247/desktop568. The Vite6.4.4 lockfile update comes from approved main. New-head hosted CI and independent non-author approval remain pending; all 11 old d45cff4 checks were green but are historical, not merge evidence for the new SHA.
Current inventory: 6 open PRs and 40 open issues. Newly opened #618 implements the already-recorded #617 relay slice; its appearance is inventory only, not an independent approval by this audit. Existing #502/#504 integration, #507 draft/review and #536 PATCH/fork-check requirements remain. #606/#607 remain open until #608 normal approved merge and final ledger. Hourly follow-up continues, without repeated unchanged-status comments or duplicate task/business stores.
PeterGuy326 commentedon Oct 21, 2026
Follow-up after #618 — 2026-10-21 (Asia/Shanghai).
Main advanced to c569aa8 via #618. Its exact head f0aff10 has independent PeterGuy326 approval and all 11 hosted checks successful; #617 is closed by that merge. This supersedes the previous pending-PR inventory, without implying customer acceptance or closing the separate negotiation/memory requirements.
#608 integrated that main by ordinary conflict-free merge and fast-forward push to d506942. Re-inspected the shared dispatch seam: group execution skips personal repair injection, while main's bounded relay handoff/history deduplication remains intact. No second task/context store or business-specific logic. Feature diff stays eight files / 355 insertions / one deletion against main.
Fresh npm ci and full final-source npm run check pass: 3097 passed, 0 failed, 3 existing conditional skips, audit 0 (scripts233/UI53/server991/renderer1251/desktop569). Build/type checks, renderer production build, updater preparation and diff check pass. Local logs are 608-post618-install.log and 608-post618-check.log in the existing external maintenance folder. New-head hosted CI and non-author approval remain pending. The previous 85a6d24 checks were all successful but are historical only.
Current inventory remains 6 open PRs and 40 issues because #624/#623 now track a separate 0.6.0 release. That is inventory, not release approval or publication authority from this maintenance run. The older #502/#504/#507/#536 dispositions remain unchanged. #606/#607 stay open pending approved #608 merge and final acceptance ledger. Hourly follow-up remains active.
PeterGuy326 commentedon Oct 21, 2026
Follow-up after #620 and the 0.6.0 baseline — 2026-10-21 (Asia/Shanghai).
Main advanced to 3314013 through task briefings/collaborators/dependencies (#620, squash b69b9d8) and the release baseline (#624). #620's current-head approval is recorded on d2d42b3; it is not a second implementation introduced by this cleanup. The current inventory is 5 open PRs and 39 open issues.
#608 merge initially conflicted in imports and runtime module inventory. Resolved by preserving the existing repair module and main's collaboration/briefing modules. A real semantic integration regression was then reproduced: an explicit retry can restore its project/task IDs from a saved briefing after a prematurely placed repair check. The new HTTP regression returned 200 instead of 409 before the fix. The existing repair guard now runs after the server-owned retry identity is restored, so another unreviewed attempt stops before a model call. No alternate retry/task/approval store was introduced.
Current #608 head: cdf8998, ordinary merge and fast-forward push. Focused repair/briefing/collaboration/relay/group suites 57/57 PASS. The complete final-source npm run check was restarted after final edits and committed merge: 3131 PASS, 0 FAIL, 3 existing conditional skips, audit 0; scripts233/UI53/server1011/renderer1264/desktop570. Logs are 608-post620-install.log,608-post620-regression-before.log,608-post620-focused.log and608-post620-final-check.log in the existing external maintenance folder. The interrupted earlier full run is not evidence.
Current-head hosted CI and independent non-author approval remain pending. No self-approval or bypass; Bindy-lbb/sun-970 requests retained. The feature remains Unreleased; the published 0.6.0 changelog is preserved. No desktop release was published by this maintenance run. The original #502/#504/#507/#536 dispositions and cross-repository responsibility boundaries remain. #606/#607 stay open pending normal approved #608 merge and final ledger; automatic follow-up is updated.