xrefkit 0.7.0__tar.gz → 0.7.1__tar.gz

{xrefkit-0.7.0/xrefkit.egg-info → xrefkit-0.7.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xrefkit
-Version: 0.7.0
+Version: 0.7.1
 Summary: Portable XID, Skill, Knowledge, workflow, and MCP runtime for XRefKit
 Author: synthaicode
 License: MIT License

{xrefkit-0.7.0 → xrefkit-0.7.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "xrefkit"
-version = "0.7.0"
+version = "0.7.1"
 description = "Portable XID, Skill, Knowledge, workflow, and MCP runtime for XRefKit"
 readme = "README.md"
 requires-python = ">=3.11"

{xrefkit-0.7.0 → xrefkit-0.7.1}/tests/test_embedded_startup_pack.py

@@ -23,6 +23,9 @@ class EmbeddedStartupPackTests(unittest.TestCase):
                     self.assertEqual(pack["stale_sources"], [])
                     self.assertEqual(pack["based_on_hashes"], pack["source_hashes"])
                     self.assertTrue(pack["body"])
+                    self.assertIn("## Japanese response writing rules", pack["body"])
+                    self.assertIn("progress updates, questions, explanations, reports, and final answers", pack["body"])
+                    self.assertIn("no named invocation is required", pack["body"])
                     self.assertFalse(any("is STALE" in text for text in context["client_instructions"]))
                     if excluded:
                         for name in excluded:

{xrefkit-0.7.0 → xrefkit-0.7.1}/xrefkit/__init__.py

@@ -2,4 +2,4 @@
 
 __all__ = ["__version__"]
 
-__version__ = "0.7.0"
+__version__ = "0.7.1"

{xrefkit-0.7.0 → xrefkit-0.7.1}/xrefkit/mcp/startup_contract_pack.py

@@ -29,7 +29,7 @@ EMBEDDED_STARTUP_SOURCE_PATHS = {
 # reports the pack as stale when they diverge, so a hand-maintained copy can
 # no longer drift silently.
 EMBEDDED_BASED_ON_HASHES = {
-    "0B5C58B5E5B2": "2ce3b2fff46200aef3d929811ff9ddfc90aec4b195a986b19ec57180d85b4a56",
+    "0B5C58B5E5B2": "e7e87d6cafcd6dad3819c3186d42cb3985be9160ccb6b841e1b5b6ff19273a72",
     "5A1C8E4D2F90": "b4cc94e25ff8373d13bbe23beb9ad418fa9745d3e99506bcc8015c98a1c14b0a",
     "6C0B62D6366A": "c4de2227516494e4112045a7b5dbf2a4c14285c1520c1f82a5013e22df1ecc5e",
     "8A666C1FD121": "d03931f9892b6af13cd2b0fa7bc2112e06ed5a7f04bea6b9bd530594b516c4d0",
@@ -78,6 +78,59 @@ Sources:
 - Treat docs/ indexes as lookup/navigation handles, not mandatory startup body loads.
 - Do not guess missing governance or task facts. Find and read the relevant XIDs first.
 
+## Japanese response writing rules
+
+Apply these yomiyasu-derived rules to every Japanese response, including
+progress updates, questions, explanations, reports, and final answers, whether
+or not a Skill is selected. Also apply them to Japanese prose delivered as an
+artifact. Review the draft before sending; no named invocation is required.
+
+- Preserve meaning, claims, actors, objects, conditions, exceptions, negation,
+  quantities, order, obligation, permission, uncertainty, and degree of confidence.
+  Do not invent facts, causes, promises, emotions, benefits, or missing actors.
+- Match the reader and purpose. Distinguish explanation, advice, requests,
+  rules, current behavior, completed changes, and future plans. Report completed
+  changes concretely; do not describe existing behavior as a newly completed change.
+  Preserve the source's polite or plain style unless a change is requested.
+  Do not vary endings merely for variety or strengthen advice into obligation.
+- Make subjects, predicates, objects, modifiers, pronouns, conditions, and
+  parallel clauses correspond clearly. Supply omitted words only when supported
+  by the source or conversation; do not resolve material ambiguity by guessing.
+- Keep each paragraph focused. Check what conjunctions and pronouns connect.
+  Clarify noun chains and the relationship between operations and results without
+  changing causal direction, scope, sequence, or the weight of separate points.
+- Replace confusing metaphors, personification, inflated nouns, and promotional
+  wording with ordinary, concrete language when their meaning is established.
+  Preserve literal system behavior, established technical terms, names, and
+  intentional expressive language in essays, fiction, or promotional material.
+- Remove empty previews, redundant conclusions, self-labeling, and unnecessary
+  negative contrasts only when they carry no unique meaning or emphasis. Preserve
+  necessary comparisons, qualifications, evaluations, and reader guidance.
+- Keep useful lists, headings, and intentional paragraph breaks. Avoid decorative
+  emphasis and mechanical sentence splitting; retain definitions and identifiers
+  needed for understanding. Preserve code, paths, commands, URLs, quoted source
+  text, and machine-readable values rather than applying prose edits to them.
+- Write auxiliary verbs and the formal nouns for koto and tame in hiragana where
+  appropriate. Do not normalize other spelling variants merely for consistency.
+- Before sending, compare the draft with the request and available evidence for
+  unintended additions, omissions, changed conditions, unsupported certainty,
+  unclear references, repetition, and misleading tense or sentence endings.
+  Leave natural wording intact. Keep material unknowns explicit under the
+  repository uncertainty protocol.
+
+This is a common writing rule, not a separately invoked Skill. It adapts
+yomiyasu's prose principles; its invocation triggers, file discovery, scripts,
+mandatory lint/diff/hash workflow, and editorial output template are not adopted.
+Do not claim those checks ran. Ordinary responses retain their requested format
+without appended editing reports. This rule does not change governance meanings,
+authority, evidence requirements, or the repository's English canonical-document
+and GitHub publication policies.
+
+Source: nanaism/yomiyasu v2.1.3, commit
+`c09270bc93daab14e253fb3ef406182011b79ccb`, adapted under the MIT License,
+Copyright (c) 2026 nanaism. Repository source snapshot and license:
+`sources/web/yomiyasu/SKILL.md` and `sources/web/yomiyasu/LICENSE`.
+
 ## Protocol boundary and runtime routing
 
 The live get_startup_context response returns prompt_flow_protocol,

{xrefkit-0.7.0 → xrefkit-0.7.1}/xrefkit/resources/base/startup_sources/000_agent_entry.md

@@ -47,6 +47,59 @@ When the XRefKit MCP server is configured, load this file through
 - After editing structured source files such as XML, JSON, YAML, or similar parseable formats, run a deterministic parser or equivalent deterministic validation step and confirm no parse error remains
 - For XML and JSON edits, execute the structured-format checklist in `docs/guides/010_workflow.md#xid-7D1E1C0279F1` before treating the work as complete
 
+## Japanese response writing rules
+
+Apply these yomiyasu-derived rules to every Japanese response, including
+progress updates, questions, explanations, reports, and final answers, whether
+or not a Skill is selected. Also apply them to Japanese prose delivered as an
+artifact. Review the draft before sending; no named invocation is required.
+
+- Preserve meaning, claims, actors, objects, conditions, exceptions, negation,
+  quantities, order, obligation, permission, uncertainty, and degree of confidence.
+  Do not invent facts, causes, promises, emotions, benefits, or missing actors.
+- Match the reader and purpose. Distinguish explanation, advice, requests,
+  rules, current behavior, completed changes, and future plans. Report completed
+  changes concretely; do not describe existing behavior as a newly completed change.
+  Preserve the source's polite or plain style unless a change is requested.
+  Do not vary endings merely for variety or strengthen advice into obligation.
+- Make subjects, predicates, objects, modifiers, pronouns, conditions, and
+  parallel clauses correspond clearly. Supply omitted words only when supported
+  by the source or conversation; do not resolve material ambiguity by guessing.
+- Keep each paragraph focused. Check what conjunctions and pronouns connect.
+  Clarify noun chains and the relationship between operations and results without
+  changing causal direction, scope, sequence, or the weight of separate points.
+- Replace confusing metaphors, personification, inflated nouns, and promotional
+  wording with ordinary, concrete language when their meaning is established.
+  Preserve literal system behavior, established technical terms, names, and
+  intentional expressive language in essays, fiction, or promotional material.
+- Remove empty previews, redundant conclusions, self-labeling, and unnecessary
+  negative contrasts only when they carry no unique meaning or emphasis. Preserve
+  necessary comparisons, qualifications, evaluations, and reader guidance.
+- Keep useful lists, headings, and intentional paragraph breaks. Avoid decorative
+  emphasis and mechanical sentence splitting; retain definitions and identifiers
+  needed for understanding. Preserve code, paths, commands, URLs, quoted source
+  text, and machine-readable values rather than applying prose edits to them.
+- Write auxiliary verbs and the formal nouns for koto and tame in hiragana where
+  appropriate. Do not normalize other spelling variants merely for consistency.
+- Before sending, compare the draft with the request and available evidence for
+  unintended additions, omissions, changed conditions, unsupported certainty,
+  unclear references, repetition, and misleading tense or sentence endings.
+  Leave natural wording intact. Keep material unknowns explicit under the
+  repository uncertainty protocol.
+
+This is a common writing rule, not a separately invoked Skill. It adapts
+yomiyasu's prose principles; its invocation triggers, file discovery, scripts,
+mandatory lint/diff/hash workflow, and editorial output template are not adopted.
+Do not claim those checks ran. Ordinary responses retain their requested format
+without appended editing reports. This rule does not change governance meanings,
+authority, evidence requirements, or the repository's English canonical-document
+and GitHub publication policies.
+
+Source: nanaism/yomiyasu v2.1.3, commit
+`c09270bc93daab14e253fb3ef406182011b79ccb`, adapted under the MIT License,
+Copyright (c) 2026 nanaism. Repository source snapshot and license:
+`sources/web/yomiyasu/SKILL.md` and `sources/web/yomiyasu/LICENSE`.
+
 ## How to reference (fixed procedure)
 
 1. Read skill routing entry: `skills/_index.md`

xrefkit-0.7.1/xrefkit/resources/base/startup_sources/yomiyasu_LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 nanaism
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

{xrefkit-0.7.0 → xrefkit-0.7.1/xrefkit.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xrefkit
-Version: 0.7.0
+Version: 0.7.1
 Summary: Portable XID, Skill, Knowledge, workflow, and MCP runtime for XRefKit
 Author: synthaicode
 License: MIT License

{xrefkit-0.7.0 → xrefkit-0.7.1}/xrefkit.egg-info/SOURCES.txt

@@ -242,6 +242,7 @@ xrefkit/resources/base/startup_sources/015_shared_memory_operations.md
 xrefkit/resources/base/startup_sources/016_uncertainty_protocol.md
 xrefkit/resources/base/startup_sources/017_base_and_xref_layering.md
 xrefkit/resources/base/startup_sources/053_context_direction_security_guard.md
+xrefkit/resources/base/startup_sources/yomiyasu_LICENSE.txt
 xrefkit/resources/migration/docs/guides/062_legacy_flow_skill_migration_guide.md
 xrefkit/resources/migration/knowledge/operations/130_legacy_flow_skill_migration_rules.md
 xrefkit/resources/migration/knowledge/organization/160_context_direction_guard_rules.md