@c4a/context 0.7.30 → 0.7.34
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/guides/lark-resources.md +22 -10
- package/package.json +1 -1
|
@@ -12,7 +12,8 @@ resource checks; it does not fetch that supplied body again. See
|
|
|
12
12
|
|
|
13
13
|
| Resource | Default capture behavior |
|
|
14
14
|
|---|---|
|
|
15
|
-
| Image
|
|
15
|
+
| Image | Download the original; on explicit download permission denial, try a same-identity preview once and mark it as a preview. |
|
|
16
|
+
| Attachment | Download the original file and link it from the Markdown projection. |
|
|
16
17
|
| Sheet | Read the complete selected sheet, render a Markdown table, and retain a CSV snapshot. |
|
|
17
18
|
| Base | Read the selected table/view with pagination, render a Markdown table, and retain a canonical JSON snapshot. |
|
|
18
19
|
| Whiteboard and diagram | Retain a readable preview plus the raw structured export. |
|
|
@@ -28,21 +29,22 @@ preserves an unavailable-resource notice with the reason code
|
|
|
28
29
|
`document.resource.source-missing`, reports a warning, and continues capture;
|
|
29
30
|
it does not pretend that the deleted content was materialized. When the current
|
|
30
31
|
identity can read the document body but the API explicitly returns
|
|
31
|
-
|
|
32
|
+
an explicit permission denial (including HTTP 403) for an embedded resource, Context records
|
|
32
33
|
`document.resource.permission-denied`, keeps the stable resource identity in
|
|
33
34
|
the audit layer, renders the same unavailable-resource notice, and continues
|
|
34
|
-
with a warning.
|
|
35
|
-
|
|
35
|
+
with a warning. Explicit missing-scope and access-denied resource responses are
|
|
36
|
+
likewise recorded without changing identity. Transient network errors, malformed
|
|
37
|
+
payloads, and unclassified failures still block capture. Reference-only
|
|
36
38
|
resources remain explicit in the capture report. Unknown non-empty XML blocks
|
|
37
39
|
stay auditable in the raw XML and receive a warning; the CLI does not infer
|
|
38
40
|
their meaning.
|
|
39
41
|
|
|
40
|
-
Document and resource reads share one access identity.
|
|
41
|
-
user
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
42
|
+
Document and resource reads share one access identity. The configured default is
|
|
43
|
+
user. Bot mode permits one whole-document user fallback for a body authorization
|
|
44
|
+
failure, restarting all pages. After the body is read, resources remain under
|
|
45
|
+
that identity. A resource failure never requests another identity's credentials.
|
|
46
|
+
Legacy explicit auto mode may select Bot when user credentials are unavailable;
|
|
47
|
+
all resources still use the identity that supplied the complete body.
|
|
46
48
|
|
|
47
49
|
## Storage lifecycle
|
|
48
50
|
|
|
@@ -178,3 +180,13 @@ limits. The reading meaning of an image is handled in writing and Review.
|
|
|
178
180
|
Source document links can be retained for viewing under the reader's permissions.
|
|
179
181
|
Temporary signed media links are not durable image hosting. Do not embed access
|
|
180
182
|
tokens in generated pages or claim that excluded images have been interpreted.
|
|
183
|
+
|
|
184
|
+
### Capture identity and unavailable media
|
|
185
|
+
|
|
186
|
+
The selected document identity remains fixed for resource reads. In Bot mode,
|
|
187
|
+
only an authorization failure while reading the body can restart the article
|
|
188
|
+
as the current user. Resource failures never trigger that identity fallback.
|
|
189
|
+
Images may use the official same-identity preview endpoint after download
|
|
190
|
+
permission is denied. Previews are marked explicitly; unavailable resources
|
|
191
|
+
retain references and diagnostics. Use available body evidence without inferring
|
|
192
|
+
missing resource contents, and review evidence gaps before approving conclusions.
|