Skip to content

AGENTS.md's built-in-entry list and putSymlink wording are now slightly stale; that is the norms layer and should land as its own proposal PR rather than in this feature change. #61

Description

@Alex1990
No description provided.

Activity

  1. github-actions commented on Sep 18, 2026

    @github-actions
    Contributor

    Loop triage — feature / ready-for-agent (confidence: high)

    Confirmed against the tree: PR #60 added the Volcano Engine TOS entry but AGENTS.md was not updated with it, and the report's title names exactly the stale spots. All three are in AGENTS.md:

    • Line 3 — built-in-entry list omits TOS. It ends "…Huawei Cloud OBS, AWS S3 (plus S3-compatible stores), Azure Blob Storage." README.md:12 already lists "…Huawei Cloud OBS, Volcano Engine TOS, AWS S3 (plus S3-compatible stores) and Azure Blob Storage", and package.json now exports ./tos.
    • Line 7 — entry-path example omits tos. It still reads src/cos|obs|aws|azure/index.ts; src/tos/{host,index,request,signature,signatureUrl}.ts exists.
    • Line 10 — "putSymlink is OSS-only" is wrong. src/tos/index.ts sets supportsSymlink: true and symlinkHeaders: (t) => ({ 'x-tos-symlink-target': t }), and exports putSymlink; README.md:440 says the TOS entry exports everything the OSS entry does, including putSymlink. The other entries (COS/OBS/AWS/Azure) still set supportsSymlink: false, so the accurate wording is that putSymlink is exported by the OSS and TOS entries only.

    Per AGENTS.md, norms-layer changes (this file, docs/agents/*, skills/*) land as a proposal PR that a human merges — never folded into a feature change. The loop's feature stage will therefore open a PR touching only AGENTS.md (three lines, no code, no workflows), committed as chore(norms) so it does not leak into CHANGELOG.md.

    Labelling ready-for-agent. If you'd rather fold this into a future docs pass instead, say so and we can close it.

  2. added
    ready-for-humanRequires a human: implementation, merge of a loop PR, or a release call
    and removed
    ready-for-agentFully specified, an AFK agent may handle it unattended
    on Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-humanRequires a human: implementation, merge of a loop PR, or a release call

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions