Changed

The agent context file records the reconnaissance gate as closed, names the remote, and states which continuous integration jobs have actually completed. It previously told an agent that questions Q-1 through Q-6 were open and that the repository had no remote, both of which would have halted work that is in fact unblocked.

Withdraws the capture-time redaction rules introduced in specification 0.1.1-draft. Process command lines are recorded verbatim again, as originally specified. Scope remains the operator's control and preparation for publication becomes an explicit downstream operation on a copy. Adds constitution principle P-9, The Instrument Does Not Lie (constitution 1.1.0): what fragcap reports is what fragcap observed, and no capture path alters an observation to produce a safer result.

Specification revised to 0.1.1-draft with the reconnaissance findings for both focal titles. Assumptions A-1 through A-4 are confirmed by measurement and A-5 is refuted: the launcher-to-client handoff is a command line argument rather than loopback traffic. Command lines are consequently treated as credential-bearing and are off by default, never entering capture output. Appendix D is populated.

• cargo xtask notes now stops at the ### Decisions section. Release notes are derived from CHANGELOG.md, and the decisions section records verbose internal rationale for changing pinned artifacts; a single decision fragment runs to kilobytes. Excluding it keeps the release page to the curated Highlights and the user-facing Added, Changed, and Fixed sections, while the full detail, decisions included, stays in CHANGELOG.md.

• The landing page presents the value proposition (issue #42, specification section 23.1 as amended). It leads with the problem fragcap solves that standard tooling does not: capture below the socket layer has already discarded the packet-to-process association, and for a client started indirectly through a launcher the owning process is not the launcher. It keeps the one worked invocation and the prerequisite honesty ("detects npcap, never installs it"), and adds a small number of concrete capability statements, each a plain fact linking into the documentation that proves it rather than an adjective. It still carries no testimonials, no feature grid, and no call to action.