@lazyingart/agintiflow 0.20.143 → 0.20.144
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lazyingart/agintiflow",
|
|
3
|
-
"version": "0.20.
|
|
3
|
+
"version": "0.20.144",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "AgInTiFlow is a project-aware agent workspace for hybrid wet-dry R&D, hardware-aware intelligence, software automation, and industrial workflows.",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -43,6 +43,8 @@ For classical Chinese texts, bracketed notes such as `〈 ... 〉`, inline comme
|
|
|
43
43
|
|
|
44
44
|
Chunk boundaries must not create malformed note syntax. Avoid putting a leading close marker such as `〉` at the start of a subchunk; attach it to the previous subchunk so the writer sees balanced source context.
|
|
45
45
|
|
|
46
|
+
For dense classical texts that require one-token-per-Hanzi plus Japanese glosses, start with provider-safe subchunks around 120-160 source characters. If outputs become malformed near provider token limits, retune smaller immediately instead of repeatedly retrying oversized chunks.
|
|
47
|
+
|
|
46
48
|
For grammar coloring, assign `g` using only: `subject`, `predicate`, `object`, `attributive`, `adverbial`, `complement`, `topic`, `function`. Color PDFs depend on these fields: every Chinese Hanzi token and every Japanese kanji token should carry `g`. Blackwhite builds should force all grammar colors to black through the renderer, not by deleting `g`.
|
|
47
49
|
|
|
48
50
|
## Completion Evidence
|