gofer-documentationlisted

# Gofer Documentation And Lineage Use this skill whenever an agent creates or changes delivery documentation in a Gofer workspace. The durable outputs are human-readable Markdown plus `.specify/specs/{feature}/delivery-lineage.json`. ## Trust Boundary Gofer is customer-side. Read `.specify/references/delivery-lineage.md` before writing and enforce all of its export rules. - Use `plane: customer`. - Stop EAI dependencies at a `public-api-capability` node from `PublicAPI`. - Never name or link internal EAI services, repositories, policies, infrastructure, `tech-docs`, or personal absolute paths. - Do not create an internal graph and rely on a viewer filter. The persisted graph itself must be safe for the customer. - Record concise rationale and evidence, never hidden chain-of-thought. ## Write The Markdown 1. Preserve the repository's existing documentation conventions. For a new durable document, use frontmatter with a stable `doc_id`, `title`, `status`, `owners`, and `updated` date. 2. Keep the stable `doc_id` when the title or path changes. Mark replaced documents `superseded` and link their replacement. 3. Use descriptive headings so graph sources can point to exact anchors. 4. Separate requirements, decisions, considered options, concise rationale, acceptance evidence, and outcomes. Do not present a plan as delivered fact. 5. Use repository-relative links and paths. Include a Git commit and SHA-256 content hash in lineage sources when known. ## Re