[codex] Add projectgraph skill

skills/.curated/projectgraph/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

skills/.curated/projectgraph/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: projectgraph
+description: Use when a user wants to initialize, seed, maintain, review, validate, auto-capture, or multi-view a ProjectGraph for a Codex Project; supports trace-first graph maintenance, Codex JSONL locators, hidden provenance, Markmap viewer setup, perspective views, and drift checks.
+---
+
+# ProjectGraph
+
+ProjectGraph is a file-based, human-facing structure map for a Codex Project. Use this skill when a user asks to create a ProjectGraph, migrate an existing Project into ProjectGraph, maintain Graph after a meaningful boundary, review Graph drift, or package ProjectGraph behavior for another Project.
+
+## Core Rules
+
+- Visible Graph records only conclusions, facts, problem structure, route tradeoffs, and logic chains.
+- Process details stay hidden in trace files and `TRACE_INDEX.json`.
+- Every visible node must trace back to at least one source reference.
+- Use Chinese as the core language by default, while preserving necessary English terms.
+- Do not add `confidence`, `status`, `RawTrace`, `LiveMindMap`, or `StableMap`.
+- Treat ProjectGraph as a record layer, not as an execution authority.
+- Automatic capture may write locator traces, but it must not silently rewrite the visible Graph.
+- Multiple views are display projections over the same canonical Graph, not separate truth sources.
+
+## Workflows
+
+### Initialize A Project
+
+1. Inspect the target Project in read-only mode first.
+2. Run `scripts/bootstrap_projectgraph.py --target <project_root> --project-name <name>`.
+3. If the Project already has `AGENTS.md`, append the ProjectGraph section only when the user wants it; do not overwrite existing project rules.
+4. Run `scripts/validate_projectgraph.py --root <project_root>`.
+5. Tell the user this is only a bootstrap structure; historical seed still requires a read-only exploration pass.
+
+### Generate A Seed Graph
+
+1. Read available history, repo docs, task records, reports, and accessible Codex transcripts.
+2. Write seed traces that state coverage limits and locators.
+3. Build `PROJECT_GRAPH.json`, `PROJECT_GRAPH.md`, and `TRACE_INDEX.json` from conclusions, facts, problem structure, route tradeoffs, and logic chains.
+4. Ask the user to review the seed before treating it as the future baseline.
+5. Run validation and fix drift before finishing.
+
+### Maintain After A Meaningful Boundary
+
+Meaningful boundaries include task completion, design decision, route exclusion, conflict correction, important risk confirmation, and `/compact` before or after context compression.
+
+1. Create a short trace with locator fields.
+2. Update `PROJECT_GRAPH.json`, `PROJECT_GRAPH.md`, and `TRACE_INDEX.json`.
+3. Add sibling nodes for new independent topics.
+4. Add child nodes for additions or refinements to old topics.
+5. Record conflicting conclusions side by side or as later correction nodes; do not silently overwrite old conclusions.
+6. Run validation.
+
+### Capture Codex JSONL Locators
+
+Use this when the user wants ProjectGraph enabled for ongoing Codex work, including ordinary windows, `/side` task windows, `/fork`, `/compact`, and agent task execution.
+
+1. Prefer Codex hook payload fields when available: `session_id`, `turn_id`, and `transcript_path`.
+2. Run `scripts/capture_codex_trace.py --root <project_root>` from a Stop hook or with `--transcript-path <jsonl>` when operating manually. The script reads hook JSON from stdin when available.
+3. Let the script write a trace keyframe containing the absolute transcript path, selected JSONL line numbers, tool-call lines, and `sha256_16` hashes.
+4. Treat `/side` and `/fork` windows as independent Codex sessions: capture their own transcript path instead of merging them into the parent trace.
+5. Promote the captured trace into `PROJECT_GRAPH.json`, `PROJECT_GRAPH.md`, and `TRACE_INDEX.json` only at a meaningful boundary.
+6. Repeated automatic captures should remain idempotent enough for daily use: if a trace title collides, the script appends a time/turn suffix instead of overwriting old evidence.
+7. Keep capture lightweight; do not add a daemon, task board, hidden status model, or automatic judgment loop.
+
+### Add Or Review Perspective Views
+
+Use this when the same ProjectGraph needs different mind-map displays for different readers.
+
+1. Keep `PROJECT_GRAPH.json` as the only canonical graph.
+2. Add display projections under `display.views` with either a `root_id` or a short `node_refs` list.
+3. Use views to reorganize what is shown, not to create new facts.
+4. Recommended first views are:
+   - `global`: project logic and full record.
+   - `technical`: route choices, implementation details, tests, and key conclusions.
+   - `project`: delivery surface, blockers, sequencing, and remaining work.
+   - `product`: user problem, intended behavior, implementation drift, and requirement changes.
+5. Run validation after adding views so every `root_id` and `node_refs` target exists.
+
+## Locator Minimum
+
+Each trace should include:
+
+- `project`
+- `cwd`
+- `date`
+- `timezone`
+- `session_id` or `codex_thread_id`
+- `turn_id`, or `null` with a reason
+- `transcript_path`, or `null` with a reason
+- `field_availability_note`
+- `boundary_type`
+- `user_quote`
+- `assistant_action`
+
+When an original Codex JSONL transcript is discoverable, include the absolute `transcript_path` and useful line numbers in the trace or source locator.
+
+For hook-generated traces, also include a short hash for every cited JSONL line. The trace is a locator and summary, not a copy of the original transcript.
+
+## Bundled Resources
+
+- `scripts/bootstrap_projectgraph.py`: creates the initial `.projectgraph/` structure, local viewer runtime, bootstrap trace, and validator in a target Project.
+- `scripts/capture_codex_trace.py`: writes trace keyframes that point back to Codex JSONL transcripts and selected tool-call lines.
+- `scripts/validate_projectgraph.py`: checks Graph, TraceIndex, trace files, forbidden keys, and viewer references.
+- `scripts/check_release.py`: runs skill-source release hygiene checks before packaging or publishing.
+- `templates/`: reusable target Project templates for AGENTS, trace locator, seed trace, Graph JSON, TraceIndex JSON, and Markdown outline.
+- `assets/`: local Markmap viewer runtime copied into target Projects by bootstrap.
+
+## Release Review Rules
+
+Use these rules when preparing this skill for `openai/skills` or another shared catalog:
+
+- Keep the published skill package minimal: `SKILL.md`, `LICENSE.txt`, scripts, templates, assets, examples, and references only when they are directly used by the skill.
+- Put broad design background, PR strategy, release notes, and reviewer-facing discussion outside the skill package unless maintainers ask for it inside the release artifact.
+- Preserve `assets/vendor/markmap-0.18.12/VENDOR_MANIFEST.json` and `THIRD_PARTY_NOTICES.md` whenever the local viewer runtime is shipped.
+- Do not add CDN fallbacks to `PROJECT_GRAPH.html`; the default viewer should remain local/offline.
+- If maintainers object to shipping vendored viewer assets in a curated skill, propose making the viewer optional or landing the first version in an experimental path while keeping Graph/Trace/validation as the core workflow.
+
+## Self-Bootstrapping Rule
+
+For the `Project_Cartographer` repo itself, keep two records in sync:
+
+- Graph records what was designed, decided, rejected, implemented, and why.
+- This skill records how future Codex agents should initialize, generate, maintain, and validate ProjectGraph in other Projects.