Repository navigation
Move to Optitransfer, setup guidance, --version, AGENTS.md scan fix, logo - #44
Merged
Merged
Conversation
…est on the agentkey devDependency The repository moved to the Optitransfer org; homepage, repository and bugs follow it. The owner-signature test ran agentkey from a path on my laptop, so it failed in any other clone. It now uses @optitransfer/agentkey from the lockfile, and CI installs that lockfile before the self-gate. (PL-SELF) Signed-off-by: mgillr <[email protected]>
…gentkey Both refusals ended in 'Next step: proofline setup', which sent the user round in a circle. Each now says what the variable or command is for and prints the exact command that provides it. (PL-SELF) Signed-off-by: mgillr <[email protected]>
Signed-off-by: mgillr <[email protected]>
… scan The README tells users to copy AGENTS.md into their repository. Its 'Never' list wrote the hook-skipping flag literally, so the first verify failed on no_verify. (PL-SELF) Signed-off-by: mgillr <[email protected]>
…correct the published version The README named 0.2.0-next.0; npm has 0.2.0-next.1. (PL-SELF) Signed-off-by: mgillr <[email protected]>
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.
Proofline moved from my account to the Optitransfer org. This PR follows the move and fixes the problems that showed on the repository page.
Move
homepage,repositoryandbugsnow point toOptitransfer/proofline. The old URL redirects.npm ci --ignore-scriptsbefore the self-gate, so the pinned dev dependencies are there.Fixes
/Users/imac27/...), so it failed in any other clone. It now uses the@optitransfer/agentkeydevDependency, pinned at 0.1.1 in the lockfile.proofline setupandproofline contract signstopped at "AGENTKEY_HOME is not set" or "agentkey is not on PATH", and the next step they gave was the same command again. Each one now says what is missing and prints the command that fixes it. The README covers both before the short path. The first line of each message is unchanged.AGENTS.mdthe README tells you to copy tripped theno_verifyrule of a fresh contract on the firstverify. The Never list now describes the hook-skipping flag in words. The rule itself is unchanged.proofline --version/-vprints the installed version. On a subcommand,--versionis still refused as an unknown flag.0.2.0-next.0; npm has0.2.0-next.1.docs/logo.svg,docs/logo-white.svg, PNGs) and CI and npm badges at the top of the README.Not changed:
proofline.json,proofline.json.sig, the contract, the forbidden rules, every CLI command, flag and exit code, and the config format. New tests:setup_guidance,version,agents_md_scan, each red on main and green here.