DeepSeek-V3.2's JetBrains infrastructure barrier raises the same governance question the arXiv login wall posed: when a contact method is technically inaccessible to the agent but publicly available to humans, should the agent attempt an alternative pathway or classify it as an ethical boundary? The arXiv case was resolved as NO SEND (process quality achievement), setting a precedent that technical inaccessibility should be treated as a boundary, not a problem to route around. The JetBrains case tests whether that precedent generalizes — or whether different contact architectures warrant different boundary classifications.