Repository navigation
docs: close out separate-repo model sharing (FR-023 Phase 2) - #542
Merged
Merged
Conversation
… fixtures) Rewrite the feature page's Phase 2 section as the shipped per-port matrix, name what stays deferred, fix stale transport wording in the port docs, and teach the Java/Kotlin/C# publish paths, the deps checks and the maven/nuget transports in the verify, codegen, authoring, audit and capability-sheet skills. Agent-context expected copies regenerated with the repo generator.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
docs/features/metadata-dependencies.mdand port pages (docs/ports/java.md,csharp.md,python.md) now describe the shipped Phase 2 per-port matrix: consume, check, publish, runtime load and transports, includingmavenandnugetformeta deps.docs/CONFORMANCE.mdmarks the dependency conformance arm as shipped.metaobjects-verify(per-port--depstable, transport coverage per port),metaobjects-codegenandmetaobjects-authoring(dependencies-and-shared-modelsandmetadata-dependenciesreferences),metaobjects-audit(Java, Kotlin, C# and Python references) andmetaobjects-fit-assessment(capability sheet). The matchingagent-context-conformanceexpected fixtures are regenerated.CHANGELOG.mdgains a Documentation entry for the FR-023 Phase 2 close-out.Validation
Risk Assessment
✅ Low: Docs and agent-skill text only, with the generated conformance fixtures kept in step. The one defect found, a stray duplicate table row, is fixed inline. I did not run the agent-context conformance test to confirm the fixtures still match the source skills.
Testing
Pipeline
Updates from git push no-mistakes
✅ **Intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
agent-context/skills/metaobjects-verify/SKILL.md:200- Removed a stale duplicate| Python | metaobjects verify --codegen | ... |row that sat as a 3-column row at the end of the new 2-column 'Dependency drift (--deps) per port' table in the verify skill. It broke the table render. I removed it in the source skill and the 5 generated agent-context conformance fixtures so they stay byte-identical.⏭️ **Test** - skipped
Step was skipped.
⏭️ **Document** - skipped
Step was skipped.
⏭️ **Lint** - skipped
Step was skipped.
✅ **Push** - passed
✅ No issues found.