docs(captain): read-view note moves to docs/captain.md (capy skill budget is fixed); adopt already-created cross-project threads (A1)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

capy/skill/gstack/SKILL.md

@@ -81,7 +81,6 @@ In a repository with a sealed configuration (a `sealed` key in its `.gstack/preg
 - Use Capy's user-visible messaging and question tools for output and decisions. Plain assistant text is not a delivered message in Capy. Use Capy's task and pull-request workflows rather than unavailable Claude or Codex host tools.
 - Capy has no native gstack host target. Claude hooks do not become enforced Capy hooks; safety skills are advisory here, and `/autoplan` prints `autoplan guard: not enforced by this host` once to say so. Report missing capabilities instead of silently claiming equivalent enforcement.
 - Selecting GPT-6 Astra or Claude in Capy does not install or authenticate the Codex or Claude Code CLI. For cross-model reviews, a subagent on another model family is a full outside voice; record the model that reviewed. Do not report a missing Codex CLI as degraded coverage when another runner reviewed.
-- `tools.capy.read` returns a view, not the whole file: about the first 38,000 characters, each line cut at 2,000. A read, change and `tools.capy.write` program therefore saves a truncated file, Drive files included. Edit long files with `tools.capy.edit`, or read and write the whole file in bash or Python and check the line count afterward; `tools.drive.history` restores a recent version.
 - Preserve the user's requested scope, decisions, and consent. Do not enable telemetry or remote artifact sharing on their behalf. Installing gstack does not authorize merging, deploying, destructive operations, or bypassing approvals.
 
 ## Maintenance

changelog.d/garrytan-r68-crew-threads-attach.md

@@ -1,6 +1,6 @@
-**A crew thread no longer creates threads itself. It asks its Captain, so every new thread joins a crew from the start (R68). The Capy skill also warns that `tools.capy.read` returns a cut-down view of long files.**
+**A crew thread no longer creates threads itself. It asks its Captain, so every new thread joins a crew from the start (R68). docs/captain.md also warns that `tools.capy.read` returns a cut-down view of long files.**
 
 ### Changed
-- **docs/captain.md** has a new section, "New threads join the crew". A crew thread asks its Captain for a new thread, and the Captain creates it in the crew. A thread the crew thread already made gets reported by code in that turn, so the Captain can add it with `crew.add`. A thread in another project goes Captain to Captain, and the receiving Captain creates it in its own crew as work, briefs it and returns the result. Only a project with no Captain lets the crew thread create the thread itself, with the code recorded on the work's issue. The cause: GBRA-240 created GBEV-33 directly in another project, and that thread ran outside every crew.
+- **docs/captain.md** has a new section, "New threads join the crew". A crew thread asks its Captain for a new thread, and the Captain creates it in the crew. A thread the crew thread already made gets reported by code in that turn, so the Captain can add it with `crew.add`. A thread in another project goes Captain to Captain, and the receiving Captain creates it in its own crew as work, briefs it and returns the result. Only a project with no Captain lets the crew thread create the thread itself, with the code recorded on the work's issue. A cross-project thread the crew thread already made goes to that project's Captain to adopt, with its code on the issue. The cause: GBRA-240 created GBEV-33 directly in another project, and that thread ran outside every crew.
 - **The Capy factory context (`factory.md` point 12)** now has the short version and cites that section. Its byte budget in `test/capy-skill-wrapper.test.ts` goes from 3,300 to 3,450: the page's new size rounded up to the next 25 bytes, and no other point was trimmed.
-- **The Capy skill's host adaptations** say that `tools.capy.read` returns about the first 38,000 characters, with each line cut at 2,000. So a read, change and `tools.capy.write` program saves a truncated file, Drive files included. Edit long files with `tools.capy.edit`, or read and write the whole file in bash or Python and check the line count. `tools.drive.history` restores a recent version. This is how the org knowledge base's rules.md lost 37 rules. The skill's context-budget ceiling (`test/fixtures/context-budget.json`) goes from 5,315 to 5,425 tokens, the measured 5,409 rounded up to the next 25, for this one line.
+- **docs/captain.md, Drive layout** says that `tools.capy.read` returns about the first 38,000 characters, with each line cut at 2,000. So a read, change and `tools.capy.write` program saves a truncated file, Drive files included. Edit long files with `tools.capy.edit`, or read and write the whole file in bash or Python and check the line count. `tools.drive.history` restores a recent version. This is how the org knowledge base's rules.md lost 37 rules. It lives in the docs page rather than the Capy skill because the skill sits at its fixed 5,315-token context budget.

docs/captain.md

@@ -66,6 +66,13 @@ surface. Keep it small and predictable:
 Scope instructions in the drive root (`AGENTS.md`, `CREW.md`) apply to every thread in
 the crew, so a rule written there needs no relaying.
 
+On Capy, `tools.capy.read` returns a view of a file, not the whole file: roughly the first
+38,000 characters, with each line cut at 2,000. A program that reads a file, changes it
+and writes it back with `tools.capy.write` therefore saves a truncated copy, and drive
+files are no exception. Edit long files with `tools.capy.edit`, or read and write the
+whole file in bash or Python and check the line count afterward. `tools.drive.history`
+restores a recent version of a drive file.
+
 ## CREW.md: the lanes' contract
 
 gstack holds how the work is done; a crew's `CREW.md` holds only what is specific to that
@@ -145,7 +152,10 @@ thread asks its Captain, who asks that project's Captain to create and own the t
 the results come back the same way. For the receiving Captain, that ask is work: it
 creates the thread in its own crew, briefs it and returns the result. Only when the other
 project has no Captain does the crew thread create the thread itself, and then it records
-the new thread's code on the work's issue so the thread can still be found.
+the new thread's code on the work's issue so the thread can still be found. A thread the
+crew thread already created in another project goes the same way: it reports the code to
+its Captain, who asks that project's Captain to adopt the thread, and the code goes on
+the work's issue.
 
 Why: a crew thread once created a thread in another project directly. That thread ran
 outside every crew, so no Captain briefed it, tracked it or could archive it.

test/context-budget-ratchet.test.ts

@@ -23,11 +23,6 @@
  *      copy-paste): fix the bloat instead.
  *   3. After a token-reduction phase lands: re-run the capture so ceilings
  *      ratchet down and the win is locked against regression.
- *
- * Hand pin: capy/skill/gstack went from 5315 to 5425 (measured 5409, rounded up
- * to the next 25, no headroom) for the host-adaptation line saying
- * tools.capy.read returns a cut-down view, so a read-then-write truncates
- * (2026-11-03). Raise a hand pin only by what the change needs.
  */
 import { describe, test, expect } from 'bun:test';
 import * as fs from 'fs';

test/fixtures/context-budget.json

@@ -9,7 +9,7 @@
     "browser-skills/hackernews-frontpage": 371,
     "canary": 7738,
     "captain": 6551,
-    "capy/skill/gstack": 5425,
+    "capy/skill/gstack": 5315,
     "careful": 1239,
     "codex": 9890,
     "context-restore": 6287,