Read the explanation
The saved mount planner computes illustrative VFS timing by cache mode and selected concurrency. At concurrency four, off mode is twelve point four divided by four, or three point one seconds; writes is three point six divided by four, or zero point nine; full is one point two divided by four, or zero point three. At fifty pixels per assigned second these bars measure one hundred fifty five, forty five and fifteen. Increasing concurrency to eight halves each formula result. The interface is not performing remote reads or observing storage throughput. These values are assigned estimates, and its fixed one hundred forty five second manual comparison is a fixture rather than a measured baseline. The initial chunk size is sixty four megabytes. Writes mode rounds chunk times two point eight to one hundred seventy nine megabytes, and full mode rounds chunk times six point five to four hundred sixteen. At half a pixel per assigned megabyte those bars measure eighty nine point five and two hundred eight. Doubling the chunk to one hundred twenty eight yields three hundred fifty eight and eight hundred thirty two megabytes. This allocation is a formula, not actual disk usage. The token estimate uses only the first three illustrative file sizes, two point four plus forty five plus eight point one megabytes, while the one hundred twenty megabyte snapshot is excluded. Its displayed stale percentage is literal zero rather than freshness verification. The timing bar uses timing divided by one hundred forty five times one hundred, then clamps its width between four and eighty five percent. A zero point nine second writes estimate would be only about zero point six two percent of that baseline but is drawn at four percent. At ten pixels per percentage point the unclipped and clipped bars measure about six point two and forty. Export creates a JSON bundle of selected cache parameters, four endpoint fixtures, MCP configuration text and a shell script. Clicking simulate adds cached-file labels and later changes status; it does not mount storage, run the shell script or authenticate a provider. Configurations and live mount verification remain distinct.