docs: the hosting guide still says user-marked untrusted files are not a taint source

Open Beginner friendly
#3,479 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, typescript
Domain
documentation

Research direction

The stale sentence is at the end of the taint passage in docs/hosting/agent-workers.md (lines 1623-1625). Read the G6 section of docs/decisions/governed-writable-workers.md (the untrusted-input anchor) to confirm what marked files do, then rewrite the sentence to match and link to that anchor. Done when the guide no longer calls marked files a non-source and tests/decision-citations.test.ts passes.

Written by the indexing model from the issue text.

Description

agent-ready area: docs priority: p3 type: docs

Context

Found while reviewing #3478 (#3429). The hosting guide's taint passage ends with "Files the user marks untrusted are not a source yet" (docs/hosting/agent-workers.md:1623-1625, at main d142e997b). That is out of date: marked files have tainted the session since the untrusted-marks work for #2673 (PR #3287), and #3478's decision-record update lists them as a taint source.

Scope

Rewrite that sentence to describe what marked files actually do, and link to the G6 section of the decision record (docs/decisions/governed-writable-workers.md#untrusted-input-g6) for the rules. Docs only.

Acceptance criteria

  • docs/hosting/agent-workers.md no longer says marked files are not a taint source, and it states the current behaviour consistently with the G6 section.
  • tests/decision-citations.test.ts passes.
Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
5h 13m
Merged PRs (30d)
953

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from schlessera/brain-kit

All issues in schlessera/brain-kit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.