These are our own test observations. The labels distinguish application issues, bounded negative tests, local browser restrictions and testing-tool effects.
FMP-UNICODE-001 / Application reliability · Repaired
How a split Unicode character cleared visible results
A valid long source name could be cut through a Unicode character, breaking contact-link rendering. The repaired link keeps the listing and saved data usable.
The demonstrated source path begins with a valid business name containing a character represented by a UTF-16 pair across the producer’s 180-code-unit cutoff. The fictional record passes the relevant source category and location filters and has no usable website, so the browser builds a Find contact link. Our own normalizer splits the character. We did not establish that a real provider currently supplies such a record or that any attacker controls it. The seeded saved-list case is a separate prerequisite, not proof that the baseline UI can normally save the already-failing record.
Repair: Build the fixed HTTPS contact-search URL with URL and URLSearchParams. An unpaired surrogate becomes a replacement character only in that outgoing query. Keep the original listing name, identifier and saved record unchanged. The same card renderer now works during search and saved-list restoration. This is a consumer repair: upstream truncation remains unchanged, and the page does not claim that all Unicode source handling has been corrected.
Read the reproduction, controls and limits · Try My People Release 7
FMP-METADATA-001 / Application reliability · Repaired
When nested source metadata interrupted a listing
An object-shaped source identifier passed the listing boundary and broke optional attribution rendering. String checks now ignore unsupported metadata while keeping the listing usable.
The candidate requires malformed nested location evidence for a supported source, with the surrounding attribution fields matching that source. No native producer was shown to create this object shape, and no production injection or attacker access was established. The same unsupported identifier with an unknown source key was ignored in the independent control; a canonical string identifier retained legitimate attribution.
Repair: Require primitive strings before validating location-evidence record IDs and dates. Apply the same check to secondary Ohio and Illinois location-source IDs and the Illinois checked date. Ignore unsupported optional metadata while retaining the underlying listing and its original saved record. Existing source, method, URL, identity and calendar checks still apply; valid source attribution remains visible.
Read the reproduction, controls and limits · Try My People Release 7
FMP-CATALOG-001 / Application reliability · Repaired
When broken suggestions stop a typed search
A fresh My People page received a malformed occupation catalog. The page said suggestions were unavailable and that a service could still be typed, but typing or submitting then failed before a search request was made. A valid catalog and a valid empty catalog each allowed one fictional search and one visible result.
Repair: Read the response within a 1 MiB byte limit, validate and detach the full catalog, and prepare its controls before committing it. Reject malformed or oversized suggestions while retaining the usable category state. A valid empty catalog remains a supported state, so typed search still works.
The unchanged-source run covered eight catalog shapes in each engine. Positive controls were a valid catalog and a valid empty catalog. Repaired cases require a completed typed search and no uncaught page error. Unit checks also exercise the actual 1,027-entry catalog, duplicate slugs, UTF-8 byte limits and cancellation of oversized streams.
Fictional local data reproduced the failure in Edge and Windows Playwright WebKit. No browser-engine flaw, attacker-controlled path or customer-loss measurement is established. Read the case and its limits · Try My People Release 6
FMP-RESTORE-001 / Application reliability · Repaired
Recovering a saved list without overwriting it
A synthetic saved list contained one valid person and a second record with a numeric phone or object-shaped listing type. Both records passed the old basic identity check. Rendering stopped after one card, while the saved count showed two; startup navigation did not initialize. A malformed cross-tab replacement and a pre-existing malformed history entry also interrupted restoration. Original local-storage bytes were not deleted.
Repair: Use a shared listing contract before rendering or restoring. At startup, show usable recovered entries while retaining the original storage bytes. Pause mutations when recovery is needed; explicitly clearing the entire saved list is a deliberate reset. Reject a malformed cross-tab replacement before changing the committed in-tab list. Reject malformed history snapshots before applying them. A storage event does not undo another tab’s write: the repair preserves this tab’s committed view, not an atomic cross-tab transaction.
Valid and empty stored lists remain usable. Repaired checks cover mixed and all-invalid records, preservation of raw storage, blocked implicit overwrites, explicit clearing, cross-tab rejection, malformed history and ordinary filters with Back, Forward and refresh. These are local-state recovery checks, not account authorization tests.
Fictional local data reproduced the failure in Edge and Windows Playwright WebKit. No browser-engine flaw, attacker-controlled path or customer-loss measurement is established. Read the case and its limits · Try My People Release 6
FMP-SOURCE-001 / Application reliability · Repaired
When an inherited source name cleared visible results
My People showed one fictional result and saved it. A replacement home-health record used an inherited object-property name as its location source, with the listing state and the location-evidence method and URL absent. The plain object lookup returned an inherited value, and rendering later tried to use a missing validation rule. The replacement left zero visible cards. The saved shortlist remained intact.
Repair: Require the source label to be an own property of the application’s fixed source registry before consulting its validation rules. Unsupported metadata is ignored. The listing can still render, and supported source attribution is preserved.
Three inherited names and one ordinary unknown-source control were checked in each engine on exact baseline source. The six inherited-name cases changed one visible result to zero; both unknown-source controls retained one. Repaired checks require one visible result and preserved saved state for every case.
Fictional local data reproduced the failure in Edge and Windows Playwright WebKit. No browser-engine flaw, attacker-controlled path or customer-loss measurement is established. Read the case and its limits · Try My People Release 6
FMP-RESPONSE-001 / Application reliability · Low severity · Repaired
A malformed search response erased the completed results.
My People displayed 12 fictional listings. A later successful HTTP response containing a null listing name left zero visible results and disabled the app’s history navigation. The saved shortlist stayed intact. Both Microsoft Edge 157.0.4341.46 and Playwright WebKit 26.5 on Windows reproduced the failure.
Repair: validate the candidate before committing it. The same two browser checks now retain all 12 results and show a retry message. Six targeted regressions cover malformed response shapes and valid empty results.
An ordinary failed request retained the results in both versions. Tested markup-shaped names stayed text and unsafe website links were blocked. These fictional local checks establish an application defect, not a browser-engine vulnerability, a customer incident or an attacker’s ability to provide the response. Physical mobile devices remain untested.
Read the search-response case study · Try My People Release 5
OCA-RECOVERY-001 / Application reliability · Low severity · Repaired
A failed sample load removed an existing review.
In Order Confirmation Auditor, trying another fictional sample cleared the current file pair, comparison and notes before the sample was ready. A controlled request failure left that in-tab work unavailable. Original files and reports already downloaded were not deleted.
Measured result: the failure reproduced in Edge and Playwright WebKit, with another independent Edge reproduction. Changing only the selector preserved the existing report; successfully loading a replacement correctly started a new review.
Repair: the current workspace stays intact while a candidate sample is checked. Comparison, review editing and exports wait. Failure retains the prior review; success replaces the pair together. Later source, tolerance or clear actions cancel pending work and prevent old results from returning.
All 23 targeted local regression cases passed after the repair, including malformed samples and canceled or superseded requests. Open Order Confirmation Auditor Release 3.
Understand the recovery test and its limits
On an authorized local copy with fictional files, annotate a comparison and download its JSON. Change the sample selector without loading: the report should remain unchanged. Then fail a replacement sample request locally and check that the original pair hashes and annotations are still available after failure. A successful replacement should begin unreviewed.
The environments were Microsoft Edge 157.0.4341.46 and Playwright WebKit 26.5 on Windows. The matrix includes controlled old-handler dispatches as robustness checks, not an attacker capability. This is an application recovery defect, not a browser-engine vulnerability. We did not measure real customer loss or how often this occurred. Firefox and physical Safari/mobile devices remain untested. See OCA-RECOVERY-001 and recoveryRegressionSummary in the evidence file.
Read the review-recovery case study
APP-STARTUP-001 / Application reliability · Low severity · Repaired
A visible file control was not always a ready file control.
Holding back the application module exposed an interaction gap in four of our CSV tools. Three sample buttons ignored early clicks. Four file inputs held a selected synthetic file, but application status did not reflect it.
Measured result: 21 lost actions in 24 controlled checks across Edge, Chrome and Playwright WebKit. Margin Guard’s already-protected demo button supplied the three passing negative controls. Repeating every action after initialization worked.
Repair: intake and policy controls now wait for completed initialization. In the matching 24 repaired checks, every tested control stayed unavailable before readiness and worked afterward. Existing comparison and export prerequisites remain in place.
Verified repairs: Margin Guard Release 6, Supplier File Converter Release 3, Supplier Quote Comparator Release 2 and Order Confirmation Auditor Release 2.
Reproduce the boundary, understand the limit
On an authorized local copy with synthetic files, hold the application module request after the HTML appears. Try a sample or select a file; then release the request and inspect the application’s loaded-file status. Repeat after initialization as a control. Our file selections used browser automation, not a physical operating-system picker.
The startup checks ran in Microsoft Edge 157.0.4341.46, Google Chrome 156.0.8078.48 and Playwright WebKit 26.5 on Windows. The controlled delay establishes that this failure was possible; it does not measure how often a visitor encountered it. This is an application readiness defect, not evidence of a browser-engine vulnerability, data disclosure or account compromise. See APP-STARTUP-001 and startupRegressionSummary in the evidence file.
Application data integrity · low severity · fixed
Invisible product IDs reached reviewed exports.
A Margin Guard SKU containing only U+200B ZERO WIDTH SPACE could produce a price-change recommendation and appear in the downloaded changes CSV after manual approval. Supplier File Converter blocked that character, but a SKU containing only U+3164 HANGUL FILLER passed its validation and approved import export.
Both paths were reproduced with fictional local files in fresh Edge contexts. The visitor had to choose the files and explicitly approve the export. We observed invalid identity data in the exported CSVs; no live inventory change, financial loss, data disclosure or code execution was observed.
Repair: check for meaningful identity content as well as unsafe formatting controls, while keeping the original source evidence. Margin Guard Release 3 and Supplier File Converter Release 2 block the tested invisible-only and directional-control cases. Six legitimate leading-zero, Arabic, CJK and joiner-containing identities survive the paired conversion, changes and rollback exports unchanged.
The new regressions failed on the original code. After repair, all 28 Margin core checks, 12 Converter core checks and three targeted browser cases passed. This is a conditional application defect; it does not establish a browser-engine vulnerability or guarantee how every Unicode character renders in every font.
Reproduction boundary and repair evidence
Use synthetic data only. The pre-repair Margin case required the same invisible SKU in both cost and price files. The Converter case required an explicit column mapping and review. The repaired controls keep these rows available as evidence but prevent approved output. A finite blacklist alone missed the Hangul filler case; deleting characters would silently change identity, so the repair preserves the raw value and requires correction.
Finding records MG-IDENTITY-002 and SFC-IDENTITY-001 are in the sanitized evidence file. Original fixtures and runnable reproducers remain in the private test workspace. Publication contains observations and repair details, with no executable exploit payload.
Read the invisible-identifier case study
Application availability · low severity · fixed
A small CSV could create a huge hidden page.
Margin Guard accepted a synthetic 500-row cost file with 410 columns. Although it was only 226,863 bytes, rendering created 437,704 page elements, including 425,524 inside closed details. One measured main-thread task lasted 1,099 ms.
This required selecting a crafted file in the app. We observed temporary interaction blocking, with no crash or data disclosure in that test. It is an application resource-amplification issue, not a newly discovered browser-engine flaw.
Repair: limit each source to 100 columns and create detailed source evidence only when a row is opened. The previous wide file now rejects. The comparable accepted 500-row, 100-column case fell from 127,704 to 12,705 initial elements, with no evidence bodies until requested. Timings and element counts describe this controlled environment, not a universal performance guarantee.
Read the CSV rendering case study
Adversarial application checks · passed
Test the controls that protect the workflow.
In the cases run, markup-like input stayed text, prototype-shaped keys did not alter object prototypes, stale file reads could not restore cleared results, and changing inputs revoked approvals and prepared downloads. Formula-risk identifiers were blocked from approved imports.
Both full applications rejected framing. The calculator’s intentional same-origin embed worked while a different-origin frame was denied. We observed no external data requests or persistent browser storage in these synthetic workflows.
These negative results cover the tested inputs and policies. They do not prove that every injection, race, extension or network configuration is safe.
Environment restriction
WebKit rejected a local test port.
The WebKit test environment refused local port 4190 before an application request reached the server. The same application bytes worked on port 4174.
The observed failure was local navigation, not evidence of an application defect. WebKit’s official portAllowed source lists 4190 among blocked ports. Inspect the source and search for 4190.
Test instrumentation
Screenshot capture produced a policy warning.
Our screenshot instrumentation injected styling that WebKit reported as a Content Security Policy (CSP) violation. A control run without screenshot capture completed all eight workflow checks without those errors.
The strict application policy was retained. Captured screenshots were reviewed separately; the warning is recorded as a testing-tool effect, not a discovered browser vulnerability.
Application issue · fixed
A small companion link needed more touch space.
At a 320px viewport, a companion navigation link measured 42.09px high. Its target was increased to at least 44px and checked again.
This was a layout defect we could correct directly. The measured target size is evidence for that control, not a claim of complete accessibility certification.
Data integrity · verified
The file checksum includes the original BOM.
The live supplier-to-margin round trip preserved SKU 00123. A synthetic UTF-8 file with a byte order mark (BOM) matched its displayed SHA-256 checksum to the exact uploaded bytes, including the BOM.
This verifies file identity in that test. It does not establish that the contents of a supplier’s real file are correct.