Repository navigation
Release 0.32.0: cross-workspace chats, Markdown drafts and safer setup - #1205
Conversation
Keep each endpoint location frozen for admission, results and source previews. Preserve independent ownership and narrow adoption/resume controls. Add action-path, legacy-binding and rendered provenance regression coverage. Authored candidate only: static checks passed; runtime/build/installed qualification remains unrun pending owned managed placement.
…aces Preserve cycle1's 812 passes and four failed fixture/error-text expectations; correct unchanged selection across cold restart and refusal wording. Add second complete scripted round trip, authenticated retained download and Canvas open, exact acknowledgement and owner-account guard. New checks unrun pending changed-source qualification.
Import only exact generated output from passed source qualification fc5e6b8; all311file hashes independently match exported static archive. Build ded5697c9c0e6353. No host build; installed-package qualification follows this exact candidate.
… expansion Coordination CI40448131446 retained1151passes/1fail/1skip/2subtests. Its workspace negative still expected newly supported cross-workspace send to fail. Exercise unchanged default-scoped history denial instead, preserving transport/browser context and no-effect assertions. Product/static bytes unchanged from installed-qualified a3c280a.
Retain secondCI40449080848 failure. Canonical slug and native metadata prevent real discovery from correctly rejecting the old unresolved fixture. Force real discovery between both full exchanges; retain every existing receipt/artifact/authority assertion. Test-only correction, product and static unchanged.
…ssets to canonical build
|
Salil Das (@sadlilas) — requesting the normal independent approval required by the repository for this user-authorized four-PR release. This combines #1196, #1197, #1202 and #1204, with a cross-workspace scope notice and no live adoption. The 69-path source union is exact; bounded independent source reviews and combined package qualification are underway. Final generated assets will update this head; please review/approve the final qualified head rather than this stale-assets checkpoint. Recommendation: one 0.32.0 batch for the new cross-workspace/editor capabilities plus bounded update/setup fixes. No ruleset or approval bypass will be used. |
|
Salil Das (@sadlilas) — final source/assets are now d840d26, independently source/assembly/static-clear, with required Fast40489183547 SUCCESS. The PR is ready for ordinary review; the affected installed-package check is still pending and will be posted before merge. Please review this exact source and both release notices. No admin bypass is planned or authorized for this batch. |
|
Updated release-owner authorization: the user now explicitly says we do not need to wait for Salil and may admin-merge once satisfied, then publish. This supersedes the earlier formal-approval wait for this release. I will bypass only the remaining formal approval after substantive reviews, affected combined-package qualification and required Fast succeed. I will not fabricate an approving review, change rules/protections, waive a product failure, alter published bytes or perform live adoption. Final d840 Fast is green; local installed-package qualification is still pending. |
|
Qualification update: the frozen 0.32.0 wheel is 24f0b5af983a04ce6382019fb3f6b919266233965ea3c807e9e7068e696a82c6. Independent raw-evidence audit verifies two matching311-file builds,766 source cases,337 installed update/cross-workspace cases,8 checkpoint cases,8 isolation checks and exact production PROBE. Initial installed setup had21passes and2PythonPlaywright driver-start failures before rendering; all5browser journeys were unrun. That initial outcome stays FAILED. A diagnostic-only second execution stopped at a strict prepared-dependency inventory mismatch before installing or probing. Its harness asserted before saving the differing paths, so the cause remains unknown; no product assertion has been weakened. Both owned guests are removed and both failed records retained. The release owner has explicitly revised the same qualifier limit from2to3 for one final evidence-capture repair and the unfinished acceptance only—not a reset or new owner. It will retain exact dependency differences before validation, reject unexplained payload drift, establish fresh installed driver readiness, then run only outstanding setup/browser checks. No rebuild or replay of completed suites. Publication remains blocked on these actual results, not on Salil approval under the updated user authorization. |
|
Release-owner acceptance for exact head d840d26 / tree d10c29ac277ee5c6d2a628807710c5d39e4d303a. Independent source reviews cleared all four accepted candidates; assembly review verified the exact 69-file author union, four metadata files, authored 0.32.0 notes/notices, and all 311 combined static assets. Final Fast 40489183547 passed committed parity; current checks are 14 successful and one explicit default-installed plan skip. No unresolved review threads. Affected qualification is accepted: 766 distinct source Python cases, 337 installed update/cross-workspace cases, 23 installed setup cases across the preserved attempts, eight editor checkpoint cases, eight isolation checks and the exact production PROBE; two identical canonical builds; five whole installed journeys (peer-preview, markdown-composer, multi-quote, compact-composer, draft-reload). Source and installed selections overlap; these are not additive unique coverage. The fresh wheel SHA-256 is 24f0b5af983a04ce6382019fb3f6b919266233965ea3c807e9e7068e696a82c6 (9,803,118 bytes), with all 825 payload files and 311 served assets bound. Independent retained-evidence audits cleared completed phases and the final suffix. Owned guests/preparations were removed with retained receipts. Both earlier qualification failures remain FAILED. The initial Python Playwright driver-start failure remains unexplained; two fresh normal startup probes passed without an identified repair. The second attempt stopped before browser effects because its comparison failed before saving the diff. The explicitly authorized third and final execution saved that diff: exactly six installer metadata/RECORD files differed, all other 2,989 dependency hashes matched, and current RECORDs were validated. Old raw metadata values remain UNKNOWN; no full-environment byte-identity claim. No assertions were relaxed, no fourth execution, and completed phases were not replayed. Scoped screenshot review found no blocking visible defect in reviewed peer, Markdown and quote surfaces; it is not physical-device or universal visual acceptance. Historical Thinkstation live remediation and Edge trust remain unverified. No live adoption is included. Administrative merge is explicitly authorized by the user after substantive satisfaction. Only the remaining formal independent GitHub approval requirement is bypassed; no approving review is fabricated, required checks are not waived, and protections are unchanged. Publication and the downloadable package remain to be verified. Post-release broad checks stay separate. |
Published: v0.32.0
Published October 27, 2026 at 04:19:29 PDT: https://github.com/microsoft/amplifier-unified/releases/tag/v0.32.0
The user explicitly authorized administrative merge after substantive acceptance. PR1205 was squash-merged at 04:17:12 PDT; only the remaining formal independent GitHub approval requirement was bypassed. No approval was fabricated, no required check waived, and no ruleset changed. Audit: #1205 (comment)
Included accepted candidates
All four source PRs are closed as shipped through this release, not merged again. Original author evidence and ownership remain preserved.
Verified identities and publication
Review and affected qualification
Independent source/assembly reviews verified all69 author files as an exact disjoint union, four metadata changes, accurate notes with two notices, and all290 historical entries preserved. FinalFast40489183547 passed committed-asset parity; fourteen checks succeeded, one default-installed plan skip was explicit, and no review threads remained.
Accepted evidence includes766 distinct source Python cases,337 installed update/cross-workspace cases,23 installed setup cases across retained attempts,8 real editor checkpoint cases,8 isolation cases, exact production PROBE, two identical canonical builds, and five complete installed browser journeys: peer-preview, markdown-composer, multi-quote, compact-composer, draft-reload. Overlapping source/installed selections are not additive unique coverage. All311 HTTP assets and actual fixture-process installed origins were verified.
Both earlier failed qualification executions remain FAILED. The original driver-start failure remains unexplained; two fresh normal startup probes passed without an identified repair. The second execution stopped before browser effects when a harness comparison failed before saving the diff. The explicitly bounded third/final execution found exactly six installer metadata/RECORD differences; all other2,989 dependency hashes matched and current RECORDs were validated. Old raw metadata values remain UNKNOWN. No full-environment byte-identity claim, fourth attempt, product-assertion waiver or completed-phase replay. All owned guests/preparations were removed with evidence retained.
Scoped pixel review covers selected peer, Markdown, quote and setup surfaces, not all35 screenshots or physical devices. Prior visual-receipt overclaims are retained with their correction.
Limits and follow-up
Broad post-release verification40495284762 attempt1 FAILED at05:20:23PDT Oct27: Python14673pass/10fail/99skip (+6subtests), browser122pass/4fail/0UNRUN of126, and readiness stopped at chat-scroll177. Publisher, installed-package and six integration lanes passed separately. The finite monitor is complete and archived. Verified evidence and bounded existing-owner handbacks are recorded at #1206 (comment); corrective-owner acknowledgments remain pending. No rerun or live change was started. Historical failures/UNKNOWNs remain retained. No live installation, service restart, certificate-store change or Thinkstation retry occurred. Historical Thinkstation commit pair/live remediation and separate Edge certificate warning remain unverified. Rich GFM is not exhaustive GitHub parity. New source support was not used to bypass the currently installed messaging guard.