25 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
the_og	2d9fb083dc	Fix: correct smart-quote/nbsp characters mangled in previous push	2026-07-07 20:56:14 -04:00
the_og	4ab3c3b00a	Fix: rebuild from clean main (previous push included unrelated contaminated content)	2026-07-07 20:51:26 -04:00
the_og	3e07b51134	Fix: rebuild from clean main (previous push included unrelated contaminated content)	2026-07-07 20:48:52 -04:00
the_og	a811e323e6	Fix: rebuild from clean main (previous push included unrelated contaminated content)	2026-07-07 20:44:39 -04:00
the_og	2b3843a714	feat: add View logs button + LogViewerDialog for in-app MCP log viewer (#6)	2026-07-07 20:40:32 -04:00
the_og	85d47aea97	test: add server_log_path coverage (macOS, Windows, missing, unsupported) (#6)	2026-07-07 20:36:58 -04:00
the_og	f9752211a2	test: add coverage for config_fingerprint mtime+size hardening (#17) ... Includes the required regression case: rewrite a file with different content, force the original mtime back via os.utime, and assert the fingerprint still differs (because size changed).	2026-07-07 20:35:03 -04:00
the_og	7c8fd6d0bb	fix: use explicit backslash-u-0-0-a-0 escape for non-breaking space literal	2026-07-07 20:34:53 -04:00
the_og	f1935fe320	feat: use mtime+size fingerprint for stale-file check (#17) ... MainWindow._loaded_mtime -> _loaded_stat (core.ConfigStat), populated via core.config_fingerprint() at load/save time. The save-path stale check now compares the full fingerprint (mtime AND size) instead of bare mtime equality.	2026-07-07 20:33:38 -04:00
the_og	346d0aabb6	fix: use   escape for non-breaking space (byte-exact transcription fix)	2026-07-07 20:30:35 -04:00
the_og	5d59c1c423	fix: restore actual file content (previous commit had placeholder text by mistake)	2026-07-07 20:30:03 -04:00
the_og	0843c51c7d	tests/test_core.py: add resolve_name_collision unit tests	2026-07-07 20:27:24 -04:00
the_og	82cec27c11	fix: use chr(0xA0) instead of a literal/escaped NBSP ... Two prior attempts to fix this line via a literal or  -escaped non-breaking space both silently reverted back to a no-op regular-space replace during transcription. Using chr(0xA0) instead removes any non-ASCII or backslash-escape character from the source line entirely.	2026-07-07 20:27:17 -04:00
the_og	4b45251682	fix: actually apply the non-breaking-space escape fix ... The previous commit message said this was fixed but the content still had the literal (unescaped) line. Apply the   escape for real this time.	2026-07-07 20:26:37 -04:00
the_og	2a0802b22f	bcc.py: unify paste/drop collision handling via shared _import_server() prompt	2026-07-07 20:26:00 -04:00
the_og	8d90ab449d	feat: add server_log_path() for in-app MCP log viewer (#6)	2026-07-07 20:24:10 -04:00
the_og	9760b1537e	fix: restore non-breaking-space literal lost in transcription ... The previous commit accidentally normalized the non-breaking space (U+00A0) in _normalize_unicode's replace() call to a regular space during a copy/paste, turning that replace() into a no-op. Use an explicit   escape instead of the literal character so it can't be silently corrupted again.	2026-07-07 20:23:44 -04:00
the_og	0f1cdbef3c	bcc_core.py: fix non-breaking-space byte lost in transcription	2026-07-07 20:22:45 -04:00
the_og	165c65be5f	bcc_core.py: add resolve_name_collision() for paste/import name-collision handling	2026-07-07 20:19:25 -04:00
the_og	3c65657d2f	feat: harden stale-file detection with mtime+size fingerprint (#17) ... Bare mtime equality can miss a concurrent external write that lands within the filesystem's mtime resolution (same-second writes), or where the writer restores the original mtime. Add config_fingerprint() returning a (mtime, size) ConfigStat pair; the stale-file check in bcc.py now compares both fields instead of mtime alone. config_mtime() is kept as-is (still used/tested independently).	2026-07-07 20:17:57 -04:00
the_og	832e5fa048	fix: bump spawn-test timeouts to avoid CI flakiness (closes #12) ... The crashed/exited/stderr spawn tests used 0.3-0.5s timeouts. On a slow CI runner, interpreter startup can exceed that, so the process is still starting when the timeout fires, gets killed, and is misclassified "ok" (still running) instead of "crashed"/"exited". Bump those three to 2.0s. The two "ok" paths (sleep-60, stdin-block) stay at 0.3s since timing out there means success.	2026-07-04 13:12:04 -04:00
the_og	ece049c993	Merge pull request 'feat: secret-in-args warning badge (#1r)' (#16) from feat/1r-secret-args-badge into main ... feat: secret-in-args warning badge (#1r) — Closes #1	2026-07-02 12:00:16 -04:00
the_og	13d6b917bb	Merge pull request 'feat: stale-file protection — detect concurrent edits on save' (#15) from feat/4-stale-file-protection into main ... Merge feat/4-stale-file-protection: stale-file protection (closes #4)	2026-07-02 02:08:13 -04:00
the_og	be45be9eab	Merge pull request 'feat: backup restore UI (#3)' (#14) from feat/3-backup-restore-ui into main ... feat: backup restore UI (#3) — closes #3	2026-07-02 01:44:44 -04:00
the_og	111fa8e367	Merge pull request 'feat: stdio server spawn-test (#2)' (#11) from feat/2-stdio-spawn-test into main ... Merge feat/2-stdio-spawn-test into main	2026-07-02 01:11:48 -04:00