Skip to content

docs: add post-0.11 evidence roadmap - #44

Merged
TheAmericanMaker merged 1 commit into
mainfrom
planning/post-0.11-evidence-roadmap
Jul 20, 2026
Merged

TheAmericanMaker merged 1 commit into
mainfrom
planning/post-0.11-evidence-roadmap

Conversation

@TheAmericanMaker

Copy link
Copy Markdown
Member

Summary

  • preserve the post-v0.11 roadmap as a durable checklist
  • record decisions confirmed by the Aimbroidery and FreeAgent dogfood runs
  • prioritize framework-owned state, post-pipeline semantics, open-question closure/deduplication, closeout integrity, and deterministic compaction coverage before publish UX

FreeAgent evidence

  • v0.11.0 completed 7/7 phases with a clean source tree
  • two PASS WITH GAPS and five PASS validations
  • porting bundle worked as the final synthesis boundary
  • exposed status ownership, inherited-question duplication, terminal carry-forward UX, closeout idempotence, and timestamp/schema issues

Verification

  • direct MCP validation of all seven FreeAgent phases
  • git diff --check

@TheAmericanMaker
TheAmericanMaker merged commit f3f7438 into main Jul 20, 2026
5 checks passed
@TheAmericanMaker
TheAmericanMaker deleted the planning/post-0.11-evidence-roadmap branch July 20, 2026 21:52
TheAmericanMaker added a commit that referenced this pull request Sep 21, 2026
The evidence baseline listed six absolute paths under a home directory on the
author's machine. They dated from f3f7438 (#44) and served no reader: the
FreeAgent run was local and its outputs were never published, so nobody
cloning this repo could open any of them. All they carried was the operating
system, the username, and the local directory layout of the machine that made
the release.

Replaced with the same six artifacts named relative to that workspace's
.codecarto/, which is what the surrounding text actually needs - it is citing
WHICH artifacts the conclusions rest on, not offering a link.

R11 sweep - the class is "machine-specific absolute path in tracked content",
swept across the whole tracked tree rather than this file:

- /home/<user>/ - six instances, all here, all closed. Five other hits are
  synthetic test inputs (/home/someone, /home/me) and one is /home/james in
  tests/dashboard.test.mjs, which is the INPUT to a test asserting that an
  absolute session path is not rendered as a link. It is not this machine's
  home and changing it would weaken the test.
- /Users/<user>/ and C:\Users\<user>\ - none.
- bare username, hostname, private IPs - none.
- credential-shaped strings - one hit, "sk-abc...1234", a deliberate fixture
  in a test proving a secret never reaches the provider.

Scope of the original exposure: docs/ is not in package.json files[], so this
never shipped in an npm tarball (verified with a real npm pack: zero docs/
entries). It has been in public git history since f3f7438 and remains there -
this commit stops it being in the current tree, and rewriting history is a
separate decision for the maintainer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant